Posts made by richard96816

That Stop-Loss box can take input from all kinds of other fxDreema logic.

You came all the way to the Buy now block and skipped over all the good stuff.

Go back. Replicate your indicator logic in fxD and let it plug the right number in for you.

I think you have different questions to ask.

Good luck.

What did you most recently change?

Errors can happen when you enter your own code or put fancy stuff in the Adjust boxes.
fxD also has a glitch on variable and constant entry. If you hit certain punctuation keys by mistake they may not be echoed to the screen but are put into the output code anyway.

If nothing else works download the mql code and have Metatrader compile it. It will show the error and what line it's on. You should be able to figure it out from there.

Sometimes erasing the value of a constant, with a few extra taps of the Backspace key to remove any hidden characters, will fix it.

Good luck.

@isp00rt Doesn't the group# thing take care of this issue?

How do I get the effect of Once per bar and No position at the same time?

Thought I could just string them together, but Once per bar overrides No position in terms of allowing multiple positions to be opened.

Connecting Once per bar after No position doesn't do what I expected.

Once per bar is acting like it's at the top of the string of blocks even though its not.

Thanks

Comments can be added in the Buy and Sell blocks under 'More settings'.

I guess we need to see more of what you're doing.

Perhaps the Delay block will do what you want.

All tester settings the same?

Perhaps your data has changed.

There are examples on the web of RSI divergence. You might be able to convince the fxD 'Indicator rise' and 'Indicator fall' blocks to help you find divergence.

Good luck.

Maybe one of the 'Risk %' money management options will do what you want. They auto-size your trade according to risk. If you're trading small size it should work. Can't trade below your broker's minimum size. Otherwise you might want a minimum trade size option to go with the max size option (Volume upper limit) that's already there.

@miro1360 Thanks very much for the response. Your example looks interesting. Need more time to absorb.

Thanks!

Curl is an external executable, accessible with the ShellExecute function and dll. Usually comes with other good tools. Python will probably do the rest of what you need or Perl, etc.
Not sure what the latency will be, but you can probably make things work with those tools.
Using fxD's 'Write to file' to shoot your data outside of MT. Lots of tools for looking inside CVS files after that.
Various MT functions that go both ways too, accessible through fxD's 'Custom MQL code' block.

Done this with other platforms and tools in the past. Usually not that hard.

If I want to check that an MA is above the last five bars do I need to use five separate blocks or can I somehow do it in one?

Thanks!

If you set the stop loss to zero, you get no stop loss. Tester and Demo will happily trade it. Many times it will make you a profit having a nice wide (nonexistent) stop loss. Until it eats your whole account.
It's a very important, very easily missed mistake. A simple scaling or range error can end up with an unintended zero.
I usually add a +1 to protect from those cases, but that's not perfect.

Thanks

Perhaps this will help ...

https://www.mql5.com/en/forum/119063

Is it possible to add comments to checked options without using Constants?
That would make all the nice enums show through to MT's tester parameters with less confusing labels. Then testing would be more powerful, simpler and faster.

Thanks

I've seen several posts asking for help with closing trades once equity gets to a certain level of profit.

Sounds like they want to protect themselves from making too much money.

Why would that be?

@bgvulk said in Грешки при компилиране:

При последното ми проектче PerBar се получиха следните грешки при компилиране и не зная защо

Possibly undefined variables or constants. See if you've got all those names defined and no extra characters.

Might be nice to have the system sanity check stop loss settings. Probably not very common to set a stop loss of zero. There's an explicit setting for that anyway, if you do want it.