Posts made by fxDreema

Mouse move... I noticed that it doesn't work, but I don't know why. It seems the code is ok

I can't find a problem, this is how expert advisors work.

Under "Tick" workfield everything happens on every tick, so when both conditions are "yes" at the same time, the logic continues to the next connected blocks.

Ready for testing. There is a category with blocks that appears when in "on Chart" workfield, these blocks are filters. To get some parameters (coordinates, object names) there is a new subcategory in Condition - Chart event data.

For the first request, for what period do you talking about? And how many timed in a bar the crossover should be detected - once, or more than once?

Little theory here: http://fxdreema.com/documentation/proje ... er%20works
For crossover you need the current price and some price from the past. This past price can be Close price from the previous M1 candle. Check "Price vs Indicator crossover" example in http://fxdreema.com/examples

There is a block named "Signals (flip-flop)" that is almost like "Condition", but little different and it can be used here I think.

For second request, some kind of memory should be used, and in this example (http://fxdreema.com/shared/9V8afS08b) I use Formula Result. When Formula block is used, it automatically creates a global variable (Result) that can be read and modified everywhere into the project. In the case, when the price rise above the variable, the variable is modified to the next level above (15 pips added). I used 15 pips because I prefer bigger values for backtest.

Very soon...

Yeah, I noticed that before And it is something that I think for.

For example... http://fxdreema.com/shared/XetCbtlTd

To go to the source code while using generator is something that doesn't make much sense. What you are doing is doing it whatever it takes, and that is very good

The reason why there is no indicators builder is that I was never interested in indicators personally.
These days I tried to make simple indicator to show me some statistic data... it's not that hard So I don't know...

I bet some people wants to see this local version with set price and serial number, because this makes it more available for cracking. But I prefer to look at this version like an optional version, child version of the mother web version, where both shares the same plan. Local version is like a copy of web version working on the local PC.

There is a simple logic like this that can be used:

A=0 (initial value)
Do next things number of times, so that every time X is different. In your case, do it 3 times for all the values you want to compare.
X=whatever
If (A>X) then (A becomes X)

At the end A will be equal to the highest X from all iterations.

This "Formula" block is simple and stupid, but it's useful. Something you may want to know is that you can use the same Result variable in more than one "Formula" block. In other words, many "Formula" blocks can work over the same variable.

So you can try this logic with Formulas again. Also, the result variable from Formula blocks can be used somewhere directly (for example in one of the input fields where number exists normally).

My example was is case the logic requires to do something when one of the values is bigger than others. If the logic says to only calculate maximum of 3 values, you may only need one variable that holds the value needed.

By the way when you connect 2 or more blocks one after another, no AND is needed. This is also the better way to do it because there will be no calculations after the last block in the chain that is false. In the case when using AND block - all of the parallel blocks will be executed. But if you like it visually, it's ok. Simple mathematics will not slow down today's computer so much

Picking up information in time A and calculating it in time B can be not needed, because you can get Open, Low, High, Close from any candle in the past, and from any timeframe. There is a Candle ID parameter, where you give the index of the candle needed. 0 means the current one, 1 is previous, 2, 3, 4...

Ahaaa.... so, maybe you are trying to do something simple than you think. I can say that this is the way it happens to me - whatever I want to make, I can always make it simple. But it takes a little time and thinking to do that. To make things simple is one of the hardest thing to do actually.

Because you are new, you can play with this a bit. It's free to try and it's enough. Basic things can be made with 6-7 blocks. Don't try to make something better than NASA. I think the best reason for this to exists is that it makes it possible for someone to try different simple strategies and also to train his logic thinking.

If you are working in MT4 and "Trade" event can help - it is possible to detect when some trade closes and then to close all others after that. Or anything like that.
Instead of flags, you can use Formula block to save some value for later use. Flags are more to be used to control the execution of the other blocks.

If this can help... http://fxdreema.com/shared/UM40c1A6b

These results can be used to compare them with something (using Condition), but unfortunately there is no strong functionality to work in deeper mathematical terms in fxdreema. Well, it is possible to embed MQL code to the project or to create custom blocks, but you have to understand programming a bit.

Check in Price levels in Condition, there is what you search for. Otherwise, the fastest method is to use bigger timeframe, if possible.

It's installed when fxdreema.exe and Data folder exists. Actually those files are only extracted from the installation archive, so the program does not exists in the list of installed programs.
I have no idea why fxdreema.exe does not want to start. I use 3rd party software to generate it, so this .exe is not my work.
You can try to run it from outside "Program Files". Or maybe you are running some kind of anti-whatever or hacking programs that causes it to not load.

Is it possible that Ask>=High[1] and Bid<=Low[1]... maybe, if candle 1 is smaller than spread. I was not able to see sells on my backtester.
When both conditions are so different that cannot happen in one time, connect them in parallel. In your case block 6 should be connected after block 5, not after Buy now. If both conditions can happen in the same time, using "OR" block is good to prevent blocks after conditions to be executed more than once in one tick.

seanmcgu, thanks for your opinion

When you are working under "Tick", blocks will be executed again and again for every new tick that comes - those blocks on the top level basically (connected from output to others and nothing connected to them). All blocks below are depending on the blocks above.

That is what an EA is all about - something is repeated again and again and again, and every time the EA checks some conditions (many times per second), and depending on those conditions it takes some actions. When it take new action, things changes and on the next moment conditions are different.

So, it's normal for some condition to be there on top level - it needs to be executed as frequently as possible (well, it depends on the condition, but there is always one on the top). "Once per bar" is something like condition+action, because it has internal memory that is changin over time. "No trade is running" is a condition. "Buy now" and "Draw arrow" are actions, and without conditions above to stop them, they will be executed as many times as many ticks arrive.

My Indicators -> Add new indicator
Then connect "Just pass" with "Levels tester (for indicators and more)" under "Tick" and load one of the buffers of your custom indicator. Carefully inspect what does the indicator returns as values.
About ZigZag indicator, I think it is not very suitable for use in EA