
Even Candles don't work on different timeframes.
It must have something to do with my onece per bar (H1) setting.
Within this no lower timeframes work.

Even Candles don't work on different timeframes.
It must have something to do with my onece per bar (H1) setting.
Within this no lower timeframes work.
EA works on a MT15 chart, so I assume the data is OK.
Played with candle IDs with no effect.
But what I see is, that I have a once per bar block.
It doesn't even work with a simple MACD.

What I want is once per current bar, check indicator of lowe timeframe bar.
How can I accomplish that?
I should have said that:
I tried Candle 1, with no effect.
But I got another idea, which I thought would solve it.
I have a "once per bar" block set to current for the whole EA.
So I tried to set the whole EA to M15 and connect to a "once per bar" block set to current:

But the the EA doesn't do anything.
I tried to have seperate "once per bar"

The EA won't start.
Hi,
I try to check an indicator on a different timeframe than the one the EA is applied to.
I thought this should be easy by just selection a different timeframe in the "More Settings" area:

But that doesn't seem to work:

I tried different timeframes, but it works only when set set to current.
Something obvious I'm doing wrong here?
Mic

This is an exact copy of a condition block.
One has a "cross width" parameter, the other not.
What's that?
Interesting, but I can't get it running.
A lot of compilation issues.
Don't know, whats meant, with compile locally.
If I can't change the trading rules ....
@fxdreema
You write about hundred times
to have a custom indicator rather than using an EA for a Job, a custom indicator should so.
So far so good.
But how?
Fxdreema has a nice click and build Usability, whereas a custom indicator needs to be coded.
Is it possible to use fxdreema building the logic and transform the resulting mq4 into a custom indicator?
Thanks, @moreirajbn!
Different kind of thinking.
I thought those things all traders do will enhance the chance, because of self-fulfilling prophecy aspects.
A resistant line is only a resistant line because a lot of traders see and respect it otherwise, it just would be a line ;-).
I'm kinda frustrated.
All strategies I tried are in the end not profitable.
I've looked at and implemented several strategies found in books or on the net, but as said before, none of them were profitable.
Played with SL and TP parameters, but little luck.
Tried several indicators (after getting known them, not just randomly).
I really would appreciate any comment on how you find and implement profitable strategies.
Thanks
M
Thanks for looking into it.
Building my own logic in fxDreema would be easy, the only thing I'm missing and I wrote this as feature request to fxDreema is "build your own block" functionality.
Otherwise you can't manage your objects so you keep view.
https://fxdreema.com/forum/topic/4328/feature-wish-sub-modules
I've read all the tutorials about custom indicators in fxDreema, but can't make it work with this indicator:
https://www.forexfactory.com/attachment.php/1375988?attachmentid=1375988&d=1393424334
It's a candlestick indicator signalinging different patterns.
In the color tab there are just 2 buffers, but I can't see how to get the information dranw on the chart.
I'm afraid, I can't get them at all, is this right?
Mic
It seems to be an issue of data.
It works with controllpoints not with full dukascopy data.
I'm not aware having coded #property strict.
... and when you say "code needs to be fixed" you are talking about your code
?
... and how can I set it to strict?
Smaller wasn't the right word.
I'd say more readable would fit better my need.
I try to structure the blocks, so I know, what's goint on.
A sub module would be really really helful.
I even work with pass blocks to omit line crossings:

Doesn't work for me.
What am I doint wrong.
tried:
+Varname@pips
+Varname@pips@
+Varname(pips)
+(Varname)pips
None of them seem to work.
It's not only visually, it helps structering the code.
For instance my harami detection, which I want to use in several EAs.
Today I have to copy them to every EA.
If I now want to change something in this detection, it'll be a mess.
I second your opnion, less is more, but this definitely helps to make it smaller.