Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Prevent Parameters from showing in Indicator Call Parameters
Does anyone know of a way to hide "Parameter Box" options from showing in an indicators call parameters?
I am writing an indicator and want to prevent new parameters (2nd generation) and certain tuning parameters from being added to the CALL to that indicator in a strategy?
I have tried changing the GridCatagory, but that didn't seem to work.
[GridCategory("Parameters2")]
For some reason "int historySize" still shows in the parameters when I call this indicator from a strategy. I tried deleting the NT created functions at the end of the indictor to try and reset the compiler, but it just kept putting in back. The parameters still show in the Parameter Dialog box so that is still okay.
changing [Category("Parameters")] to [Category("Visual")] should do what you have in mind in case I understand you correctly. Although there are probably better solutions to the problem.
[Description("Bar History for comparison")]
[Category("Parameters")]
public int HistorySize
{
get { return historySize; }
set { historySize = Math.Max(1, value); }
}
For some reason "int historySize" still shows in the parameters when I call this indicator from a strategy. I tried deleting the NT created functions at the end of the indictor to try and reset the compiler, but it just kept putting in back. The parameters still show in the Parameter Dialog box so that is still okay.
Thanks
Maybe you need to select a different name then "Parameters".
Usually replacing "GridCategory" with "Category" works.
It seems like this works sometimes... It might be certain data types as my "STRING" that is in section "Version" I can turn on and off, but the bools and ints not so lucky....
Do you know if we can write our own class initializer so NT make the big one with the millions of command line options, but I hand write one with a few or no parameters?
It seems like this works sometimes... It might be certain data types as my "STRING" that is in section "Version" I can turn on and off, but the bools and ints not so lucky....
Do you know if we can write our own class initializer so NT make the big one with the millions of command line options, but I hand write one with a few or no parameters?
I have coded hundreds of indicators. All bools and ints labeled with "Category" will not show in the parameter list of an indicator. Where is the problem?
I have coded hundreds of indicators. All bools and ints labeled with "Category" will not show in the parameter list of an indicator. Where is the problem?
I am willing to bet it is more than hundreds of indicators you have coded. For some reason, most of the BOOLs and INTs still stay in the parameter list (a few dropped when I renamed all to Category). Do you know of one of your Indicators off hand I can play with to see if I can figure out why this is not reliable in my indicator?
I am willing to bet it is more than hundreds of indicators you have coded. For some reason, most of the BOOLs and INTs still stay in the parameter list (a few dropped when I renamed all to Category). Do you know of one of your Indicators off hand I can play with to see if I can figure out why this is not reliable in my indicator?
Sorry, on my side nothing stays in the parameter list. Please rename both "GridCategory" to "Category" and "Parameters" to something else. Could you attach an example that causes problems please?