Ok, I will take a look later.
But now I have changed the connection from area 18 to area 19. It is now not only by a block to be run or be turned on but also a direct connection be a "Pass" block and this is also not working as I wrote above in my last posting. What is not working correctly now? After a "Close all..." block was run the "Pass" block shoud also run and the blocks afterwards.
Ok, but if there is a disabled "Pass" block it should run immediately after turned on by "Turn On.." block, right? Therefore all blocks behind the "Pass" block should be also run. An active "Pass" block is always running, right?
I don't really understand the difference between "Run blocks" and "Turn On blocks". Could you give me an example that shows their different application and where these blocks are not interchangeable.
Wounderful! Normalized block ID's without any "sideeffects" in EA's properties.
Apart from the above I have connected the "Pass" block directly. In that case the "Pass" block and the blocks afterwards are forced to run after one of the "Close all..." blocks was activated but that was also not working. I belive there is a problem with the output of "close all..." blocks in area 18. The button is always executing the blocks afterwards correctly. Could you look over, please (just the logic/syntax/code).
my last question is obsolet.
It seems there is a problem with one or two blocks. Take a look on my EA ...v2.8 There are two additional areas (18 and 19) rimming the relevant blocks. Area 19 and below blocks should be executed after blocks in area 18 were executed.
The behaviour is like the "Turn On..." block is not executed and therefore the "Pass" block is not turned on. The funktionality in area 19 and below is defititely working because the button in area 19 is executing correctly but not the "Pass" block in area 19. Could you look over please.
I have no idea why the "pass" block is not executing the blocks below like the button is doing. The enter connecting points are the same.
regarding block MACD divergence:
couldn't you make selectable what kinde of divergence should be used (classic divergence or hidden divergence or both of them).
Couldn't you make controlable/adjustable when a divergence is confirmed.
Well, I allways try to explain "things" as good and clear as possible but "things" are sometimes complex and very special. But it is ok I am quite satisfied with my progress in developing my EA. I will change my browser and will use chrome now. I am also using mt4 and Windows 8. Maybe there was something happend to firefox...
By the way, I am surprised about the high klicks (3400+) on our/my thread, are you refering to some questions to not to answere the same question again and again? It's definitely not me and I am the only one who is developing the EA.
these blocks were from my v2.8_backup. Deleting these blocks, removing some previousely added and klicking in history to undo the changings was leading to v2.8_wrong. Repeating that was not leading to EA's wrong behaviour this time. Ok, lets call that a mystery and hope that doesn't happan again. I better don't touch history. I still don't feel comfortable with that.
Don't misunderstand me... you are doing a great job here and fxdreema is a very helpfull product in creating EA's.
I don't know everything I have added and deleted but the wrong-appendix version should not contain the following:
blocks: 11205752 - 11205754 and 11205743,
constants: ma_period and increased_lot_factor,
variables: buy_lot_factor and sell_lot_factor
But the point is why could that happen? There is no visible deviation between v2.8 and v2.8_wrong.
The strategy itself is irrelevant. The point is that adding and removing funktionality (blocks ect.) is leading to not expected EA's behaviour or in other words said: if I add blocks and variables and remove them again it could happen that the EA has different functionality as before the modification or some not used var/cont are not deleteable. There is a kind of instability and this is not good for big projects.
The point in my last posting is that the two mentioned versions are visually (blocks, variables, ect.) the same but the wrong version has a different functionality. Before the update there were not problems at all.
I have managed to make the "Grid-EA semi-auto v2.8" working correctly with the functionality I wanted to have.
Now regarding the blocks, variables and constants "Grid-EA semi-auto v2.8" and "Grid-EA semi-auto v2.8_wrong" are the same but "Grid-EA semi-auto v2.8_wrong" is still not working correctly. You can compare these two versions to finde out what is wrong with the wrong-appendix version.
Do you have an Idea what is leading to that behaviour variables, constants are not deletable and deleted block are still working in the background. Before the update I could add and delete everything I wanted and there were no problems.
p.s.
I have to admit that I was clicking arround in the history before the correct fuctionality wasn't given any more. But "visually" "Grid-EA semi-auto v2.8_wrong" is correct.
It seems there is a seriouse problem with deleted blocks and variables/constants. It happenes again: already deleted blocks, constants and variables are "not existing" but still working and some variables and constants are not deletable.
I am using firefox if this is relevant.
Could you look over please (Grid-EA semi-auto v2.8_wrong and Grid-EA semi-auto v2.8). I didn' t have any problems before the update. What is the reason for that behaviour?
It seems replacing constants (maybe variables, too) is not working correctly.
I have changed the constant "buy_grid_tp_money" into "grid_tp_money" and than replaced "sell_grid_tp_money" with "grid_tp_money". There should be only "grid_tp_money" and no blocks with "sell_grid_tp_money" but I can't delete "sell_grid_tp_money" because there are still blocks with that constant what is not true because these blocks are already changed.
Could you look over please (only Grid-EA semi-auto v2.8).
It seems "edit titel" of blocks is not working correctly. If blocks name is extended to two lines, it is not possible to edit the lower line after reopening "edit titel".
In a similar way EAs idendify their trades I would guess. But it's ok for now. I have to think about that issue. maybe I will find a solution for my EA. Thanks so far.
That looks good but what if I am using the same EA simultaneously on different markets on the same mt4 programm /terminal? I need the global variables working for each EA and market. It is not helpfull if global vars are the same for all EA's and markets. Each EA is running on a different market and lot-size calculation is also different.
well,... is it possible to save values of variables and restore them after mt4's restart. What have to be done to make that?
variables are used for lot-size calculation, average price, ect. . Variables are using for lot-size calculation are the major issue, these variables I would like to have stored/saved before restart mt4 otherwise lot-size calculation is starting from begining. If I could do something, please explain how.
Is it possible to save current values of all variables and restore them again after mt4 restart? If not could you make "something"? In case I have to update a current running EA on live demo/cent account I am always "loosing" all variables and this is changing EA's behaviour for the future.
It seems everything is working again. Thanks.
The group-number issue still exists. You don't have to fix all older versions of my EA but I need v2.5. There are still manny errors like " 'group-number' - name expected ". Could you fix that, please.
The properties issue I will verify when markets are open again.