Errors, bugs, questions - page 1251

New comment
 
Tapochun:
We draw several trend lines. Get their price coordinates at the current time (using a script). Shift the scale. Re-derive the values of the trend lines at the current candle. Here is the result.

Let us use more constant time instead of TimeCurrent(). For example Time[0] - within the current bar this time does not change
 
stringo:
Let's use a more constant time rather than TimeCurrent(). For example Time[0] - this time does not change within the current bar
In the screenshot, you can see that measurements were made within one minute, I did not move the lines manually. I only moved the vertical scale. Yes, and if you suggest using a constant time, it turns out that the line can "jump" within one minute?
 
Tapochun:
You can see in the screenshot that the measurements were taken within one minute, I did not move the lines manually. I only moved the vertical scale. Yes, and if you suggest to use constant time, it turns out that the line can "jump" within one minute?
There is some distance between bars too. TimeCurrent in most cases will give time farther and farther away from the start of a bar. The farther the time, the higher the price, if the trend line is ascending
 
Tapochun:
We draw several trend lines. Get their price coordinates at the current time (using the script). Shift the scale. Re-derive the values of the trend lines at the current candle. Here is the result.

Has anyone already mentioned that it is better to use bar open time instead of TimeCurrent?
 

When moving triangle, ellipse, rectangle objects, the anchor points "float" disproportionately.

It does not depend on these settings


I create


drag and drop


The second anchor point of a rectangle is "drifting". The third anchor point of triangle and ellipse are "drifting".

Is it possible to fix it? I need exact "measurements".

 
stringo, more details here.
 

mt4 751 build again caching past values.

1. indicator.
2. Global variable depends on extern variable
3. Attach indicator to chart (we can do it in debug mode - it's easier)
5. Set a breakpoint on the global variable, depending on the extern variable
6. Go into the indicator settings, change the values of the extern variable.
7. But the global variable does not change its value - the old value remains
8. Open properties of the indicator again and simply press ok.
9. All is normal now.

 

The global initialisation function is called before applying changes to extern variables.

 
ALXIMIKS:

The global initialisation function is called before applying changes to extern variables.

Show an example of your code to illustrate the problem
 


Is it a bug?

1...124412451246124712481249125012511252125312541255125612571258...3190
New comment