Topics created by edwardseer

095 https://fxdreema.com/desktop

Flags are similar to Variables. You can't display their state and I don't remember even thinking about this, but this is a good idea. Where to print such information is another question 🙂 You can try this "Change Status to" thing that each block has.

Yes, in "For each Trade" you can put multiple Group numbers, separated with comma, like this "1,2,3". This also works for market names.

If you use the Comment attributes of trades, note that if you have SL or TP and the trade is closed by SL or TP, some information can be appended to the comment by the broker. For example [sl] or [tp].

yea its easy to understand this part with the documentation. i added this to my project. its better than my current method. haha something new learned 🙂

ok 🙂 was wondering which 1 to use as its a default indicator not a custom indicator

ya 😐 Sorry to bother you on that ><. Thank you.

It looks that this error is produced by the indicator. Make sure that all parameters are right and in order, but if they are... I don't know, indicator bug

Which project is this, Genesis?

I'm also not really sure what is going on in this case , I never even tried to look it closely. This looks to be the only way of doing this, here is the function to close trades fully and partially: http://docs.mql4.com/trading/orderclose When a trade is closed partially, it is kind a special, you can tell that this trade was a result of such action because it's Open Price (if I'm not wrong) is the same as the one from the original trade. But the new trade appears as unique in the other parameters, including ticket number. That's why I wrote that this trade is brand new. It's brand new, but also a result of OrderClose(), not OrderSend().

Not easily. The Comments that you can see now on the upper left corner of the chart is native from MQL4/MQL5. I will do something about this eventually, because people are asking questions like this from time to time, but now it's only the default Comment. Also, you can always create some Text objects here and there.

At least this was my idea. This is like a snapshot of the project, but it also works as a project.

ok. managed to get what i wanted doing this
https://fxdreema.com/shared/zd6iwLeOb

No problem. Wasn't expecting a 1 month bonus as it is still an awesome product to me 😄 . Thank you.

Hopefully this problem can be resolved after you finish the rewrite process.

I removed that cache now, otherwise I need to make the code even more complex, which is something I don't like. So I don't know, maybe I will turn it on again if someone decide that the block runs slowly.

Anyway, does it work now? I have blue lines here and there, but I have no idea what should I see 🙂

ya just thinking it would be a great addition to this software as its own block

Ok, but do you really need all those variables? Maybe there is a simpler way to do the thing that you want to do.

Otherwise for what you have now, I imagine using arrays. But using arrays is easier in plain code and hardly possible with using blocks 🙂

You can use "Red" or "Blue" only because these are predefined constants in MQL4. They contain some numeric value, I don't even know the values for each color and this is not important.

Here is a list of all colors: http://docs.mql4.com/constants/objectco ... /webcolors
Now constant names officially start with "clr...", but names like "Red" and "Blue" are still supported by MQL4.

Go in your fxDreema/Data folder and find somewhere... MQL4/indicators/
Inside, there are files that represents indicators that you have added. One of them is the broken one, just delete it.

hi, its a minor bug but i do not know if this will be a recurring problem but just now the condition for cross above/below would not work for one of the two conditions i set and i realised that for the cross above condition that did not work, the cross width was not there while the other had the cross width.
I tried to create new condition block, but the new condition block did not have the cross width for that condition.
However, the problem was resolved after a restart of fxdreema though.

i got it working thanks. 🙂 its for when initialising the ea starting parameters.
im currently using that 2 buffer variables method for the on ticks section.
it would be great to have this as a feature next time though .

But it should not do that. I guess you are working with the local version. If this EA is not a secret for you, send it to me so I can check it, and tell me what to do, so I can replicate the problem. My MT4 build is 765