Gallery of UIs written in MQL - page 29

 
After I generated Internal_API.mqh, I couldn't compile the file, the function was redefined, exactly the same code!
 
hini #:
After creating the file Internal_API.mqh I could not compile it, the function was overridden, exactly the same code!

This is strange. Perhaps you forgot to recompile the EA (1)KIB v1.mq5 again

You probably have a version running before yesterday's update.

Open it and compile it. Then add it to the chart again.

 
Реter Konow #:

This is strange. Perhaps you forgot to recompile the Expert Advisor (1)KIB v1.mq5.

Probably you are running the version before yesterday's update.

Open it and compile it. Then add it to the chart again.

You should see something like this:


 
Реter Konow #:
Maybe you forgot to recompile EA (1)KIB v1.mq5.

It was already recompiled. Same problem.

 
Реter Konow #:
Then add it to the chart again.

Yes, see it's just like you did.

 
Did you generate Internal_API.mqh without problems?
 
hini #:

Yes, you see, it's exactly the same as yours.

Oh, good. Now our data matches.

 
hini #:
Did you generate the Internal_API.mqh file without any problems?

Yes. But now it is printed for demonstration and understanding of UI connectivity than for work. Wait for the release of the engine.

 
Реter Konow #:

Great. Now our numbers match.

But the above problem still exists and the compiler says: EA_ADRESS is undefined, should we use DRIVE_MESSAGE_ADRESS?

 
hini #:

But the above problem still exists and the compiler says: EA_ADRESS is not defined, should we use DRIVE_MESSAGE_ADRESS?

Now the file is printed for demonstration and to understand the UI connectivity.