Information or an example?

[ETFVoyageur]

Here's one that seems like a bug to me. At the very least it is inconsistent with the way the charts handle it.

If I resize my columns, and then do an F5, NT changes my columns back to their default width. Please leave my column widths alone, just as the charts leave indicator panel heights alone when doing an F5.

One thing MA could do, though, would be to re-read ToString().

--EV

[NinjaTrader_Bertrand]

EV, I agree this seems inconsistent - I'll clarify those items with development.

Thanks,

[ETFVoyageur]

How do I set the text in the title bar of the Market Analyzer?

By default, all it says is "Market Analyzer". As discussed in previous postings, I need to have more than one Market Analyzer window. Since all MA windows have the same title, when they are iconized there is no way to look at the task bar and tell which is which.

--EV

[NinjaTrader_Bertrand]

EV, unfortunately you could not change the title - we'll add this request to your other suggestions.

Thanks

[ETFVoyageur]

Bertrand,

Here is one more request / suggestion -- I guess you need to add this to that document I emailed to you, too.

Please make the configuration dialog be non-modal.

Right now I have an indicator that is showing a very different value in Market Analyzer than on my chart.

I know that it is far more likely that it is my error than that there is an MA problem, so I am trying to find the error. One of the obvious basic things to want to do is to bring up both the MA configration dialog and the chart Indicators dialog so I can directly compare the configured values.

No can do -- both dialogs are modal .... Grrrr. Please fix this!

--EV

[ETFVoyageur]

Here's one I'll throw out while I try to track it down. Any ideas are welcome.

I have a custom trend indicator that is based on LinRegSLope(). As far as I can tell, the values I plot as an indicator for the chart are fine. For this exercise, it is enough to observe that they are positive for tickers that are sloping up, and negative for tickers that are sloping down.

Comparing the values for it on my chart with those reported when I use it as a Market Analyzer column provides quite the surprise.

• Tickers that are rising show the same value in both places (MA, chart indicator), so I would think that proves that I have Market Analyzer set up properly, and the indicator configured the same way in each place.

• However tickers that are falling show negative values as a chart indicator, and large positive values in MA.

Any idea as to why rising tickers would match in both places (as they should), but falling tickers would not match?

Bonus question: how can my indicator tell whether it is being displayed as a chart indicator vs being used to calculate the value for a Market Analyzer column? Making that separation would help debug this problem.

--EV

[ETFVoyageur]

Follow up on my bad values post -- problem has gone away, but even that is disturbing.

When I made my post, I had refreshed (F5) a couple of times, seen the values re-calculate, and gotten the same bogus values.

So, after my post, I put a Print() statement in the source and re-compiled. Now the problem went away -- Market Analyzer showed the correct values. So I took the Print() back out. Market Analyzer still shows the correct values.

That is disturbing -- I have done nothing to address whatever the problem was, yet it is now "fixed". I do not know about you, but that leaves me pretty worried.

--EV

[ETFVoyageur]

There is one minor Market Analyzer bug that I noticed while going through my "debugging".

Once the values got corrected, I had to be scrolled down for the remaining trials. I noticed that when I did an F5, my position in the list moved a few lines -- enough to put the line I was watching out of view.

I could understand jumping up to the first line (although I would strongly disagree -- that would be a bad idea). However, remaining scrolled down in the list, just jumping a few lines, seems to be an out-and-out bug.

--EV

[NinjaTrader_Bertrand]

EV, I gave it a try here but the lines remained static as I reload my NS studies - please try to take note what you may do different here should you see it next time.

The 'bogus' values issue: I'm glad you got it cleared that up - could it be due different instances of the indicator working for MA and Chart?

I've added your modal windows suggestion to our list of feedback.

[ETFVoyageur]

> I gave it a try here but the lines remained static as I reload my NS studies - please try to take note what you may do different here should you see it next time.

I'm not sure what an "NS Study" is, but my problem is completely reproducible for me. I have a Market Analyzer window with 400+ tickers. I scroll a ways down, and note the ticker at the bottom of the window. I do an F5. the window is shifted up the list by 10 lines. I tried it with 20 lines showing, and with 30 lines showing. In each case, the window was shifted up 10 lines.

