QUOTE:So when my compiled assembly name is Superticker.Indicators, why does it come out as "Indicators" in WL7?
By default, WL7 assigns a LibraryName for your Indicators based on the assembly name of your library. It uses the LibraryName as the header text in the Indicator tree node that contains your Indicators.
Now I have two "Indicators" libraries listed. One for WealthLab.Indicators and another for Superticker.Indicators. The library name should be the full assembly name.
QUOTE:
If you want to use a different name, assign a value to this property in your Indicator constructor.
CODE:Does in matter which indicator (I have several in Superticker.Indicators) I place this property value in?
public string LibraryName
Rename
It works this way to reduce the size of the labels in the tree. So it's working as designed. To create a custom name assign it in each indicator constructor. You can even have different indicators from the same assembly appear in different folders using this property.
QUOTE:Okay, I changed the assembly name to Superticker.SuperIndicators and that does change the library tree heading to SuperIndicators (without changing the Visual Studio project name). Interesting.
It works this way to reduce the size of the labels in the tree.
QUOTE:I'm assuming only the "dummy" constructor, which WL7 calls at startup, needs to make this property assignment since it builds the directory tree. The primary constructor doesn't need to make this assignment.
To create a custom name assign it in each indicator constructor.
QUOTE:Hmm. I'm trying to decide if that's an advantage or a disadvantage? I guess that depends on how you use it.
You can even have different indicators from the same assembly appear in different folders using this property.
Thanks for all the clarifications.
Can you add the LibraryName property to StrategyBase for compiled strategies as well?
Let's open a new Feature Request for this so we can properly track the request.
Your Response
Post
Edit Post
Login is required