Posts made by fxDreema

I don't even know what is that error Where do you see that error?

Parabolic.mq4 - what is this, indicator from internet or EA made with fxDreema?

Ok, I guess it is some EA. Then at least tell me which of your projects we are talking about. Just like that I can't even recognize this as an EA, how can I say what is located at row 156 position 43

You are talking for the "Adjust" field? +100 is ok when we are talking about money. But if you decided to work with the account equity or balance, then you can also try that Profit (Equity-Balance) option

But it moved eventually? You can try that Reference price setting. I added it because of people who work with small stops.

Remove #property strict if exists. If it doesn't exist or it still gives that error, then the code must be fixed

Never

What problems do you have now?

I have no idea what this is. And by the way I have no idea what futures are I know it's stupid, but I'm not a serious trader and when I trade, I do it on currencies. So I don't know why these futures need such expiration time and what is this time anyway

You said smaller. And to fix this problem easily I did something in the past - blocks can be made to look smaller. Right click and look at the Resize option It's not the best option, but it's something.

Oh no! Completely my fault. I was convinced that I did everything right, but I used the wrong MQL function for this. Indtead of toDigits() I was using toPips()... probably because it sound more like pips. Anyway, it should work now, at least I hope.

This problem comes from some indicator I guess. Last month I was working on a MQL4 to MQL5 converter so I now understand indicators a liiiitle bit better. Not very much better So while I was testing different indicators I noticed something. That error "array out of range" would appear in MQL5 indicator if anything is wrong with the buffers inside OnCalculate(). But the same indicator could work in MQL4 without problems when there is no #property strict. It seems that in MQL4 you have the option to set the code as strict mode or not, while in MQL5 you don't have this option - it's always strict.

So, if your indicator has #property strict you can try how it will work without it. Otherwise you must fix the problem in the code.

I have some feeling that you want to have moving pending order, something like trailing pending order. And there is a block for this - https://fxdreema.com/demo/mt4-trailing-pending-orders

Let's say that I don't understand your english. And my native language is not english by the way

Well, this is better https://www.mql5.com/en/docs/convert/timetostring
I guess there is no proper way in fxDreema to output time variable, I wonder what can I do about this. But this works: http://prntscr.com/dwzl2t

https://fxdreema.com/forum/topic/4329/illegal-operation-use

But how many topic about this... Ok, for some reason this problem was in the code for 1 year and more, but the compiler didn't care. Now I don't know exactly why this problem started to appear, but I repacked build 100: https://fxdreema.com/desktop Different file, the same version... I like it at 100

Where... In most blocks that work with time, for example "Time filter" there is an option to choose between different ways to input data. But if you need a function to convert string to datetime, then you can try StringToTime() https://www.mql5.com/en/docs/convert/stringtotime

But I don't recommend using any custom function that I have created. toDigits() is just one of them and I can change it in future without asking anyone.

ConstantName pips should work, this is the official way. If it doesn't work, then I need to know why. But in my little test that I did now it works...

I don't understand the idea here

I was also thinking about this for long time. There is a problem that some people tend to copy-paste groups of blocks and the result is projects that contain thousands of block. This is not very pretty. But even if I do what you want, then what will happen... people will make huge projects that only look small. I don't necessarily like this idea. I prefer people to make projects with less blocks, not more. I mean, I don't like the idea of fixing some problem only visually.