Posts made by isp00rt

Then you agree the Timer doesn't work? If modifying the timer period is not possible, what's the point of that tab?

That logic is not what I need. The variable is reinitialized before the timer is changed. That's the opposite I need. I want the variable to hold the new timer period before it is reinitialized, not the opposite.

Then why isn't it working in my project? I use that exact same block but the timer period is not modified?

I want to open trades at specific periods of time and I want to select those periods. I created this project to do it because this is theoretically the way to change the timer evet period:

https://fxdreema.com/shared/CRE95xYbe

However, it doesn't work. The event is executed at the value bu default no matter what. Can the admin fix it, please?

That I will do. Thank you for your help.

I already knew that solution, but it doens't work for me. I need to open trades at a very specific periods of time and conditioning that to the arrival of ticks is not an option.

I've been trying several configurations but to no avail. I guess it is a bug. Sadly, seeing the admin is simply disappeared from the forums, I don't see it will be fixed soon, if ever is.

Ok, I see what I really need is a way to insert a Cinstant in theProject Options' 'Timer period'. However, I cannot. Could someone please suggest any way to do it?

I know this is an old topic but it fits exactly what I'm looking for. I need to create a variable that is active for a specific amount of time in minutes. I will create a constant to select how many minutes.

I'm testing if I can do that by using 'on Timer' tab, but this is my first experience here and this is the only thread I found dealing with it. This is test project I created:

https://fxdreema.com/shared/CRE95xYbe

I want the variable to be modified exactly 2 minutes after it was last modified. According to the information window of the 'Change timer period' block, it modifies when this tab is activated. However, it still performs as per default every 60 seconds. For some reason I can't see now, the block is simply ignored. Any help?

Maybe I will try to open a ticket. Thanks for the advice miro.

I can finally confirm that if no indicators windows are present, the block works perfectly. There is no need to specify any width and height. The problem is when subwindows are included. It crashes it on MT5 no matter what. Could that be fixed, please?

I don't think he's looking for the logic behind the indicator but the solution for many mq5 indicators like this: one buffer --> two colour values. How can we "translate" that into fxDreema two buffers eligible on the 'Condition' operands?

I think I found a clue. Those 102 pixels are the height of the indicator's subwindow. No matter what dimensions I use (I tried those from miro), the problem is always the same. Now I will try not using any subwindow.

No, I don't have any other chart, app or file with that weird height. I will try miro's new settings.

I hate MT5 crap :(. It took 26 screenshots today. 23 like this:

And three like this:

This is simply ridiculous. Why two different formats from the SAME code doing the job?

One more question, please. Where are the pics supposed to be found?

Question 1. Considering that I want to take an image of every buy/sell trade I will have to connect it immediately after the buy/Sell block. Correct?

Question 2. I'm not a programmer. I'm not sure if any of the words included in your example are variables. Is there any? If so, which ones?

I used the exact same miro settings and this is what I got:

BTW, I forgot to tell that I'm trying this on MQL5. Am I missing something?

I used the same setting as per miro except that I didn't specify any Width and Height. They were both blank. I will try as per miro suggests.

Still waiting for some help.

Still here!