Vanilla MT4 | Page 2 | Metals Mine

Options

Go to
Permalinks
Print Thread

Similar Threads

Best Forex Vanilla Options Broker 0 replies

Plain Vanilla options 1 reply

5 decimal places in MT4? 5 secs timeframe in MT4 6 replies

MT4 Mobile vs. MT4 Mobile SE - Significant difference? 0 replies

Any effect with charting MT4 but executing trades with non-MT4 broker? 17 replies

Attachments: Vanilla MT4
Exit Attachments

Vanilla MT4

  • #21
  • Aug 11, 2018 5:52pm Aug 11, 2018 5:52pm
VERSION 0.0.2 UP NOW! https://goo.gl/8QSbGq

Changelog -

  1. Updated terminal to build 1126 and metaeditor to build 1861 (June '18 update)
  2. Changed name of setup.exe to MT-Tools.exe
  3. Launchers in terminal directories are now prefixed with the machine name for launching on multiple machines from one synced cloud-drive
  4. A "LAUNCH-ALL-TERMINALS" file is now included in the main MT4 parent directory to launch all terminals without needing directly invoke the script and selecting the option.
  5. Bug fixes

  • #22
  • Aug 12, 2018 9:28am Aug 12, 2018 9:28am
Awesome! This thing is a life changer.
  • #23
  • Aug 12, 2018 10:47am Aug 12, 2018 10:47am
Quoting Nicholishen
VERSION 0.0.2 UP NOW! https://goo.gl/8QSbGq Changelog - Updated terminal to build 1126 and meta editor to build 1861 (June '18 update) Changed name of setup.exe to MT-Tools.exe Launchers in terminal directories are now prefixed with the machine name for launching on multiple machines from one synced cloud-drive A "LAUNCH-ALL-TERMINALS" file is now included in the main MT4 parent directory to launch all terminals without needing directly invoke the script and selecting the option. Bug fixes
Good day, Nicholsen .... a big fan of your work here, especially the chartstudyprofilemanager (most useful part of my arsenal so far).....
now, concerning your new piece of work, I am trying to grasp what it does exactly and if it is similar to this tool ( http://www.floatingcharts.com/ ) in action... I use a three-screen setup and if your new piece does similar stuff to the above link, that would be mad awesome...please clarify if they are similar in any way... thanks
  • #24
  • Aug 13, 2018 10:14am Aug 13, 2018 10:14am
Quoting hubertolie
{quote} Good day, Nicholsen .... a big fan of your work here, especially the chartstudyprofilemanager (most useful part of my arsenal so far)..... now, concerning your new piece of work, I am trying to grasp what it does exactly and if it is similar to this tool ( http://www.floatingcharts.com/ ) in action... I use a three-screen setup and if your new piece does similar stuff to the above link, that would be mad awesome...please clarify if they are similar in any way... thanks
Great question. Floating charts removes the window limitations and allows you to separate the chart windows from the terminal. The alternative to using floating charts is to use two (or more) running terminals that are logged into the same account.
The problem with with this method is:

  1. while each terminal is getting the same account data from the broker you will have history files being built * n terminals
  2. your MQL files won't be synced
  3. it's generally a PITA to launch multiple terminals.

Using Vanilla MT4 you'll be able to easily:

  1. launch multiple terminals
  2. the multiple histories are now stored in one folder only
  3. MQL files are all synced.

I would argue that this option is better than floating charts because now you'll have the full depth of terminal options for each window.

To set this up you would:

  1. Download and run MT-Tools.exe
  2. Setup your account on the first terminal
  3. Copy your MQL files to the new directory.
  4. Make sure all your settings are how you want them
  5. Launch MT-Tools again and select the "clone" option.
  6. Since you have 3 monitors, you'll want to add 2 more clone terminals
  7. Use the "LAUNCH-ALL-TERMINALS" shortcut to launch all windows at once.

Here's an example of what it looks like on my dual monitor config (1 landscape and 1 portrait)

Attached Image (click to enlarge)
Click to Enlarge Name: Screenshot (1).png Size: 394 KB
  • #25
  • Aug 15, 2018 3:22pm Aug 15, 2018 3:22pm
Quoting Nicholishen
{quote} Great question. Floating charts removes the window limitations and allows you to separate the chart windows from the terminal. The alternative to using floating charts is to use two (or more) running terminals that are logged into the same account. The problem with with this method is: while each terminal is getting the same account data from the broker you will have history files being built * n terminals your MQL files won't be synced it's generally a PITA to launch multiple terminals. Using Vanilla MT4 you'll be able to easily: launch...
Lovely reply, much appreciated, quite clear now........ one quick add-on though... is it, even slightly possible to add a means to control multiple instrument tabs across the mt4s opened at the same time (that is, if I click on Eurusd tab on one mt4 say the daily chart on one screen, the others (say the Eurusd H4 and H1 tabs on the mt4 setups on the other screens that have been set up, open/pop up at the same time). Seeing as the idea behind multiple screens/mt4s is to be able to do top-down analysis, so as to see the overall picture the market is painting....(something like a real-time mt4 remote for multiple instances of the app) hope you get what I am trying to point out... great stuff you put out by the way, we appreciate the kindness.
  • #26
  • Aug 15, 2018 3:43pm Aug 15, 2018 3:43pm
This will prove very useful for all the portable mt4's I have manually been copy & pasting with this i'tll be a real time saver thank you so much for sharing
  • #27
  • Aug 15, 2018 8:21pm Aug 15, 2018 8:21pm
Quoting hubertolie
{quote} Lovely reply, much appreciated, quite clear now........ one quick add-on though... is it, even slightly possible to add a means to control multiple instrument tabs across the mt4s opened at the same time (that is, if I click on Eurusd tab on one mt4 say the daily chart on one screen, the others (say the Eurusd H4 and H1 tabs on the mt4 setups on the other screens that have been set up, open/pop up at the same time). Seeing as the idea behind multiple screens/mt4s is to be able to do top-down analysis, so as to see the overall picture the...
In terms of this project, each terminal is isolated unto itself so that feature is not inherent with this type of setup. If that's a feature you need then you'll probably still want to use floating-charts, and then use this setup when you need multiple synced terminals.
  • #28
  • Aug 19, 2018 9:02pm Aug 19, 2018 9:02pm
Quoting Nicholishen
{quote} Anything can be done. You can easily write a python script to compile by command-line, but I can assure you that is not the answer. You should never need to re-compile your EA unless you are making hard changes to your logic, and hiding input params does nothing to improve security. Based on your explanation your EA should be reading from a csv file which you can keep open in excel to change the params on the fly. Also, I've seen in wireshark that both metaeditor and terminal call to several different APIs hosted on mql5.com, and it's entirely...
I am not surprised with what you are seeing in wireshark. I am sure the server can decypher what the client is doing or configured. Could you please explain "open-source is the only way to secure your algo"... how open source will secure my algo? I don't want anyone to read my MQ4 :-
Staying in my lane...
  • #29
  • Aug 19, 2018 9:42pm Aug 19, 2018 9:42pm
Very interesting Nicholishen. Thanks for posting.
  • #30
  • Aug 20, 2018 5:04am Aug 20, 2018 5:04am
Quoting VEEFX
{quote} I am not surprised with what you are seeing in wireshark. I am sure the server can decypher what the client is doing or configured. Could you please explain "open-source is the only way to secure your algo"... how open source will secure my algo? I don't want anyone to read my MQ4 :-
The point I was making was that MQL is a proprietary language that makes programs with a proprietary compiler that run on a proprietary platform. I'm not saying there are malicious back-doors built into MT, but I can assure you there's no way to prove that there isn't. So if you had a legit need to secure your logic then the obvious first step is to compartmentalize it from the potential security threat, and in this case we're talking about metatrader. The reason you need to use open-source is because you know there's no phone-home mechanisms in your stack because you have full stack visibility. So let's say you're not ready to port over to a full FIX stack and you have a broker that you like (they use MT), then you'd want to run a socket server from MT and use a separate program to run your logic and make simple calls into your MT-server with trade commands. In this example I'd use dingmaotu's mql-zmq to run an EA as a "server", and then I'd run all my logic in a program written in python.
  • #31
  • Aug 20, 2018 10:49am Aug 20, 2018 10:49am
Quoting Nicholishen
{quote} The point I was making was that MQL is a proprietary language that makes programs with a proprietary compiler that run on a proprietary platform. I'm not saying there are malicious back-doors built into MT, but I can assure you there's no way to prove that there isn't. So if you had a legit need to secure your logic then the obvious first step is to compartmentalize it from the potential security threat, and in this case we're talking about metatrader. The reason you need to use open-source is because you know there's no phone-home mechanisms...
Perfect. Thanks for your time in explaining. That is the route I am eventually planning to take...a complete broken-independant, platform-independant fully owned server based solution. My design has no effect on spread widening or slippage so using one price feed and sending orders via API to a different broker will also work. My kids have picked up python so I am learning a little bit myself as well. I will most likely transition to Oanda API first to dip my toes and then move to FIX.

I had mentioned a while back that I have secured a decent large line of credit to go big (instead of andgoing the VC route) and some idiots thought I will risk that capital to trade LOL Hopefully I will get to where I want to be (in complete isolation :-)
Staying in my lane...
  • #32
  • Aug 20, 2018 11:31am Aug 20, 2018 11:31am
Quoting VEEFX
{quote} Perfect. Thanks for your time in explaining. That is the route I am eventually planning to take...a complete broken-independant, platform-independant fully owned server based solution. My design has no effect on spread widening or slippage so using one price feed and sending orders via API to a different broker will also work. My kids have picked up python so I am learning a little bit myself as well. I will most likely transition to Oanda API first to dip my toes and then move to FIX. I had mentioned a while back that I have secured a decent...
If you already have the grail and the capital then it's time to spread your wings and leave the MT nest all together.
  • #33
  • Edited 7:50pm Aug 20, 2018 5:11pm | Edited 7:50pm
Quoting VEEFX
{quote} ...I also deal with one more issue across terminals. I compile my EA several times a day as I do not have external parameters (by design). in current state, I have the metaediter opened for each terminal instance to make 4-5 times same code edits and then compile for EA to go into effect. Is there a way to make such code changes only once and have it go into effect to all terminals without restarting the terminals...
There is a very easy solution for that problem. Have your MQL sources in a Git repository outside your regular terminal installations. Any other versioning system will do but Git is the standard and the best. You make code changes in the repo and compile only once.

Symlink the MQL4 folders of all your parallel installed terminals to the repo and make changes only in the repo (use the Link Shell extension for this). This way changes get distributed to all terminals immediately. The terminals will not get notified by the MetaEditor and will not reload indicators/experts (you don't really want this if the terminal is trading). However changed scripts are detected and used immediately.

Only a terminal in the repo folder (if you have one running there which is a valid use case) will automatically reload indicators/experts. Be very careful with this and don't do it with trading code. It's possible to reload without errors but there are plenty of issues. Better avoid it.

If you really want to automatically notify all terminals you have to use some custom C++ code. Hook the WinAPI messages sent to the terminal by the MetaEditor and send duplicates to the other terminals. I use WinSpector for finding the messages. Not for the faint-hearted and I personally don't need it. Even without that other terminals don't need to be restarted, only the changed MQL module needs to be reloaded. I usually do this by having the indicator/expert under work in a template and then it's just a mouse click to reload the template.

Another important advantage of a versioning system is that MetaQuotes can not mess around with your files. If a new terminal version indeed does you immediately notice it and can rollback with a single command (git reset ...).

My trading code runs on a VPS (strict separation between development and production). Again multiple parallel intallations and again with Git it's just a single command (git pull...) to update all installations at once.

Attached a screenshot how it looks in practice. These are 22 instances running on only one MQL codebase. In this case even old (pre 600) and new (post 600) terminal versions are mixed.

Attached Image


Repo structure (just as an example): https://github.com/rosasurfer/mt4-mql
It takes blood, sweat and enough tears to wash away the blood.
  • #34
  • Aug 20, 2018 9:21pm Aug 20, 2018 9:21pm
Quoting emmzett
{quote} There is a very easy solution for that problem. Have your MQL sources in a Git repository outside your regular terminal installations. Any other versioning system will do but Git is the standard and the best. You make code changes in the repo and compile only once. Symlink the MQL4 folders of all your parallel installed terminals to the repo and make changes only in the repo (use the Link Shell extension for this). This way changes get distributed to all terminals...
I'm totally on board with git and use it all the time. Anyone who does anything with programming and doesn't know git should learn it and use it ASAP. That being said, the rest of the stuff you mention is already handled in the included MT-Tools program.
  • #35
  • Aug 20, 2018 10:10pm Aug 20, 2018 10:10pm
Excellent. I expect later we can connect MT5 or MT6 data feed to this broker-independent MT4 for charting. People will make EA for this data feed connection. I will continue to use MT4 for next +20 years for charting.....
Simplicity is the ultimate sophistication - Leonardo da Vinci
  • #36
  • Aug 20, 2018 10:50pm Aug 20, 2018 10:50pm
Quoting heispark
Excellent. I expect later we can connect MT5 or MT6 data feed to this broker-independent MT4 for charting. People will make EA for this data feed connection. I will continue to use MT4 for next +20 years for charting.....
This isn't a modified terminal. Even though it's free of broker specific branding and config you will still need to connect to a broker with a MT4 feed.
  • #37
  • Aug 21, 2018 2:04am Aug 21, 2018 2:04am
Quoting Nicholishen
{quote} This isn't a modified terminal. Even though it's free of broker specific branding and config you will still need to connect to a broker with a MT4 feed.
Perhaps, we can log into a 'virtual' broker through EA in MT5 side (to get price data feed from a broker based MT5. Because I have custom indicators without source codes, I have to stick to MT4.) Anyway, this needs to be done in the future.....when MT4 is no longer supported in decent brokers. Also, I expect we will have some commercial solutions thanks to high demand. MT4 will live much longer regardless of Metaquotes' hope.
Simplicity is the ultimate sophistication - Leonardo da Vinci
  • #38
  • Edited 3:18am Aug 21, 2018 2:17am | Edited 3:18am
Quoting heispark
{quote} Perhaps, we can log into a 'virtual' broker through EA in MT5...
Connecting an MT4 terminal to an external datafeed is possible but a complete different ball-park. I know for sure that it's possible with old builds, I doubt that it would be easy for current builds. For example my setup uses tricks with the old terminals to get real offline-charts (offline-charts where you can switch timeframes in the regular way during offline-updating).

But it's kind of off-topic here, so I will not go into it much further.
It takes blood, sweat and enough tears to wash away the blood.
  • #39
  • Aug 21, 2018 3:34am Aug 21, 2018 3:34am
Quoting Nicholishen
{quote} I'm totally on board with git and use it all the time. Anyone who does anything with programming and doesn't know git should learn it and use it ASAP. That being said, the rest of the stuff you mention is already handled in the included MT-Tools program.
Isn't git an online repository instead of local and isolated? Why would I want to expose my mql code outside of my garage :-)

Quoting emmzett
{quote} There is a very easy solution for that problem. Have your MQL sources in a Git repository outside your regular terminal installations. Any other versioning system will do but Git is the standard and the best. You make code changes in the repo and compile only once. Symlink the MQL4 folders of all your parallel installed terminals to the repo and make changes only in the repo (use the Link Shell extension for this). This way changes get distributed to all terminals...
Thanks. I learned something new today. Appreciate it.
Staying in my lane...
  • #40
  • Aug 21, 2018 4:18am Aug 21, 2018 4:18am
Quoting VEEFX
{quote}...Isn't git an online repository instead of local and isolated? Why would I want to expose my mql code outside of my garage :-) {quote}...
Let me try to answer that. Git is just a command line tool and the standard versioning system for developers. Whether you publish your repo online visible to anybody, or create a private repo at Github accessible only by you, or create a private repo on a private server (accessible only by you and not even by Github), or don't use a Git server at all and store your repo locally on your machine or a USB stick (in this case your development code base connects to a "Git server" on your local machine), is completely up to you. Git itself (the binary) can act as both: versioning management and Git server.

Said that, storing a repo on a public server (even if visibility is private) has a lot of advantages. Nowadays there are countless web services supporting developers by fetching each new change made by you, analyzing it (statically or dynamically) and helping you in ensuring/improving code quality. This alone makes an externally accessible repo worth it. Many of those services are even free. Github makes sure that only the services you allow get access to your proprietary codes.

Then there is this other very common mis-believe: Why would I want to expose my code outside of my garage?
Opposite to of what most people think you will not risk losing your genious ideas to the public by publishing it. After some years of hiding my code I realized that even if I publish a profitable strategy, almost nobody else will be capable of re-using it (and thus "stealing" my idea). If it only was that easy...

Any profitable strategy needs to be continously maintained, without deep understanding of the inner workings nobody can simply "re-use" it. Consider on top of that the huge majority of FF members is not able to even copy a downloaded file to the right MetaTrader folder.

An automated system is exactly that, it will continue without question even if it starts losing. Without constant market adaption every strategy stops working after a few months. This is the nature of automated trading, otherwise banks would fire all their traders and only trade in an "automated" way. However the truth is only a very small percentage of money is traded fully automated. Manual trading with manual risk control will always achieve superior results.

So for me, having the possibility that somebody spots an error in my codes very much outweights the "dis-advantage" of it being not hidden. Also public code forces you to think more before you write (think of private or sensitive data which should never be hardcoded). A public repo already improves code quality by itself.
It takes blood, sweat and enough tears to wash away the blood.
0 traders viewing now