Bugs in Metaeditor/parser

[democog]

Hello, 

I came across two bugs in Metaeditor, one visual and the other with the parser

 The visual one is kinda weird because it only appears under certain circumstances that are not very obvious, still it appeared to me when some dozen tabs were open and the two last ones were having the names "props" and "base"; this is important because it seems to matter what is the size of the names and also of the content - so not all 4-letter words are the same (because of the font of the tabs being not monospaced).. Also, it happened when much many tabs were open - so to speak.. Last, I may say that I have a "custom scaling" in my PC, along with altered "text size", all in Windows (11) settings 

 Also, here is the parser bug: 

        ushort val;

        Alert("some "+++val); 

greets

[Matei-Alexandru Mihai]

Interesting findings, thanks for sharing. I’ve also noticed some small inconsistencies in MetaEditor from time to time, but never looked into it deeply. Good catch with the parser bug, hopefully MetaQuotes will fix this in a future update.

[democog]

Matei-Alexandru Mihai #:
Interesting findings, thanks for sharing. I’ve also noticed some small inconsistencies in MetaEditor from time to time, but never looked into it deeply. Good catch with the parser bug, hopefully MetaQuotes will fix this in a future update.

Hello, 

Greets for the comment as well :) Well, it is true that there could be some small bugs here and there, but I really wish that MetaQuotes would look from the ground up/overhaul the import (#import) functionality, because right now it seems more of a hit and miss when it will work.. So some times I find I have to proceed completely without it, which of course increases the compile time

greets

[Matei-Alexandru Mihai]

democog #:

Hello, 

Greets for the comment as well :) Well, it is true that there could be some small bugs here and there, but I really wish that MetaQuotes would look from the ground up/overhaul the import (#import) functionality, because right now it seems more of a hit and miss when it will work.. So quite often I find I have to proceed completely without it, which of course increases the compile time

greets

Yes, I completely agree with you. The #import functionality does feel inconsistent at times, and I’ve also noticed cases where it behaves unpredictably. It would be great if MetaQuotes could give this part a full review in a future update, because compile time and reliability are really important for bigger projects. Thanks again for pointing this out!

[democog]

Matei-Alexandru Mihai #:
Yes, I completely agree with you. The #import functionality does feel inconsistent at times, and I’ve also noticed cases where it behaves unpredictably. It would be great if MetaQuotes could give this part a full review in a future update, because compile time and reliability are really important for bigger projects. Thanks again for pointing this out!

Well, we can only hope :) In the mean time I will prepare a minimal example where import fails but I guess I will post on a separate topic 

greets