Errors, bugs, questions - page 1107

[Renat Fatkhullin]

Silent:

I'm talking about "graph-walking" objects, when you change the scale of the price, the objects move around the graph in a very large range, #766333 from 2013.06.06.14:16

Just updated the ticket. Wait for a reply in it, please.

[Andrew Petras]

Renat:
Up with the ticket. Wait for an answer in it, please.

Okay, thank you.

[A100]

Compilation error

ENUM_DAY_OF_WEEK f()
{
        return ( ENUM_DAY_OF_WEEK( 1 ) ); // ошибка компиляции
}

but otherwise

        return   ENUM_DAY_OF_WEEK( 1 ); // нормально
        return                      1;   // нормально
   

OK

[Vladimir Karputov]

On the new 900 build, these errors appear when switching timeframes:

Tried it on a clean chart without indicators, EAs, scripts etc. What is this error?

P.S. So far I have noticed it only on one instrument "UX-3.14".

[A100]

Compilation error

class A {
public:
        void f() {}
};

void OnStart()
{
               A * const z = new A;
// не путать с
//       const A *       a = new A; // и с
//       const A * const a = new A;
        z = new A; //     ошибка компиляции   обоснована, поскольку ранее объявлено const z
        z.f();     // (!) ошибка компиляции необоснована, поскольку z не const A* 
}

In this case const is a pointer but not the object itself (i.e. z is not const A*), hence f() does not have to be const

Those who doubt can check a similar C++ compiler operation

[A100]

Superfluous warnings, why?

int f( int x )
{
        return ( x == 2 ? 0 :  1 <<  x - 1  );   //           предупреждение
        return ( x == 2 ? 0 : (1 <<  x - 1) );   //все равно предупреждение
        return ( x == 2 ? 0 :  1 << (x - 1) );   //уточнил
}

        int y = 2;
        int x = 1 <<  5 - y;  //предупреждение
        int x = 1 << (5 - y); //уточнил

Priority operations areprioritised, unnecessary warnings make it difficult to identify the really important ambiguities

[x572intraday]

On timeframe <= M5 levels of TA-tool Daily Fibo Channel disappear. That is, when the chart is vertically compressed (in hope to see at least so) and scrolled back, at some moment the lines appear and it is even possible to trace the moment of their visibility transition to invisibility.

The template is in the archive.

[Vladimir Karputov]

x100intraday:

On timeframe <= M5 levels of TA-tool Daily Fibo Channel disappear. That is, when the chart is vertically compressed (hoping to see at least so) and scrolled back, at some point the lines appear and you can even trace the moment of their transition from visibility to invisibility.

The template is in the archive.

Read the "Finobacci Channel" terminal help.

When you set the channel, you are bound to prices and timeframe. When you reduce the timeframe, of course, the levels simply disappear from view. But the channel itself remains on the chart. To check this, right-click and select"List of Objects".

[x572intraday]

barabashkakvn:

Read the Help for the Finobacci Channel terminal.

When you set the channel, you make a reference to prices and times. When you reduce the timeframe, of course, the levels simply disappear from view. But the channel itself remains on the chart. To check this, right-click and select"List of Objects".

First, it is not the Finobacci Channel but the Fibonacci Channel.

Secondly, I suspect that you didn't sketch the pattern I attached before you rushed to comment on the problem (unlikely, but that may be due to different hardware, such as monitor or video card).

Thirdly, have now double-checked and verified that the lines are disappearing as early as M6.

Fourth, please trace the change of the line presence when diminishing step by step the timeframe and draw an obvious conclusion that the line cannot abruptly "run away" behind the screen when smoothly going to a lower (i.e. neighboring) timeframe. I have not suddenly gone from H4 to M5 and wondered: where is my line? Its withdrawal should be gradual, but it just disappears.

When I go from M10 to M6, the line cannot suddenly disappear beyond the boundaries of the monitor. That is, it obviously loses its display on the chart - the visualization proper, but it does not go beyond the boundaries of the visible area of the chart. It is impossible to find the line even with a very strong vertical compression of the chart and even a very significant rewind of the chart. And in the Object List, of course, the tool continues to be present, no one argues.

[Andrew Petras]

x100intraday:

Servicedesk.

Saw such a glitch when checking objects for correct display, exactly when scaling the price scale. Apparently, it stayed that way.