Hi Carbonmimeti Any indicator called using the Fml() or FmlVar() functions in an exploration will only supply or recognize the "default" value from all Input() functions in the indicator. The user-set value or values only apply when the source indicator is plotted on a chart. For all other uses (such as an exploration or expert) only the default Input() value will be used. Input( "PROMPT TEXT", MINIMUM VALUE, MAXIMUM VALUE, DEFAULT VALUE); The Minimum and Maximum values allow flexibility for any indicator using this function, but the indicator can only deliver the DEFAULT VALUE to an exploration or expert. If you want the exploration to use a set value then the DEFAULT VALUE must be set accordingly before you run the exploration. If this doesn't help then please supply more details about the problem. Roy

Could 'GV' dll be able to solve the 'only default value' problem in explorations or at least to help somehow ? 

... I've been thinking so, yet have never done any try in this sense.

If an 'OPT' function existed, maybe it would do the trick... ?!?

Mark

 

 

 

Hi Mark Here’s an example of how you might go about modifying any custom indicator so that one or more user periods can be imported into an exploration as a constant value for any column formula. The indicator below is just a simple example. In reality you can create your own constant indicator to deliver any single constant, or up to 6 constants if needed, bearing in mind that only 6 Input() functions can be used in a MetaStock indicator. {New Indicator} {GV Set Periods} Constant:=Input("GV Set Periods", 2, 999, 10); Periods:=ExtFml("GV.SetVar","Periods",Constant); ExtFml("GV.GetVar","Periods"); Once the Global Variable has been created (by dropping the indicator onto any chart) that same variable can then be called by any other tool, including explorations, experts and system tests. {Your exploration} {ColA:} Periods:=Last Value(ExtFml("GV.GetVar","Periods")); Add your own code after the Periods parameter and do the same for any other columns if necessary. The reason for using LastValue() around the Global Variable GetVar function is to force the Periods parameter to be considered as a constant. If a “GV Set Periods” indicator is used then there’s no need to worry about a set sequence for getting the Periods parameter to a window or column of any tool. However, If a Global Variable is created in any tool other than the Indicator Builder the GV SetVar function must have a higher priority than subsequent windows or columns. That means that the GV SetVar function must create the GV in column A, and subsequent columns should use the GV GetVar function to access the constant. Hope this helps Roy

Hi Mark The CLEAR function deletes all data stored by the GV if memory serves me correctly. From what I recall the CLEAR has little if any value. I found it to be less than helpful and have avoided it for years. Here's some other facts that you might not know. It can store up to 100 variables. Multiple GV DLLs (different names such as GD, GL, GS etc.) can be used to increase the number of stored variables. Data from individual price bars can be accumulated across a portfolio. The down side of doing this is that ALL securities must have the same number of bars and generally identical dates and time stamps. Otherwise the data becomes corrupted and is entirely useless from that point on. Roy