Screen refreshing constantly

[aslane]

This is a strange one.

I installed Multicharts 6.0 beta to do some evaluations and it seems to be causing a strange interaction with Ninja Trader. When both programs are open, I see a huge CPU spike and screen flicker when the mouse is over an NT chart. When the mouse is moved over something else it goes away. The NT chart window does not need to be active (could be in background). It would seem that something is happening causing Ninja to want to constantly refresh the chart. The other apps and the windows desktop are also flickering/refreshing.

It has nothing to do with workspace/chart/indicator, as I have verified it happens with a new clean workspace with a single clean chart with no indicator. I am running B11 today, but it is also happening with 6.5.

Might be some strange windows thing (running XP with all fixes), but it seems Ninja is the catalyst, as it is only Ninja windows that cause the problem.

Update: it is only when mouse over the chart pane, not the title bar or toolbar.

[NinjaTrader_Dierk]

Unfortunately I would not know, since I don't know how MC would impact the .NET runtime or the windows OS (desktop flickering). The only advice I could provide at this time is running either NT or MC. Sorry for the inconvenience...

[aslane]

Here is another hint I figured out today. It only happens on a chart that has the cross hair enabled. When the normal pointer is enabled there is no flickering/refresh going on. So it must have something to do with your crosshair refresh algorithm. Even if the cursor is not moving, you continue to refresh the screen.

[NinjaTrader_Dierk]

>> Even if the cursor is not moving, you continue to refresh the screen
No we don't (provided there is no new data coming in).

[aslane]

Well, you are refreshing.

I did not mean to say that it is intentional. I suspect there is some event you are responding to that then causes another event causing a feedback loop somehow, and it is not just Ninja, but instead MC is a part of that loop along with Windows. While not the same, it is like the situation of not calling invalidate() in plot(). I am only trying to give you as much info as possible, so you can perhaps have an a-ha moment.

I understand that it may actually be .net or MC that is at fault, but you also have to understand that it may be Ninja, and not be so defensive when your users try to help you out.

In any case, it is not critical, as it can be worked around by turning off the cross hair.

[NinjaTrader_Dierk]

I tried to point out that this issue is beyond our control as our code would not refresh.