You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
There are a ton of little things like that. And I don't write about the non-metals, because the answer is that we are not going to change anything (including the bugs), and that's it.
Visual Studio has a plugin(VassistX) that, among other things, highlights user-defined types, including classes, in colour when an instance of the class is initialised. Is it possible for developers to add class highlighting in colour to MetaEditor in future builds?
Here's what to make it look like:
As in 4, metaeditor may overwrite the currently edited code file in case of a power failure or unexpected computer shutdown (file handling is a sore subject for developers in general, somehow file operations they never tra-la-pam-pam).
If you noticed the loss of code and you do not want to lose the results of long-term work, this trouble has a solution. For goodness sake, the editor "littered" the disk with editable code unnoticed. You may scan the disk to find the freshest code fragment.
But you need a program that can access the disk on the physical level. Here I can not recommend anything, because for many, many years I use a very old program, but I think to find such a program is not a problem.
I have Ctrl+F7, when working with Expert Advisor without errors in the code, the error listing is 40 kilobytes long.
The main file is mq5, classes are in mqh. Every mqh is processed, despite the fact that these files are not intended to be compiled, but are built in mq5.
Should I translate the code into files with other extensions or is there another solution to this problem?
gip:
If you notice that code is missing and you don't want to lose the results of a long run, there is a solution to this problem. For the good of the editor, it is unnoticeable that it "littered" the disk with editable code. By scanning the disk you may find the freshest copy of a code fragment.
It's hard to recover... it's better to keep a copy!
recovery is difficult... it's better to keep a copy always!
Depending on where you want to restore. It is easier to always keep a copy on disk (if possible, also on flash drives).
PS
By the way, if you work from a flash drive, you can almost always recover the data (if you notice it in time).