Faulty global cross hair in 6.5.1000.6

[astrolobe]

In version 6.5.1000.6, the global cross hairs only move in sync if both charts have the pointer set to Global Cross Hair.
In the previous version you could set just the chart you wanted to move in sync, by setting its pointer to Global Cross Hair, and leaving the other chart to only Cross Hair.

[NinjaTrader_Dierk]

>> In version 6.5.1000.6, the global cross hairs only move in sync if both charts have the pointer set to Global Cross Hair.
Correct, this is expected behavior. Prior behavior was incorrect.

[astrolobe]

I preferred the old behavior.
If you have two charts that are different timeframes, then when you are over the larger timeframe chart, the smaller timeframe chart is jumping around all over the place.

[NinjaTrader_Dierk]

>> If you have two charts that are different timeframes, then when you are over the larger timeframe chart, the smaller timeframe chart is jumping around all over the place.
Not sure I follow. This works as before.

[bigriver]

I agree with astrolobe...the behavior of the new global cursor is different and fairly unworkable. I definitely prefer the old behavior.

Say I move my cursor to a higher timeframe chart...my lower timeframe chart then jumps to wherever my higher timeframe chart cursor is. I've lost my place on the lower timeframe chart and when I go back to my lower timeframe chart, I have to find where I was. Not to mention that the lower timeframe chart data is jerking all over the place, not pleasant visually.

[NinjaTrader_Ray]

Say I move my cursor to a higher timeframe chart...my lower timeframe chart then jumps to wherever my higher timeframe chart cursor is. I've lost my place on the lower timeframe chart and when I go back to my lower timeframe chart, I have to find where I was. Not to mention that the lower timeframe chart data is jerking all over the place, not pleasant visually.

This is expected behaviour since both cross hairs are in sync along the x and y axis of both charts. What you experience before was actual a result of a bug. I can see the value of having the lower time frame drive synchronization on the higher time frame but not be on the receiving end. This behaviour is on our NT7 list where you would be able to have a chart either receive only, send only or both.

[bigriver]

In the meantime, any way I could get that "bug" back?

[NinjaTrader_Ray]

Prior NT version, available on our website.

[gdargento]

Agree w/astrolobe. Made sense in previous version w/lower timeframe chart driving the higher.