> The 'bogus' values issue: I'm glad you got it cleared that up - could it be due different instances of the indicator working for MA and Chart?

I recompiled and reloaded each one, so no. Also, do not forget that even when I saw the problem most of the tickers were handled correctly in MA (all were on the chart). Just a few were not. I have no way to know whether it was coincidence or something real that all the bad ones I noticed were in downtrends. Also, don't forget that these tickers did not have that problem yesterday or the day before -- I would have noticed, believe me (the reported CAGRs went from a correct negative value to +28,000,000 when they were bad).

I do not believe it was a Market Analyzer bug, though -- instead I believe some sort of NT corruption, or possibly faulty caching of some sort. I tried to compile a different indicator (i.e. one not associated with MA). It complained that a property getter was trying to access its value without an object instance. After puzzling over that one, I replaced the Get() line with returning a constant. Compiled fine. Then I restored the original code. That compiled fine also. Note what is common about both cases -- something was clearly wrong, I made a minor change and re-compiled, and then changed back to the original code and re-compiled again. By then the problem had gone away.

I wish I could tell you more -- I am convinced that there was something wrong with NT, but I have no way to get into that state again, so I cannot tell you enough to help reproduce the problem or get it fixed.

I just exited and restarted NT. I hope that the problems are gone, but I'll never be able to prove that (you cannot prove the absence of something).

> I've added your modal windows suggestion to our list of feedback.

Thank you. I know that I previously suggested making the Indicators dialog non-modal. I am constantly reminded because I keep running into the problem. I do not know how anyone who is a developer could have made the configuration dialogs modal to begin with -- it is so frequently very frustrating.

-- EV

[NinjaTrader_Bertrand]

EV, with NS study I was referring to 'NinjaScript' studies / indicator which you reload via the F5 command. Just tried reproducing here with the SP500 list running on Kinetick live, but unfortunately I'm not able to - do you have the RowFilter and AutoSort for example enabled as this happens?

I've read your comments on the CAGR values issue, but would have unfortunately no explanation for now - please keep me updated if you see it reoccurring on your end so we can then look into further.

[ETFVoyageur]

> Just tried reproducing here with the SP500 list running on Kinetick live, but unfortunately I'm not able to - do you have the RowFilter and AutoSort for example enabled as this happens?

Bingo! That's the bug! I have row filter set. If I run off row filter, then I do not have the problem. The software is not properly allowing for row filtering.

> I've read your comments on the CAGR values issue, but would have unfortunately no explanation for now - please keep me updated if you see it reoccurring on your end so we can then look into further.

I agree that there is nothing for you to do at this point, other than be alert for any similar complaints from others. I'll let you know if I see it happening again. I wish I could be more helpful, but I have already told you all I know about it.

--EV

[ETFVoyageur]

Please add instrument manager to the list of dialogs that should be non-modal.

Basically, I am asking that no dialog be modal except for things like error dialogs that need to be addressed before proceeding. Making configuration or manager type dialogs modal is just frustrating when you are trying to find problems.

Right now, Instrument Manager is not showing all of the tickers in my Instrument List that should be there. I'm trying to find out why. Every time I go to look at something, I first have to take down Instrument Manger and the list I am trying to "debug"

Please, just make all dialogs non-modal unless there is a solid reason why one has to be modal (such as the error dialog example, mentioned above). Most of NT's dialogs being modal is a Royal Pain .....

--EV

[NinjaTrader_Bertrand]

EV, thanks again for the feedback, non modal dialogs are on our list already to be considered for the future.

I'll look into the unexpected outcome when the 'row filter' is set, thanks reporting back here.

[ETFVoyageur]

> non modal dialogs are on our list already to be considered for the future.

I did not want to keep beating on that one, but I did want to make sure that the list was about dialogs in general, not just the few I had specifically called out. Thanks for letting me knopw that the general issue is on the list -- I won't mention it again.

-- EV