Please add a call like
that can be called in BacktestComplete().
Useful for strategies that don't produce trades (so Backtest Results are boring) but some graphics in the Chart.
CODE:
ShowChart()
that can be called in BacktestComplete().
Useful for strategies that don't produce trades (so Backtest Results are boring) but some graphics in the Chart.
Rename
IMHO, this would be so overly catered to 0.01% of strategies to just consume development resources and bloat the code base. Why would a strategy not produce trades in a backtesting/trading application?
Wouldn't it be simpler to simply show the Chart after a single-symbol run like WL7 use to do? I certainly miss that feature.
If we did that, other people would complain about that change. We can't make everyone 100% happy.
In a single symbol backtest, you just need to click the chart tab one time.
Afterward, you can click symbols in the DS tree to re-run the backtest to your heart's content and the chart tab will remain selected.
In a single symbol backtest, you just need to click the chart tab one time.
Afterward, you can click symbols in the DS tree to re-run the backtest to your heart's content and the chart tab will remain selected.
I'd expect this goes to the Wish List and either dies a silent death (like suggested by Eugene's 0.01% argument) or sparks some interest in the community.
What I know:
I have a strategy (and plans to produce more) which generate interesting graphics.
People will get a "run this strategy" advice and:
...sit and watch and wonder why they don't see nothin....
Especially Building Block users are not accustomed to open the Chart.
Of course, for a power user there is no point to even think about...
.... but there exist users that are not exactly "power users"
So this is more about #usability #user-friendlyness #not-important-but-nice
What I know:
I have a strategy (and plans to produce more) which generate interesting graphics.
People will get a "run this strategy" advice and:
...sit and watch and wonder why they don't see nothin....
Especially Building Block users are not accustomed to open the Chart.
Of course, for a power user there is no point to even think about...
.... but there exist users that are not exactly "power users"
So this is more about #usability #user-friendlyness #not-important-but-nice
QUOTE:
just consume development resources
I'd guess it takes Dion longer to read through this discussion and think about its usefulness than it'll take him to implement
CODE:
ShowChart()
QUOTE:
If we did that, other people would complain about that change. We can't make everyone 100% happy.
QUOTE:
... Building Block users are not accustomed to open the Chart.
So the point both of you are making is that opening the Chart after a run by default should be controlled by a check box in Preferences.
Why don't you just come out and say that?
I'm not saying that at all. I said we can't make everyone 100% happy.
Adding a checkbox preference for every piece of minutiae isn't a solid approach.
Adding a checkbox preference for every piece of minutiae isn't a solid approach.
All I asked for is a tiny additional member function of class UserStrategyBase.
Dr Koch said, "All I asked for is a tiny ..."
ROFL!
ROFL!
Meanwhile I found a much better solution for this problem:
The new finantic.InteractiveGraphics extension.
If a strategy uses the ScottPlot library (along with this extension) it will open the graphics at the end of backtest.
So my dream came true! :)
I think I am ok if you put this #FeatureRequest in the "Declined" drawer.
-or- even better:
Solved, implemented by the finantic.InteractiveGraphics extension.
The new finantic.InteractiveGraphics extension.
If a strategy uses the ScottPlot library (along with this extension) it will open the graphics at the end of backtest.
So my dream came true! :)
I think I am ok if you put this #FeatureRequest in the "Declined" drawer.
-or- even better:
Solved, implemented by the finantic.InteractiveGraphics extension.
Your Response
Post
Edit Post
Login is required