Announcement
Collapse
No announcement yet.
Partner 728x90
Collapse
NinjaTrader
ClearOutputWindow with multiple output windows
Collapse
X
-
Originally posted by NinjaTrader_Matthew View PostThanks for your report. There is an issue where the method is defaulting to the Output tab 1. Beta 2 will include a fix where the ClearOutputWindow() method will clear the output tab that was previously set by PrintTo variable.
NTEIGHT-8254
Comment
-
Originally posted by koganam View PostMaybe better to provide an overload where we can specify the exact window to clear?MatthewNinjaTrader Product Management
Comment
-
Originally posted by NinjaTrader_Matthew View PostFor simplicity, ClearOutputWindow will work as stated, however if you'd like, you can always call NinjaTrader.Code.Output.Reset(PrintTo outputTab) (which will be available in the next beta build)
Code:protected void ClearOutputWindow(PrintTo outputTab) { NinjaTrader.Code.Output.Reset(outputTab); return; }
Comment
-
ClearOutputWindow with multiple output windows
Thanks, Matthew and particularly, thanks koganam!
Matthew, I would recommend that in this case "simplicity" needs to be superseded in favour of accuracy and extensibility. The potential is not insignificant for "confusing" situations where multiple strategies writing to both windows could cause "unexpected" clearing.
As koganam so eloquently suggests, the functionality really should be to allow the method to have an overload specifying the Output window to be cleared (by index or whatever is appropriate). Of course, two different signatures could be created to allow a convenient form of backwards compatibility -- one with no parameter, as currently, that would function as you indicate; the other with the Output window parameter.
In a separate thread (http://www.ninjatrader.com/support/f...ad.php?t=74170), I recommend extending the Output window functionality, and if this is implemented (please ), such an update to ClearOutputWindow would be essential.
Thanks.
Comment
-
We are in favor of simplicity. Providing an overload still does not prevent situations where another script clears the output window unexpectedly. I will not argue the system can't stand to be improved, but we're interested in seeing what sort of enhanced add-on output window or debugging tools the community can come up with. We'll definitely put your feedback down to be reviewed at the point our plate is cleared to revisit the output system.MatthewNinjaTrader Product Management
Comment
Latest Posts
Collapse
Topics | Statistics | Last Post | ||
---|---|---|---|---|
Started by cmtjoancolmenero, Today, 02:31 PM
|
2 responses
6 views
0 likes
|
Last Post Today, 02:49 PM | ||
Started by tradebot, Today, 01:25 PM
|
2 responses
8 views
0 likes
|
Last Post
by tradebot
Today, 02:36 PM
|
||
Started by merc410, Today, 03:41 AM
|
4 responses
27 views
0 likes
|
Last Post
by merc410
Today, 02:27 PM
|
||
Started by Graci117, Yesterday, 11:40 PM
|
2 responses
18 views
0 likes
|
Last Post
by Graci117
Today, 02:26 PM
|
||
Started by Taddypole, Today, 02:25 PM
|
0 responses
3 views
0 likes
|
Last Post
by Taddypole
Today, 02:25 PM
|
Comment