Posts made by fxDreema

It looks that some loops broke when I enabled strict mode. Can you tell me which block makes this problem?

This was another problem in For each Trade I expected that "strict" mode is responsible only for the syntax, but it looks that it does something while running.

Well, I guess you can always put some EA to backtest and see what is going on in Journal

http://prntscr.com/9cbvlc
http://i.imgur.com/A6bemm3.png

If you don't specify delimeter in "Send HTTP request", then the expected response is one single value, plain text. No key should be specified in Condition.

If you specify delimeter in "Send HTTP request", then the response should be like this "value1,value2,value3" if the delimeter is ",". In this case the response text is exploded with the same delimeter and it will look like ["value1", "value2", "value3"]. These values have keys such as 0, 1 and 2. No associative arrays here and no JSON.

At the moment I don't use such function. I remember that someone advised me to do it like this before, but I wasn't convinced do make it fact. Well, if you have such function you can use it. Custom function can be defined in https://fxdreema.com/studio and then used directly from every block. Don't try to modify MagicStart, if you do something, better do it with the Group number.

But if you add the same EA in two different symbols with the same magic numbers, this is not a problem because the default setting in all blocks like "No trade" are to work with the current symbol only.

You know what... I think it will be enough to use Group number as something like _Period. This is predefined integer variable in MetaTrader and is something like the function Period(). This will separate trades when the same EA is used in different timeframes. As I mentioned above, by default there is symbol (market) separation.

I guess you are talking for the last block on the list, but the last in each category or the last from all of them, which is "Custom MQL4 Code"?

Here are some extra options, but only for custom indicators. In my MetaTrader I can't find Fractals available as a custom indicator.
http://prntscr.com/9cbgot

Otherwise you need "for" loop where you can check each candle starting from the current one, break the loop when the right one is found and get it's data. This is how the last option in the screenshot works, but only for custom indicators. I have no plans to make these options available for each built-in indicator, because... because for now I don't want to put more options in each indicator.

It looks that there are more warnings than before, but in fact they are less. I just enables strict mode (#property strict) and I spent a day to clear warnings here and there, but probably some of them are still there. I forgot to check purple blocks (on Trade, on Chart...), it's probably because of them, but again - those warnings only appear because I enabled strict mode and the code that produces them is actually unchanged.

Strict mode is something that allows MetaEditor to print more warnings and errors and to be more strict about the coding rules.

It should be fixed

Maybe I missed some Print() somewhere.... what's written in those logs, is there some repeating message?

The error is not because those particular warnings, but obviously I made some changes and this error leaked. I will take a look and I will fix it

Oops, my fault! Yesterday I made some changes here and there, but it looks that without knowing I revert back to the old version of this function. Now it should be working.

Sorry, I made many changes yesterday and there can be some issues. It should work now. By the way you can use this as a data type for this constant - ENUM_TIMEFRAMES

I think it's obvious in Condition. I don't know what have you tried, but yesterday I made some changes in almost all blocks so there is a chance for something broken. You tried this and it doesn't work?

Малко е като електронна схема - https://fxdreema.com/shared/9po0PFDGb

Windows 10 again...

What is crashing is probably mql.exe, the original compiler that is used by fxdreema.exe and is located under /Data. Try to replace it with mql.exe from these links http://forum.mql4.com/61609#922370

Много зависи къде се намира "Once per bar". Ако е на топ ниво преди "Condition", тогава ще реагира на първия тик от свещта, иначе зависи от "Condition".

Сега ако настоваш за абсолютно точно време, т.е. да реагираш когато удари секундата на :00, тука навлизаме в едни интересни дълбини. Експертите по принцип се правят да реагират на тикове, то и няма смисъл от друго, щото принципно ако няма промяна в цената няма и смисъл от търговия. Не всеки път обаче би дошъл тик точно в :00. Въпреки това експерта може да се направи да реагира по време през този "on Timer" евент, обаче тогава възниква проблем с тестера. Първо, самата функция на евента OnTimer() не е направена да работи в тестов режим и второ, тестера си работи с неговите генерирани тикове и поне аз не съм успял досега да го вкарам в някакъв регулярен времеви цикъл. Просто като се пусне един while() цикъл в тестера и той замръзва в първия си тик.

Today I decided to clear some errors and now MQL4 files are generated in strict mode. Also because I optimized some code, now backtests are little bit faster (well, it depends what blocks are used)

By the way you can try to delete the hidden file named user_default in Data. I'm not sure that this will fix the problem, but who knows