Errors, bugs, questions - page 2231

 

There are two experts. Knock on the same file opened via FileOpen with these flags:

in Expert 1 -FILE_READ|FILE_WRITE|FILE_BIN|FILE_SHARE_READ

in Expert 2 - FILE_READ|FILE_BIN|FILE_SHARE_READ

The second expert gets error 5004.

How to provide a read?

 
Stanislav Korotky:

How do you ensure a reading?

This was discussed a week ago https://www.mql5.com/ru/forum/1111/page2226#comment_8062626

Apparently not - since nothing has changed in two years

Ошибки, баги, вопросы
Ошибки, баги, вопросы
  • 2018.07.12
  • www.mql5.com
Общее обсуждение: Ошибки, баги, вопросы
 
Stanislav Korotky:

There are two experts. Knock on the same file opened via FileOpen with these flags:

in Expert 1 -FILE_READ|FILE_WRITE|FILE_BIN|FILE_SHARE_READ

in Expert 2 - FILE_READ|FILE_BIN|FILE_SHARE_READ

The second expert gets error 5004.

How to provide reads?

I would use a resource that can be read from a file and saved to a file for sharing within one terminal instead of a file.

union to help.

 
Stanislav Korotky:

There are two experts. Knock on the same file opened via FileOpen with these flags:

in Expert 1 -FILE_READ|FILE_WRITE|FILE_BIN|FILE_SHARE_READ

in Expert 2 - FILE_READ|FILE_BIN|FILE_SHARE_READ

The second expert gets error 5004.

How to provide reading?

Are these two EAs in the same terminal?

If not, where is the FILE_COMMON flag?

 
Stanislav Korotky:

There are two experts. Knock on the same file opened via FileOpen with these flags:

in Expert 1 -FILE_READ|FILE_WRITE|FILE_BIN|FILE_SHARE_READ

in Expert 2 - FILE_READ|FILE_BIN|FILE_SHARE_READ

The second expert gets error 5004.

How do you provide a read?


Try addingFILE_SHARE_WRITE as well.

 
Vladislav Andruschenko:


Try addingFILE_SHARE_WRITE as well.

Tried it, doesn't help. Other comments - COMMON is not needed, because there is only one terminal, if there were several, it would be COMMON, but it doesn't solve anything. What I need are files - resources don't work.

Above have given link (even two) to the same problem - it seems it really exists - very sad.

PS. That's why I do not like forums with such endless questions and answers - it is difficult to systematise information in them. I have long suggested that MQ make questions and answers separate, similar to SO, but the old-fashioned way is probably more familiar.

 
Stanislav Korotky:

Try after opening a file for writing (part 1 of the code) to view it with Windows viewer. at least it will be clear which handle the problem is with.

If it opens, it's the second one, if not, it's the first one.

 
Alexey Kozitsyn:

Only there's a catch. If you then go to the object properties and exit from there, the levels will be coloured the same colour:) Still, there are some lags with this coloring. Bild 1881, x64.

Colours of different levels can only be set programmatically.

From the object properties dialog one colour is assigned to all levels. That's the way it was intended.

But we'll see what can be done to not reset the colour from the object's properties dialog, if it was not touched

 
Alexander:

The colours of the different levels can only be set programmatically.

The same colour is assigned to all levels in the object properties dialogue. This is the intention.

But we will see what we can do to not reset the colour from the object properties dialog if it has not been touched

Thanks for the reply.

 
Vladislav Andruschenko:

Problem in the marketplace:

When replying to messages in the Discussion section, or adding a new reply, a blank page appears:

Whereas if you copy the link after the reply, the same blank page appears.

But if you click on the DISCLOSURE tab, then the page with the same link appears (I compared it) and everything is fine.

Vladislav Andruschenko:

The problem is in the marketplace from a mobile phone:

If you go from your mobile phone (any phone) to your profile - seller - stats, then the stats hangs and the site is unavailable for about 5 minutes.

Nothing happens, no data is displayed.

The status bar freezes.

This is only in the Seller - Statistics section


Thank you for your messages. We're sorting it out.

Reason: