Topics created by Dieter

http://fxdreema.com/globals/files/help_block.png - this one?

Ok, I have understand it.

Manny thanks... 🙂

Try with "SAVE" button, I will check what is going on... And sorry for that problem!

Adjust field. You can write there something like "+0.1"... what you put there will be added to the value of that operand, and you can actually see the result if you see the source code of that block (right-click and hit "Source code").
Status field - this will change what you see when you run the EA on the top-center. This place where normally it says "Starting..." and "Working".
Comparison field cannot be used to write something there, this is a normal html select (drop-down) field.

It's always better if someone understands MQL4 or MQL5 here on this website. Or basics of programming, no matter what language - I mean functions, definitions, variables, constants, statements, arrays... If you have questions about this, ask them.

Get this now: http://fxdreema.com/desktop

I hope it will work. Thanks for reporting that!

Thank you,

you have done a good work.
😄 😄 😄 😄 😄 😄 😄

I don't know, I don't pay so much attention about warnings, because they does not make problems... they are only a little bit annoying if MetaEditor is used, and that's all.

Ooops, for some reason I can't reach your email. Check your messages here in the forum.

The problems are not the warning messages.
The problems ist that with MT 4.00 Build 432 (31 May 2012) commpiled ea´s do not work. Build 432 is in combination with, Forwalktester, bird´s-Tick data site and tickstory very powerful.

I will stop the discussion here. I will solve the problems by myself.

It depends on custom indicators and also how they are used. Normally indicators should be fast, but I saw some slow custom indicators. Maybe their code is not optimized. Custom indicator is written well when it calculates it's value only for the last candle on every tick. Bad written custom indicator is when it recalculates all candles on every tick.

In EA, use the custom indicator when needed. For example, if the EA needs to know the value from custom indicator only once when the new candle is created, put "Once per bar" before the condition, so that the condition will be executed once per bar and the indicator inside as well.

Also, if you have to check multiple indicators in a row, put the fastest at the top, or the one that can make the condition to pass not so often.

Dear Fxdreema,

ich have no alert massage in the journal.

But with this discusion I have better understand how the fxdreema-tool is working (var, blocks, general idea). I have stoped the error and hope that the profit will be with the ea´s. 😄 😄 😄 😄 😄 😄 😄 😄 😄 😄 😄 😄 😄 😄 😄 😄

Thanks for the quick info.

In the competition I'll wait about a week to Information.
Very good service!

Best regards,

Dieter

Initially, yes, but it will depend on your specific conditions.