|
PureBytes Links
Trading Reference Links
|
Like the Explorer(MSKv70-Man. p.368) you are able to, however always "default"-ing
back to the last value in the to-be-assigned variable, eg the "5" in your example
(MSKv70-Man. p.354).
Functions are by programmers written Tools, used in programs.
Functions can therefore be used in scripts.
Scripts can be run in and by programs to execute certain actions.
- Input() is a Function.
- Variable is a Function, of and in a script (MSK formula language is scripting).
Input() for Function used in a script's to-be-assigned variable is that Function's formula
stored in that variable (for outcome it is also a variable held in that formula).
An assigned variable is a temporarily <and for that script only> in MEM stored formula
string of that variable.
Once assigned=always assigned (for use in that script).
The moment you fire up that formula(eh SysTest), you are assigning a variable for definite.
Thus at that time it cannot also ask you, the user, to again change that value.
You can do so, but this should then be done prior to the fire-ing-up of the then-for-definite
assignment.
By MetaStock design, the Sytem-Tester and the Explorer are 2 of MSK's sub-programs,
that are programmaticily not designed to "live" inter-act with the user, eg and therefore
give user the chance to in a later stage alter or change the custom script's values.
This can be solved when Equis changes and re-designs these 2 programs to now also
contain and hold the capability for user to "live inter-act" in and with program's
SysTest/Exploration sub-programs.
A workaround for the moment would be to make a change upfront to the to-be-assigned
variable's default value in the SysTest's script, or use multiple -different-time-periods-
versions of your original SysTest.
Design levels:
"Inter-act-ing" is known as being user-definable/communication and as is the base
of all Windows compatible program's : also known as being user-friendly !!!!!!!!
Of late, PD Manager & Equis were looking for good improvement suggestions for both
of these sub-programs, eh at least for the System Tester. Since that it is of value and that it
has no use endlessly debating this program's "short-coming", have cc-ed mail to
suggestions@xxxxxxxxx
Regards,
Ton Maas
ms-irb@xxxxxxxxxxxxxxxx
Dismiss the ".nospam" bit (including the dot) when replying.
Homepage http://home.planet.nl/~anthmaas
----- Original Message -----
From: "Owen Davies" <owen@xxxxxxxxxxxxx>
To: <metastock@xxxxxxxxxxxxx>
Sent: zaterdag 12 augustus 2000 1:43
Subject: Re: Psychological Index
> I hate to ask something that's a stupid question, even for me, but:
>
> Am I missing something, or can we really not use an Input statement
> in a system test? As in:
>
> Len:=Input("Period of Short Moving Average",1,100,5);
>
> If so, this jumps to the top of my list of silly omissions that
> MUST BE CORRECTED in the next revision.
>
> Owen Davies
>
>
|