While VS is one of the few at least partially good things MS has done over the years you can have dark colors in MetaEditor as well. Background and highlights can be defined in settings and the interface abides Windows themes, although not as perfectly as possible.
You cannot say "partially good" when developers in Metaeditor got stuck for several years in the very same version of the Editor, with the very same features as it has today.
What is the MQ core business?
At least, have the damn CLI compiler signaling the Terminal (Core Business), that its EA code has changed and it has to be reloaded. Let developers choose their own developing venue... and be more productive. That's the business they want, and that's the business we want. Free us on the development side, focus on the Terminal side...
The productivity index measures the output produced for each hour of labor worked. This indicator is useful for predicting inflation and output growth. If the cost of labor increases respective to the increase of productivity, and, moreover, if the increase in production costs is unlikely, then it will not cause inflation. It has a significant...
While VS is one of the few at least partially good things MS has done over the years you can have dark colors in MetaEditor as well. Background and highlights can be defined in settings and the interface abides Windows themes, although not as perfectly as possible.
Can you share your config? Don't mind if this will take to much of your time.
Well, we are talking here about the Open Source project from Microsoft called Visual Studio Code. It is completely FREE for personal and commercial use. Download it from here: code.visualstudio.com. Install it - the process is plain simple and common. Then, launch it. VSC will automatically launch a web page with initial tutorials, it is a good...
"Remember to always make a backup of this settings anywhere you want. I prefer to save my code snippets in a a Gist in my GitHub space. So I can grab and update them easily over several machines."
You might want to checkout the VSC extention "Settings Sync".
It basically automates your backup via Gist concept, and lets you easily export/import configs across different machines and environments - brings along all your extensions too!
"Remember to always make a backup of this settings anywhere you want. I prefer to save my code snippets in a a Gist in my GitHub space. So I can grab and update them easily over several machines."
You might want to checkout the VSC extention "Settings Sync".
It basically automates your backup via Gist concept, and lets you easily export/import configs across different machines and environments - brings along all your extensions too!
We know all MetaEditor has some drawbacks, mainly when you work with medium/big projects. However it has some interesting built-in features linked with MT4/MT5 terminal.
Mainly the debugging features, which I am using heavily, so I am wondering how people using an external editor are managing that. I can't imagine you always have to print your variable's value to debug your code ?
We know all MetaEditor has some drawbacks, mainly when you work with medium/big projects. However it has some interesting built-in features linked with MT4/MT5 terminal.
Mainly the debugging features, which I am using heavily, so I am wondering how people using an external editor are managing that. I can't imagine you always have to print your variable's value to debug your code ?
What I do is run both editors simultaneously so changes in one are mirrored in the other. The only time you will run into issues is when you make changes in one, forget to save, then make changes in the other and thereby create merge conflicts. This can be mostly mitigated by turning on the autosave feature in vscode.
We know all MetaEditor has some drawbacks, mainly when you work with medium/big projects. However it has some interesting built-in features linked with MT4/MT5 terminal.
Mainly the debugging features, which I am using heavily, so I am wondering how people using an external editor are managing that. I can't imagine you always have to print your variable's value to debug your code ?
Nailed it! Print everywhere - just with an added IF to print the correct set of data in case you are inside a FOR...
But, I'm loving it...
Visual GIT on the Navigator tree, TODOs widget, NO strain to the eyes... with a decent machine, knocking down the Terminal and then the compiling time is pretty fast... No Looking Back... (It is NOT for the beginners - I'm a coder since my 14 yo...)
What I do is run both editors simultaneously so changes in one are mirrored in the other. The only time you will run into issues is when you make changes in one, forget to save, then make changes in the other and thereby create merge conflicts. This can be mostly mitigated by turning on the autosave feature in vscode.
It's what I thought, not worth the trouble for me. Thanks for your answer.
Nailed it! Print everywhere - just with an added IF to print the correct set of data in case you are inside a FOR...
But, I'm loving it...
Visual GIT on the Navigator tree, TODOs widget, NO strain to the eyes... with a decent machine, knocking down the Terminal and then the compiling time is pretty fast... No Looking Back... (It is NOT for the beginners - I'm a coder since my 14 yo...)
;)
I am interested by efficiency and not by gadget. Using print statement to debug nowadays is insane.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
While VS is one of the few at least partially good things MS has done over the years you can have dark colors in MetaEditor as well. Background and highlights can be defined in settings and the interface abides Windows themes, although not as perfectly as possible.
You cannot say "partially good" when developers in Metaeditor got stuck for several years in the very same version of the Editor, with the very same features as it has today.
What is the MQ core business?
At least, have the damn CLI compiler signaling the Terminal (Core Business), that its EA code has changed and it has to be reloaded. Let developers choose their own developing venue... and be more productive. That's the business they want, and that's the business we want. Free us on the development side, focus on the Terminal side...
While VS is one of the few at least partially good things MS has done over the years you can have dark colors in MetaEditor as well. Background and highlights can be defined in settings and the interface abides Windows themes, although not as perfectly as possible.
Can you share your config? Don't mind if this will take to much of your time.
Can you share your config? Don't mind if this will take to much of your time.
Since my last post on using VSC for my coding... I'm still LOVING IT...
I'm using a set of colors in VSC that is visually coherent and visually usefull:
https://gist.github.com/MinionsLabs/5025741818d603a1b43286248d3d2ad8
Cheers!
;)
Since my last post on using VSC for my coding... I'm still LOVING IT...
I'm using a set of colors in VSC that is visually coherent and visually usefull:
https://gist.github.com/MinionsLabs/5025741818d603a1b43286248d3d2ad8
Cheers!
;)
Great blog post.
In regards to this quote:
"Remember to always make a backup of this settings anywhere you want. I prefer to save my code snippets in a a Gist in my GitHub space. So I can grab and update them easily over several machines."
You might want to checkout the VSC extention "Settings Sync".
It basically automates your backup via Gist concept, and lets you easily export/import configs across different machines and environments - brings along all your extensions too!
Great blog post.
In regards to this quote:
"Remember to always make a backup of this settings anywhere you want. I prefer to save my code snippets in a a Gist in my GitHub space. So I can grab and update them easily over several machines."
You might want to checkout the VSC extention "Settings Sync".
It basically automates your backup via Gist concept, and lets you easily export/import configs across different machines and environments - brings along all your extensions too!
Wow! I will check this! Thanks a lot!
It's been more almost 3 months using VSC on a daily basis. I'm lovivng it!
Additional Tip: for those who need Like me TODOs and FIXMEs right inbto the code, I'm using Todo Tree. It is simple and Superb!
We know all MetaEditor has some drawbacks, mainly when you work with medium/big projects. However it has some interesting built-in features linked with MT4/MT5 terminal.
Mainly the debugging features, which I am using heavily, so I am wondering how people using an external editor are managing that. I can't imagine you always have to print your variable's value to debug your code ?
We know all MetaEditor has some drawbacks, mainly when you work with medium/big projects. However it has some interesting built-in features linked with MT4/MT5 terminal.
Mainly the debugging features, which I am using heavily, so I am wondering how people using an external editor are managing that. I can't imagine you always have to print your variable's value to debug your code ?
What I do is run both editors simultaneously so changes in one are mirrored in the other. The only time you will run into issues is when you make changes in one, forget to save, then make changes in the other and thereby create merge conflicts. This can be mostly mitigated by turning on the autosave feature in vscode.
We know all MetaEditor has some drawbacks, mainly when you work with medium/big projects. However it has some interesting built-in features linked with MT4/MT5 terminal.
Mainly the debugging features, which I am using heavily, so I am wondering how people using an external editor are managing that. I can't imagine you always have to print your variable's value to debug your code ?
Nailed it! Print everywhere - just with an added IF to print the correct set of data in case you are inside a FOR...
But, I'm loving it...
Visual GIT on the Navigator tree, TODOs widget, NO strain to the eyes... with a decent machine, knocking down the Terminal and then the compiling time is pretty fast... No Looking Back... (It is NOT for the beginners - I'm a coder since my 14 yo...)
;)
What I do is run both editors simultaneously so changes in one are mirrored in the other. The only time you will run into issues is when you make changes in one, forget to save, then make changes in the other and thereby create merge conflicts. This can be mostly mitigated by turning on the autosave feature in vscode.
Nailed it! Print everywhere - just with an added IF to print the correct set of data in case you are inside a FOR...
But, I'm loving it...
Visual GIT on the Navigator tree, TODOs widget, NO strain to the eyes... with a decent machine, knocking down the Terminal and then the compiling time is pretty fast... No Looking Back... (It is NOT for the beginners - I'm a coder since my 14 yo...)
;)