Problem:
Different strategies use different Max Risk settings (when you use it for position sizing). At the moment there's only one setting in Trading Preferences that you have to use with Building Blocks.
Possible solutions:
1) In C# you can overwrite it individually for each strategy. Would be nice to integrate that feature within the MetaStrategy overview.
2) Or some kind of Building Block that you can add to each strategy where you define your "Max Risk Indicator".
Either way, most importantly you should be able to set it for each strategy individually.
Different strategies use different Max Risk settings (when you use it for position sizing). At the moment there's only one setting in Trading Preferences that you have to use with Building Blocks.
Possible solutions:
1) In C# you can overwrite it individually for each strategy. Would be nice to integrate that feature within the MetaStrategy overview.
2) Or some kind of Building Block that you can add to each strategy where you define your "Max Risk Indicator".
Either way, most importantly you should be able to set it for each strategy individually.
Rename
Re: "Set "Max Risk" individually for each Strategy in MetaStrategy?"
That's too big of a [design] change. Cone's original suggestion was to request a quite reasonable expansion of the existing Max Risk preference to differentiate between long (e.g. using Low) and SHORT indicator (e.g. same indicator using High). Don't you already have complete control for doing what you request in C# code strategies?
Let me rename the topic accordingly.
That's too big of a [design] change. Cone's original suggestion was to request a quite reasonable expansion of the existing Max Risk preference to differentiate between long (e.g. using Low) and SHORT indicator (e.g. same indicator using High). Don't you already have complete control for doing what you request in C# code strategies?
Let me rename the topic accordingly.
Yes in C# sure. But I'm no coding expert and I guess many other people as well ;-)
And I thought when it's relatively easy manageable in C# with "override" that it should be also no big deal to give this possibility to the "Building Blocks Community" :-) But as I said before, no coding expert so my fault. :)
And I thought when it's relatively easy manageable in C# with "override" that it should be also no big deal to give this possibility to the "Building Blocks Community" :-) But as I said before, no coding expert so my fault. :)
Your Response
Post
Edit Post
Login is required