working with (Round Number Detector)
-
Hello fxdreema
How do I go about making the [Round Number Detector] reset after it gives a signal ,so it can give signals multiple times?? I need it.
-
I think people were asking me this thing before, but I don't know why. You want to be able to detect certain level, and then if the price is moving around it to detect it again? To reset it remotely from other block or what? But I don't think I will do that with the remote reset, because yet another block that is kinda disconnected from others... I'm tired to explain to people how such blocks work
-
Ah you see I intend to open trades from there when__ other conditions are met__.
Look at the example of the EA I just wrote, the BLUE and RED work according to the RND, but because you set it to signal ONCE per round number, all those places marked in YELLOW were ignored, I need it to avoid that.
May be you could add the option CONTINUOUS/ONCE in its parameters?
or allow the RUN block execute it again?
It will really help. If not I will have to find a way of making my own RND which would really complicate the project
-
Yes, but remember that the price can move up and down around the round level and cross it many many times, so it can't be reset all the time. There must be some limit. One way is to reset it after the price moves with N pips above/below the latest round level. Or to reset it on each new candle... I think this is what you want. I will try to add some options
-
I added one option to reset it after some % movement. You can try it. I actually changed most of the code in the block and I tested it, but as always I expect bugs and if you find some problem, report it to me
-
Ah Thank you so much
I will test it to see how it works.
-
I don't know if this may be the cause but I have an EA which I just built this morning that doesn't detect the round numbers anymore other than every so often. Could this be a problem that the block has been recoded?
I tried the desktop version that still has the old round numbers block and it works fine other than this issue that the originator of this thread was talking about. I am one of the people that need some sort of reset to happen as it doesn't repeat signals once orders triggered and closed.
Daniel
-
keydcuk, give me simple example that contains 2 or 3 blocks and tell me what is your expectation from it. I will check it and I will see what is the problem - this is the idea. Because when I see that someone says something like "doesn't work", I read it like "ak#ka#%khsga2171". It means nothing to me, exactly nothing.
Yes, I tried the block and it worked for me, but I always forget the details in this particular blocks, so I need more information of it's problems.
-
__keydcuk, give me simple example that contains 2 or 3 blocks and tell me what is your expectation from it. I will check it and I will see what is the problem - this is the idea. Because when I see that someone says something like "doesn't work", I read it like "ak#ka#%khsga2171". It means nothing to me, exactly nothing.
Yes, I tried the block and it worked for me, but I always forget the details in this particular blocks, so I need more information of it's problems.[/quote:3vf317i3]
Thanks for your attention as always. Here is my example which is a snippet of the EA I am working with
https://fxdreema.com/shared/rZStnNwed
Also I add screenshots of the test and comment on its missed open trades.
Daniel
......
Screenshot_1.png
Screenshot_2.png -
Fixed (I think). The problem was in some code optimizations that happen when generating the output code
