I had this idea, to add some option to collect the time each block uses to work. Well, it was not that simple when I started doing it. I think there was some problem with the speed of execution of a single block and the precision of the function that returns time (GetTickCount()). As I remember, a single block passes too fast to be detected by this function.
Aaaaaaa, so you mean something different = to automatically export the EA every time new action is made. Because to save the project (for me) means to save changes to the database, not to export files.
Ummmm... I don't know, I never thought about that, never needed it. I think I will not make it for the web version because this action requires some CPU power. Not much for 1 person, but on the server there are many and who knows. For the local version it's ok, but I don't know 
It's not that way even with MetaEditor, you have to compile it every time, at least to check if there are some errors.
I was also confused of how trailing stop works before
This checks where SL is and moves it when it's needed. It does that on every tick, for every trade independently.
Tick comes -> Work with trade 1 -> Work with trade 2 -> Work with trade N
So because of that it should be placed for example with "Pass", to be executed on every tick. Normally, this is not must, because sometimes you may want to use trailing stop A in some hours and trailing stop B in others.
Trailing stop parameter = at what distance SL line must be kept. X pips away from the current price or other option. Dynamic level is when you use some indicator, like MA, to follow it's line. Dynamic pips is when you want to use custom value for pips.
In other options there is "Function value"... it's the same, I have to rename all to "Custom value" actually
Trailing step parameter - how often to update Stop Loss, if this is 0 it will be updated every time when needed, too often, so your broker will not like you.
The rule is, for Buy: When Ask > SL+TrailingStop+TrailingStep => Move SL to Ask-TrailingStop
Trailing Start parameter = if you want to wait to profit with some pips and then start trailing stop.
But you probably hit those buttons after you make some change that adds new step in Actions History, I can't find some good reason to make those button to also create Actions Histoy point or something like that, they are just like "let me try how the EA works as it is now".
Well, there are some actions that are not saved right at the moment, like moving a block to a new place, but this is mostly because I was not decided to make that possible (the idea is to not put much garbage in Actions History). And also for the web version sometimes an action can be missed because of network issues. But in the local version... why export buttons should create history point if it is already there (most of the time, the most important actions)
Well, it is saved when you do some action that adds something to the Action History. I'm thinking sometimes to remove those two big buttons, as they were used for some reasons before the Action History was fact, now their role is... let's say not as big as they looks like. But they are sweet and I like them to be there
I can see you are using 1 as start candle in one place in block 3... if this could be the problem. I tried (with 0 instead of 1) and the result is this: http://prntscr.com/33oivs
And the same goes for the last MT5 version
But here is a quick fix.
For those who understands russian: http://www.mql5.com/ru/forum/21374
English: http://www.mql5.com/en/forum/22148#comment_803835
Download one of these files and put it into the MetaTrader installation. No .dll is needed, and those should work for MT4 and MT5 as well.
I will probably include those into the next fxDreema local version, so if no compiler was found - to use what's available in it. This is how the web version works actually, it uses compilers on the server
Hm, bad news. It looks that the problem is now true, it's not a bug... unfortunately Because the problem is that they included the compiler into metaeditor.exe and it's not standalone .exe. Before build 600 it was metalang.exe, after build 600 it was mql.exe (and mql.dll) and now it's gone. Here is a little bit more information about this move: http://forum.mql4.com/61609/page2
To be honest, I don't know what will happen now. The compiler was a simple DOS program that was able to be used from external programs (like fxDreema or Forex EA Generator) with simple CMD (command prompt, this black DOS screen that shows only text) commands. Now I guess it's possible to use old mql.exe/mql.dll if you have them from older installation, at least you can try. But I think at some point .ex4 files generated with this last standalone compiler will stop work in MetaTrader 4. I can also include this old compiler into the local version, but again... the same will probably happen.
If at some point MetaQuotes decide to completely cut off the usage of their compiler from external programs, then EA generators will no longer work for MetaTrader They do stupid things sometimes, I will not be surprised.
I will tell this again - I don't understand what you want to say! I hope Google will translate this to you correctly. Again, I don't understand your words. I don't understand the meaning of your sentences. Yes, it's only few words, but they are not placed in order that I can understand. I understand each of the words, but not the whole sentence.
if anyone else can help... I just don't get the questions
Which version, and... because things can be quite complex depending on the Windows version, by reading here can you find something that causes this problem: topic/2374
I mean... now that I'm trying to export .ex4 file it works for me, so I need more information about the problem.
So, pending orders in time instead of price. I started thinking how can I do that, probably in blocks "Buy pending order" and "Sell pending order" with another options that makes it possible to delay the order with time and to execute it as a trade at the price whatever it will be in the future. But I'm still not sure about the consequences of this approach, because another blocks (like "No pending order exists") must be updated as well, and some driver needs to be added to detect the time to react, which will also slow down the backtesting a tiny bit.
If it is a block like "Delay passing" which will allow the EA to continue working, then some more problems will be on the table, because there is no context here, it's something general. For example you can have "No trade is running -> Delay passing -> Buy now", but how will "No trade is running" know that we expect "Buy now" to be executed after some time? It will just continue passing and executing "Delay passing" over and over again, which will create multiple delays for the same thing and at the end we will end up with multiple "Buy now" executions. Again, this is in the general case when "Delay passing" is not aware what it controls.
Because of that, and because it looks a little bit fancy (and who knows if others will need it), I will ask you for the exact situation that you want to work on. It happens very often someone to ask for A, but to want to achieve B that does not actually need A. And sometimes there are various ways to do something. So, with what time do you want to delay the signal? You know... if we talk for indicators only, and the signal you want to delay is something like 1 candle or few candles, then you can just check past candles for that signal and react at the moment, this is how things are done normally
No, as you already know there was not big interest in this part of fxDreema. And unfortunately there are always some buggy behaviours in the local version because of the software that I use to generate it. Their last version was more than year ago and there is nothing better than that. So you probably see some flashes when opening the studio, missing title on the taskbar, and maybe it will freeze with no reason sometimes.
It's much more stable on the web version and I work there. Well, I'm working on the web version all the time and on the local version just to check if something has failed on it :)))
By the way this is how it looks for me, if you are curious: http://prntscr.com/33658v
I just reuploaded 078 with some fixes, you can try it.
I had an idea of a block that when executed once, will remember to execute the next blocks after some time. But I suspect there is something missing here and I'm not sure this is practical. For example if you delay "Buy now" with 5 seconds, and then when the event will happen - in the beginning of some tick just before other blocks blocks to be executed, or after some of them, or after all of them, or on the exact place where the block is.
Why do you want this actually, maybe you are trying to fix something that can be fixed in another more appropriate way?
There is a special option for backtesting, normally it doesn't work for backtesting because the time is not real when you backtest. But there is an option anyway, it needs to allow dll because it's something like a trick. If you want the delay to see things more clear in backtesting, look for that words "When backtesting..." in that block.
If you want something else... probably describe how it should work?
Uuuummm... this Google Translate... sorry, I don't understand the question 
It works for 1, 2 or 3 word at a time, but more than that... it's crap.
I think I told you, write your question as steps, 1) Do that, 2) Do that, 3) Do that, where "Do that" is something very very very very simple, like "Open tade", "Set SL to 10 pips" or something like this.
There are some things to be considered...
Input parameters should not be entered, they are automatically created depending on the input parameters you create on the right side. Use ~next~ where it should go to execute next blocks and ~inext~ if you want to have yellow output. Always use 1 ~next~ and 0 or 1 ~inext~, it's not that more than 1 can't be used, but it's better to be 1.
I can suggest to write something, save, and see what code is going out of the block. Notice that when you save it, it does not check for errors, I was always too lazy to implement this, but I'm using this Studio and it's enough for me and obviously there are no many other people using it, so... I imagine that I'm the only one that is using it :)))
There is a block "Delay", it actually stops the EA for a while at that moment. if this is the idea...
Someone is using this! 
Hummm... is it working if you don't click there, probably links are not correct, I always have problems with the program I use to generate this local version.
The word "position" is mostly used for MT5, in MT4 those are not really positions. What position is - this is when you mix all trades into only 1 for the given market (symbol). A position is always 1 per symbol.
if this can help: http://fxdreema.com/shared/VYGzSz5ee
But be sure that you understand how these pink blocks work, because many people find them confusing, I think they are not too complex and they are much flexible. So read the description of "For each Trade". This EA works even without block 3, but I always recommend this block to be there.
I think it's better to use pending orders. And those groups... use them in case you have strategy with limited number of groups of trades, when each of these groups is designed to do different things, different logic, like if you have multiple EAs at the same time. If each trade has to follow the same logic as the previous one, then don't use groups, then command each trade the same way as the previous... similar to what I have on the right side where blocks 5, 6 and 7 are.