Posts made by fxDreema

Аз пък си мисля за Open на свещта

Добре де, представи си че работиш не с 1, а с 10 поръчки в момента, значи ако искаш да работиш с Open ... с Open на коя от всички ще работиш? Програмата трябва да знае с Open на точно коя поръчка да работи. И има в Condition такъв параметър - нейде из (in loop) групата. Само че в тоя случая е добре да се ползва For each Trade, че тоя блок зарежда поръчките една след една. Е, ако е една поръчка - зарежда само нея. Но по принцип в МТ4 нещата са направени с мисълта за много поръчки в един и същи момент.

Пробвай "Indicator tester" или някой друг блок дето да визуализира данни, ако се чудиш как да хванеш Open на даденото място в стратегията. И когато МА се пресича с нещо което е просто стойност (няма различна стойност за предишен бар), тогава пресичането е:

• За x>: MA[0]>стойност И MA[1]<стойност
• За x<: MA[0]<стойност И MA[1]>стойност
  така че самия сигнал би трябвало да работи.

SL to fractal level, then break even, then trailing stop?
I think it's not needed to use both, break even and trailing stop. In this way trailing stop will not affect the trade until some profit reached: http://fxdreema.com/shared/D5xBmxQFd

One true/false parameter missed in the middle. Now I can recomment to define that indicator in "My Indicators", It's now possible to manually set it up

With blocks - Condition and Formula blocks. Or Conditions and Variables. This can be also written as source code if you create custom block. Something like this...

calculations, calculations, calculations...

if (certain condition) {~next~} else {~inext~}

Here ~next~ and ~inext~ keywords are filled with data in the project, depending on what blocks are to be executed next (inext is for the yellow output).

I noticed, and I'm sorry for that. I will fix that, I don't know when because I just started again to optimize fxDreema's source code, but in any case you can manually create buffers and name them as you need. Check the indicator options to see how many they are:
http://prntscr.com/25u3k0
And some information can be also extracted from the indicator itself. There is a row "#property indicator_buffers" that tells the number of buffers, and somewhere below they are defined with meaningful name.

Мисля че няма да стане по нормалния начин. Трябва да прегледам дали не трябват специални добавки към x> и x< когато се работи с Open,Close,High,Low. Но за да не те обърквам направо ще ти препоръчам да си направиш една или две Condition, така че да се образува необходимия сигнал. Примерно MA0>Open0 е едното условие, пък другото е... знам ли, там както го виждаш, ще да е MA1<Някоя друга част на предишната свещ, мисля че High или Low са подходящи, но Open понеже може да е от двете страни не ми се струва като добър вариант.

This indicator has 4 buffers, but they can't be detected for some reason... I have to check that later. But anyway, you can manually fill the data for 4 buffers - click on "new..." and write whatever you want to the input fields.
http://prntscr.com/25u3k0

Break even block loops trades inside, so normally it's not meant to be used inside loop (under "For each Trade"). Read the description of "For each Trade" to understand about loops.

Break even block, when executed, modifies SL of all (filtered) trades that are in profit in this moment. So I guess you can just place this block under the condition where you check the profit. If you mean the total account profit (equity-balance).

Design about what?
Here on the right is an example of trailing stop using loop blocks (blocks are now renamed, but you will get it): http://fxdreema.com/demo/mt4-9975

http://fxdreema.com/examples

Mmmmm... who knows what other people are using. But you should know how fxDreema works - basically "on Tick" causes blocks to be executed on every tick, and on every tick you check some conditions and you use some filters (which are also conditions) - and at the end you have trading blocks. So if you want to buy/sell on 2 different types of signals - no problem, just add some Condition and/or other blocks in order to filter out the signals needed.

If you ask me how to buy on signal and then buy on other signal that the same indicator does not detect, well... the same indicator can't be used. All indicators are just numeric values for the EA.

None of these require server calls (if there is something about MT that I am not aware of), they interact with MT only, and MT interacts with the server when needed - and this is when trade/order is created, modified, closed. Checking trades happens locally and it's actually fery fast, so I guess the EA reads temporary variables that MT updates when new event happens.

Indicators are very different. Use "Indicator tester" block to visually see what values some of it's buffers sends to the EA, so when you know this you will have an idea how it works. If everything is fine you can use "Condition" block to compare values or one of the blocks in "Indicators" category - they are like special versions of "Condition" block and works for most indicators.

There is an input parameter called "MagicStart" - this is magic number basically. But if in blocks you have Group number different than 0 (or empty), then that EA uses multiple magic numbers, because...

magic number = MagicStart + Group number.

The other way is to modify SL from time to time, every 1 minute for example.

Well, I don't trade and I don't have good experience with brokers to tell you what they like and don't like. But sending too many queries to any server causes it to not like you in general, so... make things in a way to not over-communicate with the server

Trailing step naturally makes it to modify SL not so often, because some distance (step) must be traveled, but if your SL is as small as possible, I don't see space for Step

When SL is keep so short, there are probably many error messages as well. I can suggest using Virtual stops, because something is moved, but it's not the real SL and at the end the trade should be closed. I never tested it with small stops, I don't know what possible errors can come out of this, but I guess it should work. Or use some kind of indicator or conditions to tell you when to close trades.

Just to mention, not long time ago, I modified trading actions so to try again and again if some action fails. There are type of errors that are "recoverable" and others are "fatal", and when recoverable error happens - it will try again, but if fatal error happens - it will stop trying. So the EA itself is going to push the broker to do what is needed to execute the command. If you detect some situation when the EA is not pushy enough and can cause the EA to lose money because of errors, please, message me.

This block is hidden. I decided to hide it primarily because it gives "independent" signals. I mean...it works for itself and does not care what is going on before and after it. The reason why I created this block was to cover that strategy where you buy-sell-buy-sell, but this can be created with trading blocks as well, and will be more accurate. With "Signals" block, it can give you a signal and then the trading block may fail, and this will corrupt the strategy.
Without Signals block strategy like this looks like:

No buys -> Condition -> Close sells -> Buy now
No sells -> Opposite condition -> Close buys -> Sell now

And you can see that here conditions are checked depending on what trades there are exists right now, and Signals do that no matter what trades exists, if any.

I'm also thinking about hiding "Formula" block Or to upgrade it somehow.

Well, I think this does not happen now, I removed that "bug" before and now I tried - "," is not converted into "."

I think so. You can always try it.

When you have error and after you remove somthing the error is still there, this simply means that this thing that you removed does not produce that error, it's something else.
Check that formula with MarketInfo above, it has "." where it needs to have "," - just after Symbol().