Chart won't compress bar spacing sometimes

[adamus]

Yes it is Brett

[NinjaTrader_Brett]

Great.

Can you please send me that workspace to support at ninjatrader dot com ATTN: Brett.

My Documents->NinjaTrader 7->workspaces->Name of Bad workspace.XML

Thanks.

[adamus]

Sorry Brett, had another issue and ended up saving my workspace again before I read your message.

I guess it can wait till it recurs.

[adamus]

I've got this one again. In fact I have had it repeatedly every week or fortnight since posting over a year ago. I figured since you are bringing out NT8, it would be good to get the issued logged at your end.

I've been using one of the work-around to bring it back to normal, like today.

What do you want me to do? You still want a copy of my workspace or has someone else already logged the issue?

[NinjaTrader_Brett]

Hello,

I do have one reproducible scenario with this, has to do with taking the actual window size and shrinking it, then adjusting bar spacing and when you make the chart large again you can only get the spacing so small.

If this sounds like what might be happening to you then we have it if not then we would want to work with you to get a reproducible scenario.

Thanks.

[adamus]

Brett,
that's not it. I think this issue has more to do with the data that's loaded compared to the session settings or similar, as opposed to anything to do with the window size - that seems to be no issue here.

[NinjaTrader_Bertrand]

adamus, would be then great if you could contact us via Help >> Mail to Support with the issue workspace included. Please also add details / settings you routinely use in your setup that would potentially help us reproduce in house and therefore be able to address going forward.

Thanks much for your support on this matter.

[Alfred]

2 cents...

Fairly often, usually on a small size 2 data series tick chart, for some reason it may become so that one cannot compress as much as desired...then will scroll the chart back into a thin area of overnight data and then reset the chart by typing in the period value...then most times you will see a much more compressed chart (sometimes if this does not appear to work on the first attempt...for some reason it helps to then go full screen after you get back to a thin area, then reset the data period)....then scroll back (or hit End) to return to the latest and it will then be compressed too much usually and then you can expand to the level of compression desired...and then fuss around a bit as desired...have also found that HiLo charts work better and display better (especially in a fast market area) re compression etc than OHLC charts...you do not seem to have to fuss with compression rates as much throughout the day on HiLo charts vs OHLC charts...use Hilo almost exclusively now....

Probably do this scroll back & reset about one or 2 times a day on 1 or 2 active charts...

.......

[adamus]

Workspace sent.

[adamus]

It's behaving itself OK today. I'll post when it goes up the creek again.

[adamus]

I'm seeing it right now. I've just powered up NT7 and I can't get more than 4 mins onto my chart - same story as every time.

None of the work-arounds are working either today

Probably here Alfred it's a specially difficult case because I've got bid and ask plotted on the chart.

[NinjaTrader_Bertrand]

Thanks adamus, on which workspace / instrument would you see this today so I could check against the ones you sent kindly in? Do you notice any errors in your logs this morning around the restore time when I occurred?

[Alfred]

another idea...??

adamus....here is something I do to keep things working well...after shut down go to NT7>db> and there delete all sub folders in cache, minute and tick....then when you start up you will have clean data and generally things work better perhaps...something to try maybe...

.......

[adamus]

I didn't realise I sent you more than one workspace. The one called Euro PAT is the one I used all the time and the one I mean now.

The instrument is $EURUSD from IB.

This is the only error in there which I don't recognise:

2013-05-01 11:05:22 Default Error validating request:-'wc' : cause - The symbol or the local-symbol or the security id must be entered ServerValidateError

This error also occured after I restarted at 12:24 and in the IB log there were simultaneous errors like this:

^M
HD 12:32:00:627 JTS-EServerSocket-498: SECDEF  Sending  reqId=FixSecDefReqBySymbol459  symbol=EUR 0 IDEALPRO CASH^M
HD 12:32:00:876 JTS-EServerSocket-498: [0:20:65:1:0:0:0:ERR] -'wc' : cause - The symbol or the local-symbol or the security id must be entered^M
HD 12:32:00:876 JTS-EServerSocket-498: Anticipated error^M
HD jextend.d: The symbol or the local-symbol or the security id must be entered^M
        at jextend.oc.p(oc.java:171)^M
        at jextend.wc.e(wc.java:316)^M
        at jextend.tb.i(tb.java:302)^M
        at jextend.af.db(af.java:1334)^M
        at jextend.af.run(af.java:1183)^M
        at java.lang.Thread.run(Unknown Source)^M

[adamus]

adamus....here is something I do to keep things working well...after shut down go to NT7>db> and there delete all sub folders in cache, minute and tick....then when you start up you will have clean data and generally things work better perhaps...something to try maybe...

.......

OK I'll try it tonight. I hate the data management with NT7. Today the thing overwrote a load of old data, pulling down a bad tick again from IB for the 50th time which I'll have to correct. That bad data in the Historical Data Manager is burnt into my screen.