Problem with changing internal values ​​on blocks

[FED]

Hi everyone,
I noticed that if you don't change the internal values ​​of a block, such as time filters or conditions, after a while it won't allow you to do so anymore, and you're forced to delete the block and then insert a new one. Has anyone else noticed this problem?
Thanks in advance for anyone willing to respond.

[jstap]

I have never had this problem

[sktsec]

@FED
Don't think that is the case.

But the response time actually varies when you double click to open a block. The response might be so slow that you "felt" that was not working. The problem may be from your ISP / location. In my case, all my connection to fxdreema requiring VPN / Proxy connection. But it is good for other ISPs, so it seems not geo-location problem. Maybe some protocol blocked by my ISP, I really don't know the exact reason.

[l'andorrà]

@FED Never experienced something like that. I bet for sktsec explanation.

[FED]

I'm using an internet connection via a smartphone hotspot. However, it's strange since the new value inside the block changes, but when I backtest it, it remains with the old value.

[jstap]

That's not FX, that's what terminals do, just and check values have been changed

[FED]

I don't know what I could do.
In the meantime, I'll continue deleting old blocks and adding new ones every time I need to change the internal value.

[jstap]

try updating your internet browser, or use another

[FED]

I update the browser every week, I also tried using another browser but nothing, I can't solve the problem

[FED]

It seems like the block freezes after a certain number of days and even if you change the value (the new value is displayed) it remains with the old value

[jstap]

try saving and reading as a terminal (global) variable.

[FED]

I've already done this with variable or constant settings, if you don't change them frequently I have to redo those too

[jstap]

global variables are stored in a folder separate to where your local variables are, so they will not change until you change them, so if a block is reading them to use, it will be the same untill you change.

[FED]

Yes, I tried changing it from there too. Are you referring to the left column under the project name? Changing that also changes the value visually but not actually because it remains the old one.

[jstap]

This is an example on how to use global variables, press f3 and you will see all on your platform, when you change the input the comment will update and the saved global variable: https://fxdreema.com/shared/MCg4nvb2d

[FED]

Yes, I understand.
It doesn't let me change the values ​​after a few days, either, so I have to delete the variable and constant and then create a new one. The problem remains the same as when changing the values ​​in the normal block.

[FED]

If you try to change the value 100 of the variable you set after a few days with another value it displays the new value but if you test it in backtest the old value 100 remains

[jstap]

It won't on backtest test on a live chart, what ever is set shouldn't change unless you change, use global regularly and the never change by them selves. if you change before starting backtest it will show that number

[FED]

I think blocks freeze when using the Normalize Block IDs feature.

[jstap]

Maybe, set it and keeo updated, unless the ordre blocks run then this doesn't matter that much, just stop crazy numbers.