Undeclared identifier

[Babago]

Can you please help me to use this indicator on FXdreema?
When i compile the EA it gives me this error "Undeclared identifier"
is the only indicator that gives me this error.. also if i tried with Indicator Tester..

Thanks
Dave

......
GMTS-Tape.mq4

[fxDreema]

It uses datatype which is defined in it - ENUM_NEXTTF. You can define it as int with default value of 0, which is Disabled. Also, for some reason fxDreema does not detect it's 4 buffers, so add them manually. This is what it should be: http://prntscr.com/40i7tk
Buffer names are optional, I defined them as the name of their colors.
I don't know how this indicator works, it is also very slow and heavy on my system

[Babago]

Thank you, it resolve the problem!

Can you check please why i can't set boolean parameters with constants i created?
i would like to set, for example, "forceconsecutive" with the "Forceconsecutive" constant..
but it not save the change
i also tried with integer 0-1

https://fxdreema.com/shared/rpJ6VjAM

thanks

[fxDreema]

Ummm... I think it is saved but then it does not appear as saved... bug

I don't know when I will fix it, so for now I can give a workaroud - define this parameter as "int" and use 0 and 1. Integer is compatible with boolean.

[Babago]

Yeah!!
Thanks again sir!

[Babago]

Probably i found another bug..
i tried with a lot of configuration but

1. "indicator rise" return always false
2. Both Rise and Fall seems not respect the parameters of number of candels

https://fxdreema.com/shared/vgSonh6S

Can you check please?

[fxDreema]

The current candle has ID = 0. The previous candle has ID = 1. The next one is 2, then 3, 4, 5....
Candle with ID = -1 does not exists

[Babago]

Oh sorry! I forget it!
Forgive me, really!

Can you help me to understand this other problem?

I have several indicators that create this issue
https://dl.dropboxusercontent.com/u/492826/Schermata 2014-07-10 alle 02.34.46.png

It's like they open several times when they are loaded and condition is valid..
Instead seems they are opened and closed when the condition is not valid..

This is an example of what i found in the journal

Condition not valid
2014.07.10 01:21:21.238 2014.04.09 23:25 Custom indicator FlatTrend_Macd nmc AUDUSD,M5: removed
2014.07.10 01:21:21.235 2014.04.09 23:25 Custom indicator FlatTrend_Macd nmc AUDUSD,M5: loaded successfully
2014.07.10 01:21:21.228 2014.04.09 23:20 BABAGO BACKTEST AUDUSD,M5: FLAT TREND NON VALIDA
2014.07.10 01:21:21.201 2014.04.09 23:20 Custom indicator FlatTrend_Macd nmc AUDUSD,M5: removed
2014.07.10 01:21:21.197 2014.04.09 23:20 Custom indicator FlatTrend_Macd nmc AUDUSD,M5: loaded successfully

condition valid
2014.07.10 01:25:45.063 2013.05.08 02:25 BABAGO BACKTEST AUDUSD,M5: FLAT TREND NON VALIDA
2014.07.10 01:25:45.052 2013.05.08 02:25 Custom indicator FlatTrend_Macd nmc AUDUSD,M5: loaded successfully
2014.07.10 01:25:45.033 2013.05.08 02:20 Custom indicator FlatTrend_Macd nmc AUDUSD,M5: loaded successfully
2014.07.10 01:25:45.017 2013.05.08 02:15 Custom indicator FlatTrend_Macd nmc AUDUSD,M5: loaded successfully
2014.07.10 01:25:45.001 2013.05.08 02:10 Custom indicator FlatTrend_Macd nmc AUDUSD,M5: loaded successfully
2014.07.10 01:25:44.982 2013.05.08 02:05 Custom indicator FlatTrend_Macd nmc AUDUSD,M5: loaded successfully
2014.07.10 01:25:44.968 2013.05.08 02:00 Custom indicator FlatTrend_Macd nmc AUDUSD,M5: loaded successfully

When i run backtest without visual mode they starts to skips trade or, sometimes, after a while, backtest stops and in the journal i found "invalid ex4"...
Probably due to the big number of indicator loaded, in fact the ram fills up to 4gb when usually it's around 1gb..

This is one of that indicators..
https://dl.dropboxusercontent.com/u/492 ... %20nmc.mq4

Probably i have to modify some code in it to prevent this problem?

Thanks again,
have a nice day

[fxDreema]

I can use that indicator with no problems at all: https://fxdreema.com/shared/LvrioUY6c
I use the same indicator with 2 different settings here, so 2 indicators appear on my list after the end of the test, as expected.

I don't remember what caused indicators to reappear, I have seen such a thing before, I think in MT5. I need more details - the project itself? Maybe checking the same EA in another MT4? How another custom indicators behave?

[Babago]

Ok i found the problem!

your example version works well on my MT4
so i gradually removed everything from my EA leaving only the indicator...
and discovered the problem was in the constant i used in the timeframe field.. i set it as integer..
but make it as text solved the problem!

Hope this can help someone else..

Thanks for your time
Dave

[Babago]

__Ummm... I think it is saved but then it does not appear as saved... bug

I don't know when I will fix it, so for now I can give a workaroud - define this parameter as "int" and use 0 and 1. Integer is compatible with boolean.[/quote:5jqo8r32]

__Ummm... I think it is saved but then it does not appear as saved... bug

I don't know when I will fix it, so for now I can give a workaroud - define this parameter as "int" and use 0 and 1. Integer is compatible with boolean.[/quote:5jqo8r32]

hi,
i'm facing with a lot of problem due to this bug..
trying to reproduce it you can see it here

https://fxdreema.com/shared/l5JA69Tjd

when i set as timeframe of an indicator or what else a constant like "MyTimeframe" in that project
and update the block and save mq4 file everything is fine.
If i open again that block and don't update again, constants remains saved in the mq4 even if are not visible in the block in FxDreema.

But now i realized (after an entire month of work )that after change any parameters of that block and update it i lost all ore some constants in the mq4 file.

The only way is to remember all the constants i use in blocks and re-insert them every time i update a block.

Unfortunatly in big projects it became a big issue to remember all of them
and all my backtest have to run a second time..

This happens both on Local and Web versions.

Are you thinking to fix it shortly? I don't want to make you any pressure!

I ask just to know if i have to found a new way to solve the problem like correct the code directly in mq4
or can i wait for your fix.

Thanks again for your help!!!
Dave

......
Schermata 2014-08-07 alle 14.28.53.png

[fxDreema]

Oh, I forgot about this one
Fixed on the web version and reuploaded as build 086. But be careful with these select values.

[Babago]

Thank you!
I'll check them carfully

Have a nice weekend
Dave