Topics created by monsterfly

Thanks for the detailed explanation. The block flow is fairly straight forward and making sure any particular block has access to an available variable is exactly what I am trying to do. Manually placing the code for my object description find in the int start() and making sure the variable is declared seems to work for what I am doing. Of course being able to define the variables in a custom block and select which ones would be global would be a nice feature. Anyway, thanks again for the explanation.

The wev version is just what it is, always the latest revision. There are no versions for it, it's just a website page that looks like desktop application. The desktop version has some build numbers, but my idea is that everyone should work with the latest thing available. I have only 1 head and I just can't think and support old versions.

When I do changes, I have some scripts that will automatically update the project you are loading to the latest state, if necessary. When I decide to remove some block, I only hide it and it still works, but a warning message appears for that project.

No. Such thing would require arrays for remembering the state for each frame, but in "Once per bar" there is only 1 memory value that works in general. It's not impossible for "Once per bar" to be modified, but as a result it will start to work slower and this is something I don't like. Unfortunately in MQL4/MQL5 there are no associative arrays to make things simpler and I don't know how to easily work in scenarios where associative arrays would work fine.