This request might be one of those bottom-of-barrel priorities. But, for those of us that use external C# editors, it sure would be nice for workflow if when you press the Compile button, then WL8 remains where you're at (chart, etc.). This of course would be a Preferences setting.
Sometimes you're making a few tweaks in your code and analyzing the results, say in the backtest results or on a chart. If you press Compile, then you have to jump back to where you were at (backtest results, chart, etc.)
Sometimes you're making a few tweaks in your code and analyzing the results, say in the backtest results or on a chart. If you press Compile, then you have to jump back to where you were at (backtest results, chart, etc.)
Rename
I see such option as highly counterintuitive. When you click Compile you naturally expect the code to be compiled and see the result of it e.g. "Compiled OK". And what if compiler throws an error? You would discard it because to glance at a chart or review visualizers is more important? That's plain alogical.
Not to mention that introduction of single-user options would overload the GUI (even the Preferences dialog) and might detract prospective customers from using the crowded, complex platform.
Not to mention that introduction of single-user options would overload the GUI (even the Preferences dialog) and might detract prospective customers from using the crowded, complex platform.
The feature I requested would be configurable in the preferences.
Here is the scenario: If I'm working in an external editor, say Visual Studio or JetBrains Rider, and my code compiles ok there, then in WL8 it is likely to compile successfully, too. With the feature I mentioned, I simply remain where I'm at in WL8. That way, WL8 does not take me to over to the C# Code Editor tab. If there is a compilation error in WL8 then WL8 would show the C# Code Editor tab. In any case, WL8 can show the status of the latest compilation in the status line.
The way it is now, when I press compile, WL8 jumps to the C# Code Editor tab. Then I have to go back to where I was at (chart, whatever). If using an external editor, I have no real use to jump to the C# Code Editor tab on a successful compilation.
I hope I'm explaining this well.
Here is the scenario: If I'm working in an external editor, say Visual Studio or JetBrains Rider, and my code compiles ok there, then in WL8 it is likely to compile successfully, too. With the feature I mentioned, I simply remain where I'm at in WL8. That way, WL8 does not take me to over to the C# Code Editor tab. If there is a compilation error in WL8 then WL8 would show the C# Code Editor tab. In any case, WL8 can show the status of the latest compilation in the status line.
The way it is now, when I press compile, WL8 jumps to the C# Code Editor tab. Then I have to go back to where I was at (chart, whatever). If using an external editor, I have no real use to jump to the C# Code Editor tab on a successful compilation.
I hope I'm explaining this well.
Of course I understand that scenario.
But compilation in an external IDE does not guarantee successful compilation in WL8 - for example, if a dependency hasn't been referenced in the Assembly References dialog yet.
Even better, we should gray out the Compile button if the C# Editor is not in focus. This would discourage the user from pressing it while his or her intention is something completely different. Elegant and no new confusing options.
By the way, "Run Backtest" itself does the compilation and remains always accessible in Backtest Results and Chart views.
But compilation in an external IDE does not guarantee successful compilation in WL8 - for example, if a dependency hasn't been referenced in the Assembly References dialog yet.
Even better, we should gray out the Compile button if the C# Editor is not in focus. This would discourage the user from pressing it while his or her intention is something completely different. Elegant and no new confusing options.
By the way, "Run Backtest" itself does the compilation and remains always accessible in Backtest Results and Chart views.
Like Eugene said, I think the simplest solution is to just not press the Compile button. Pressing Run Backtest also does a compile if needed (if there were any changes) without moving the view to the Editor.
Thanks, Eugene. I was not aware a compilation takes place upon running a backtest. Hence, I now believe that my request is moot. Thanks, again.
Glad to have helped you, Paul!
Your Response
Post
Edit Post
Login is required