Topics created by Trader3487

I am trying to test whether this ea recognizes different timeframe outside of current timeframe of test. I am trying to test for the crossover of ma20 and ma50 that occurs on 27-february-2013.

The test you gave me before that prints uses an indicator tester block to print the daily high no matter what timeframe the test is run under works fine. I also know the fxt files I am using are accurate because if you run the following ea on the D1 timeframe, it draws the veritical line at 27-february-2013 00:00. But, if you try running the test on H4, H1 or M15 timeframe, it draws the line several days later on 3-mar-2013 20:00.

http://fxdreema.com/shared/yu9M1JHxc

The test works on mt5 but I can't get it to work on mt4. I am using tickstory data. FXT file sizes are less than 1GB.

Any ideas? Thank you 🙂

mt4 with tickstory data.jpg

mt5 with exness data.jpg

......
mt4 with tickstory data.jpg
mt5 with exness data.jpg

Well, this block does A-B and compares this to C. The time is in it's own format - seconds from 1.1.1970 - and you can for example compare Candle Time [0] (or the current server time, notice that Candle Time does not change in every second) with another Candle Time that you have it in a variable. Again, this is measured in seconds, so foe example 1 hour is 3600 seconds.
If this function can also help: http://docs.mql4.com/en/common/periodseconds

ok, I understand - no pressure. I was referring to text (http://docs.mql4.com/en/constants/objec ... t/obj_text) - being able to print any text, including "this is example of text" over the candle. Would be a nice feature to have but not critical 🙂

Tickstory does support mt4 600+ via this link: http://www.tickstory.com/files/tickstor ... 1.3RC2.zip
I've also noticed improved performance in the new mt4 release, especially in compiling mq4 files.

Thanks for the tips - Ramdisk sounds interesting 🙂

ok, I can understand the code but am not good at writing my own (yet). That would be a nice feature for the future - same idea as with markets but with groups 🙂

beautiful, thanks!

I think this is because MA also goes up/down when the price goes up/down and the crossover extends itself. Maybe Once per bar can help? Or maybe some tolerance.

figured it out - I had illegal character "/" in title of file

Uploaded

great, thanks - I'll check it out next week (I figured out a workaround using about 100 blocks but your solution would make it a lot cleaner!)

great, thanks. I understand loops from the last conversation 😉

The mistake is that it does what a custom indicator should do, but EAs are not really the right place to do Indicator's job. You can see in the code how much stuff is in there and how complicated it looks - it's because of that. And I also think the performance is lower in this way. These blocks was some of my ideas that I wanted to try, and because I am not an indicator guy... this is the result 🙂

another (similar) practical application of this feature that would be really useful - if there was a "New new top in trend" or "New bottom in trend" in the previous bar (or previous n bars), then execute orange output.

ok thanks 🙂

Sometimes I play with fxDreema trying some simple strategies, mostly for fun. The history data is crap, but what can I say 🙂

yes, that's the one - didn't recognize it. thanks 🙂

Last days I updated the documentation about indicators.
Here: http://fxdreema.com/documentation/getti ... indicators
and here: http://fxdreema.com/documentation/proje ... indicators

I noticed. I will fix it, but I think the example was something simple, not very important 🙂

MA3 x< MA5 checks two conditions inside, one of which is MA3 < MA5. If you want to check if one of your block conditions are true and continue, then that crossover condition is not needed there, at least in the example on the right. In this example you can have moments when 1708 will be executed twice per tick because both conditions are true at the same time.

The example on the left.. this separates crossover moments from the general condition (MA3 < MA5) that is true in both conditions. But as you connect outputs to the same block, it is the same as you use only MA3 < MA5.

Here see more about crossovers: viewtopic.php?f=2&t=2290

@goldis No it won't, easiest way is candle cross on 1 pass, if not connect yellow to another condition, if yes pass, if not check 3, etc until all candle numbers are checkd.