does MQL5 Cloud Protector work for ex4? because we can use MetaEdit of MT5 to compile .mq4 file.
does MQL5 Cloud Protector work for ex4? because we can use MetaEdit of MT5 to compile .mq4 file.
At this moment Cloud Protector not supported in the current MT4. Please wait when update will be available for MT4.
At this moment Cloud Protector not supported in the current MT4. Please wait when update will be available for MT4.
Got it. Thank you.
Nice Job!!
Custom symbols are running so smooth! :)
MQL5 Storage is not working with me, has anyone with the same problem like me?
The windows keeps blank when I click "Show storage log". I know my files are stored in the cloud, but somehow MetaEditor build 1702 is not recognize it, MetaEditor 1653 is fine about it.
Nice Job!!
Custom symbols are running so smooth! :)
MQL5 Storage is not working with me, has anyone with the same problem like me?
The windows keeps blank when I click "Show storage log". I know my files are stored in the cloud, but somehow MetaEditor build 1702 is not recognize it, MetaEditor 1653 is fine about it.
Did you try this instruction?
To support new shared projects, we have updated the protocol of operation with the MQL5 Storage. Therefore, you will need to perform a checkout of all data from the storage after the platform update. Data stored at the MQL5 Storage will not be lost or affected during the update.
Before updating the platform to the new version, we recommend that you perform the Commit operation to send all local changes to the MQL5 Storage.
Did you try this instruction?
Yes, I did, but something I noticed is that my commit logs are "gone". For an example, let's suppose I made 30 commits in MetaEditor build 1653. With Build 1703 I'm unable to see this 30 commits at my log and, as consequence, I can't go back to earlier versions of my project, but at least, I can access directly mql5 svn and retrieve it if needed. With this new protocol, I suppose I have to commit everything again and have a new log from this point forward. If I'm wrong about it or if you know a way to migrate from this svn to the new one, please let me know.
Thank you.
Yes, I did, but something I noticed is that my commit logs are "gone". For an example, let's suppose I made 30 commits in MetaEditor build 1653. With Build 1703 I'm unable to see this 30 commits at my log and, as consequence, I can't go back to earlier versions of my project, but at least, I can access directly mql5 svn and retrieve it if needed. With this new protocol, I suppose I have to commit everything again and have a new log from this point forward. If I'm wrong about it or if you know a way to migrate from this svn to the new one, please let me know. Thank you.
Unfortunatelly we can't transfer old commits to the new storage. All your commits in the old storage which will be available a long time. In the new storage we take effort to the shared projects as like github.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Long-awaited release of the platform which incorporates brand new features. Be among the first users to share the new experience.
The beta version of the updated MetaTrader 5 platform will be released on 6 December 2017. We will update our public MetaQuotes-Demo server located at access.metatrader5.com:443. We invite all traders to join testing in order to evaluate the updated platform features and to help developers fix errors.
To update the MetaTrader 5 platform up to build 1700, connect to access.metatrader5.com server:443.
The final build of the new MetaTrader 5 platform will be released after the public beta test.
Support for older versions of desktop and mobile terminals will end upon the release of the new platform version:
MQL5 Storage Operation Protocol Changes
To support new shared projects, we have updated the protocol of operation with the MQL5 Storage. Therefore, you will need to perform a checkout of all data from the storage after the platform update. Data stored at the MQL5 Storage will not be lost or affected during the update.
Before updating the platform to the new version, we recommend that you perform the Commit operation to send all local changes to the MQL5 Storage.
The update will feature the following changes:
Now the main MQ5 program file does not appear as the project. The project is a separate "MQPROJ" file, which stores program settings, compilation parameters and information about all used files. Main project settings can be accessed from a separate dialog box, so there is no need to specify them in the source code via #property now.
A separate tab in the Navigator is provided for a convenient work with the project. All files, such as include, resource, header and other files are arranged into categories on this tab. All files are automatically added to the project navigator. For example, if you include a new MQH file, it will automatically appear in the "Dependencies" section of the navigator.
Support for new projects has also been implemented in the updated MQL5 Storage online repository. It is a convenient option for developing large projects through collaboration with other members of the MQL5.community.
New Shared Projects section is provided for group projects. A project created in this section is immediately sent to the storage: you can grant permissions to other users and start collaboration right away.
When you compile a project in Shared Projects, an executable EX5 file is automatically copied to the local Experts, Indicators or Scripts directory depending on the program type. You can easily launch the program on a chart without having to copy files manually.What's New in the MQL5 Storage Operation
To implement support for new shared projects, we have modified the protocol of operation with the MQL5 Storage. Therefore, you will need to perform a checkout of all data from the storage after the platform update. Data stored at the MQL5 storage will not be lost or affected during the update.
New Projects: Examples of Creation and Operation Details
A new project entity has been added in MetaEditor. A project is an mqproj file that stores common program properties and information about all used files. Now, program properties can be conveniently managed from a separate MetaEditor dialog instead of manual modification of properties in the source code (using #property directives).
If you have available code, you can easily test new projects by using the 'New Project from Source' command.
In the directory where the selected file is located, a new project file with the same name and the mqproj extension will be created. The main program properties specified in the source code via #property will be automatically added to the project, including the name, copyright, version, link to the developer's site and program description.
Two new options for compiling MQL5 programs have been added to project properties:To work with projects, use a separate Project tab in the Navigator window. All files used in a project are displayed on this tab in a convenient form. When a project is generated from a source file, all used include files (specified using the #include directory in the main MQ5 file and in its include files) are automatically added to the Dependencies section.
When a new include file is added to the source code, it also appears in the project Navigator. Used header files are added to the Headers section; images, sounds and other MQL5 programs used in the project as resource are added to the Resources section. MQ5 files with the source code are displayed in the Sources section. In the 'Settings and files' section, you can add other files, such as set files for testing and chart templates.
Use context menu commands to add existing files to a project or to delete files from it. Be careful when deleting files, since you can remove a file from the project (remove the binding) or completely delete it from the hard disk:
Creation of a new project is as easy as the creation of a normal MQL5 program. Click 'New Project', select the type of new program and specify properties (such as name, event handlers, etc) in the MQL5 Wizard.To obtain an executable EX5 file, you can open the project and press F7 (the compilation command) or open the main MQ5 file of the program and compile it.
Shared Projects in MQL5 Storage: Operation Details
Shared projects are managed from a separate Shared Projects section. If you have not connected the storage yet, execute the 'Activate MQL5 Storage' command from the context menu of the desired folder. MetaEditor will check if your storage contains any saved data and if there are any share projects available to you. All available data will be retrieved from the storage and uploaded to your computer (the checkout operation). Available group projects appear in the Shared Projects section. To retrieve the projects, execute "Checkout from Storage" in the context menu.
To create a new group project, select the Shared Projects folder and click "New Project":
Then complete standard MQL5 steps: set the type, name and properties of the desired program. For group projects, you should use clear and understandable names, so that other participants could easily find them. Only Latin letters without spaces can be used in project names.A created object is immediately added to the MQL5 Storage. Standard Library files used in the project are not added to the storage, and you can add them manually.
To allow other participants to work with the project, open its properties. From here you can grant permissions to selected users by specifying their MQL5.community login, as well as set common parameters for the group work:
When you compile a group project, the executable EX5 file is automatically copied to the local Experts, Indicators or Scripts directory depending on the program type. It allows you to instantly run the program in the terminal without having to copy it manually to the proper directory.How It Works
Note: the USDEUR and USDGBP pairs are used in the source dollar index formula. Since only reverse pairs are available in the platform, a negative power and Ask instead of Bid are used in the synthetic symbol formula.
The platform will calculate in real time the price of the new instrument based on the quotes of the other six symbols provided by your broker. The price changes will be visualized in the Market Watch window and on the chart:
Create a new custom symbol, open its specification and enter the formula:
For convenience, the formula editor shows a list of possible options as you type the names of symbols and functions.Calculation of ticks and one-minute bars of a synthetic instrument starts when this instrument is added to the Market Watch. Also, all symbols required for the synthetic price calculation are automatically added to the Market Watch. An entry about the calculation start will be added to the platform journal: Synthetic Symbol USDX: processing started.
Real-Time Calculation of Quotes
Every 100 ms (i.e. ten times per second) the prices of symbols used in calculation are checked. If at least one of them has changed, the price of the synthetic symbol is calculated and a new tick is generated. Calculation is performed in parallel in three threads for Bid, Ask and Last prices. For example, if the calculation formula is EURUSD*GBPUSD, the price of the synthetic symbol will be calculated as follows:
The availability of changes is checked separately for each price. For example, if only the Bid price of a source instrument has changed, only the appropriate price of a synthetic instrument will be calculated.
Creating a History of Minute Bars
In addition to collecting ticks in real time, the platform creates a minute history of the synthetic instrument. It enables traders to view synthetic symbol charts similar to normal ones, as well as to conduct technical analysis using objects and indicators.
When a trader adds a synthetic instrument to the Market Watch, the platform checks whether its calculated minute history exists. If it does not exist, the history for the last 60 days will be created, which includes about 50,000 bars. If a lower value is specified in the 'Max. bars in chart' parameter in platform settings, the appropriate restriction will apply.
If some of bars within this period have already been created, the platform will additionally generate new bars. A deeper history is created if the user tries to view an older time period on the chart (by scrolling it back or accessing it from an MQL5 program).
The history of one-minute bars of a synthetic instrument is calculated based one one-minute bars (not ticks) of instruments used in its formula. For example, to calculate the Open price of a 1-minute bar of a synthetic symbol, the platform uses the Open prices of symbols used in its formula. High, Low and Close prices are calculated in a similar way.
If the required bar is not available for any of the instruments, the platform will use the Close price of the previous bar. For example, three instruments are used: EURUSD, USDJPY and GBPUSD. If in the calculation of a bar corresponding to 12:00 the required bar of USDJPY is not available, the following prices will be used for calculation:
If the minute bar is not available for all of the instruments used in the formula, the appropriate minute bar of the synthetic instrument will not be calculated.
Drawing New Minute Bars
All new bars (current and subsequent ones) of the synthetic instrument are created based on generated ticks. The price used for building the bars depends on the value of the Chart Mode parameter in the specification:
What Operations Can Be Used in the Symbol Formula
Price data and some properties of existing symbols provided by the broker can be used for calculating synthetic prices. Specify the following:
Mind the calculation priority of arithmetic operations:
You can use constants in the formula:
You can also use in the formula all mathematical functions supported in MQL5, except for MathSrand, MathRand and MathIsValidNuber: Only short names are used for all functions, such as fabs(), acos(), asin() etc.
The CustomTicksAdd function allows feeding quotes as if these quotes were received from a broker's server. Data is sent to the Market Watch window instead of being directly written to the tick database. Then, the terminal saves ticks from the Market Watch to the database. If a large volume of data is passed in one call, the function behavior changes, in order to save resources. If more than 256 ticks are transmitted, data is divided into two parts. A larger part is recorded directly to the tick database (similar to CustomTicksReplace). The second part consisting of the last 128 ticks is sent to the Market Watch, from where the terminal saves the ticks to a database.
Now, this type of protection is available to all platform users. To protect your files, execute the following command in MetaEditor: Tools—MQL5 Cloud Protector. The only difference of MQL5 Cloud Protector from the mechanism used in the Market, is that the file is not linked to the user's computer. Protected via MQL5 Cloud Protector files can be run on any computers similar to common EX5 files.
If a symbol chart is constructed using Bid prices (as per specification settings), Bid High and Bid Low prices are shown for this symbol. If a symbol chart is constructed using Last prices, Last High and Last Low prices are shown for this symbol.
If Market Watch contains at least one symbol whose chart is drawn based on Last prices, the Last column is automatically enabled in addition to High/Low.
For convenience, modified entries are highlighted as follows:To save the changes, click "Apply Changes" at the bottom of the window.
The function accepts dynamic arrays of the same type and the same dimensions. For multidimensional arrays, the number of elements in all dimensions except the first one should match.
The same menu allows adding to program code files in the form of a binary or text array. Among others, you can transfer chart templates with Expert Advisors or indicators: insert your template in the program code as an array, and save it to disk then using the FileSave function. After that the template can be applied on the desired chart right from an Expert Advisor using the ChartApplyTemplate function.The update will be available through the LiveUpdate system.