Posts made by fxDreema

Is there error otherwise? I fixed some problem yesterday, but who knows, maybe another is introduced?

The idea is that when a global variable is used in block, and that variable is with the same name with some local variable for this block (each block is a function in MQL4), then the local variable is prefixed with this "l0ca1_" thing.
In your case, in the block is used variable named "GridStart", and you probably had Variable with the same name, so to not mix them in the function the one that is local is renamed everywhere in that function.

Because one counter is used to control multiple trades, for this array is needed. I think there is no way to do this with existing blocks, and I don't have some great idea which is the easiest way to do it otherwise, but I can think about it

На мен ми се вижда Price Mode да е нагласено на "Bid", общо взето както си идва по дифолт в блока

Somewhere in the middle, there is a search field also available

For a single candle I really recommend "Single candle template" block, it's somewhere in the middle of the list.

There is something wrong with Result names. If you use in "Formula" blocks result named different than "Result1" to "Result5" it will work.

In your block 2 I'm not sure you want to use "Global variables in MT4" on the right side, you want to use "Value".

Yes, my fault, something is missing for this block. I don't know when I will fix it, but for now I can suggest to use "Modify Variables" block, it is basically the same block with different name and color.

"TestGenerator" says what is the real format, the EA can't change it really, and this message appears before the EA. Inside the EA it uses this "0.01" format, but outside everything looks the same as without EA, and I think it's not possible to change that fact. Well, I never searched for a way to do it, so who knows.

This point format option is... if the word "soft" describes it? Calculations happens inside the EA so it works as it is with different broker settings - those that you prefer. The idea is also good because in this way the same EA can work in the same way with two brokers that have different point size for the same market... if my last words mean something

The mistake is that it does what a custom indicator should do, but EAs are not really the right place to do Indicator's job. You can see in the code how much stuff is in there and how complicated it looks - it's because of that. And I also think the performance is lower in this way. These blocks was some of my ideas that I wanted to try, and because I am not an indicator guy... this is the result

Or within a loop, there is example of this too. Just don't put "For each Trade" and below - "Trailing stop", because I'm so tired to explain how these loops should be not used

Hm, maybe I can add some option to grid blocks to snap orders to some round number, this will be good. Otherwise there is a block named "Round numbers detector" that gives 1-time signals when the price reaches new level. I think the orange output reacts on upper level and the yellow output reacts to lower level. Only I'm not sure if this block is suitable for orders

As I can see in the code it works with candles from 0 to PastCandlesCount-1, which is total of PastCandlesCount candles including current one.
Most blocks in this category does what custom indicators should do, now I consider this as a mistake, so use them if you want but I will suggest to use custom indicators if you have

As I said, in fxDreema these - Ask, Bid, Point... - are not used, so RefreshRates() is useless, because it controls them, but they are not used and there is no matter In fxDreema MarketInfo() is used and RefreshRates() has nothing to do with it.

It is possible that some calculation in some function is not correct, I don't know now. If you can inspect this it will be good (search for "OrderClose" function in the code and check it's input parameters), otherwise you can tell me the broker and the instrument and all that is needed for me to recreate this situation here.

And here are the limits of MT4: http://book.mql4.com/appendix/limits

I don't think it will help, because Ask, Bid and all these constants are not used anyway. Is this error appear every time the EA is trying to send a new trade?

I don't know about MA_Type error, at least when I try it it does not appear. MA_TEMA is a constant defined within the indicator, but use it's numeric representation instead. This is from the indicator:

/*
MODE_SMA       0     Simple moving average, 
MODE_EMA       1     Exponential moving average, 
MODE_SMMA      2     Smoothed moving average, 
MODE_LWMA      3     Linear weighted moving average.
MODE_DEMA      4     Double Exponential Moving Average. 
MODE_TEMA      5     Triple Exponential Moving Average.
MODE_T3MA      6     T3 Moving Average. 
MODE_JMA       7     Jurik Moving Average. 
MODE_HMA       8     Hull Moving Average. 
MODE_DECEMA    9     DECEMA Moving Average. 
MODE_SALT      10    SALT Indicator. 
*/

Not a bad idea

Това дето показва че е липсващ, на пръв поглед ми изглежда проблем с "&". Трябва да видя какво точно се случва с тоя символ, но ако се окажа тутка можеш да пробваш с име на файла без това "&"

How do you define Uptrend in this case - using MAs, candles, other indicators? For example, there is a block "Indicator rise" that detects if MA rises for X candles with Y pips.

No, new for me, I just found a post about this somewhere and I posted here just for information. What is interesting about Molanis is that one can download version 3.1, and I found a topic in their forum that mentions version 3.2... almost a year ago! Will this happen to fxDreema as well?