|
PureBytes Links
Trading Reference Links
|
I believe that the MSX examples were published in that format because only
the MSX API could perform the desired calculations for those specific
indicators.
I would expect that when indicators can be calculated in the standard
MetaStock formula language, they will be published in that format.
Ken Hunt
Programming Manager
Equis International
-----Original Message-----
From: T.E.M. Lockefeer [mailto:sky40912@xxxxxxxxx]
Sent: Wednesday, July 19, 2000 10:19 AM
To: metastock@xxxxxxxxxxxxx
Subject: Re: Question on calculation
Kent :
Improvements are of course always welcome but for a MS 6.52 user
it looks like being old fasioned not to upgrade : suddenly the formulas
with the
articles in Stocks and Commodities asume that every MS 6.52 user
automatically
upgraded to newer versions of MS with MSX capability :
i donot think that is the case : are we (MS 6.52 users) now something
Equis never
more thinks again ? . Will we ever see again those copy and paste
formula's ?
Thanks for your reply and for your collegues of support@xxxxxxxxxxxxxxxxxxx
Will i ever get a reply on my email from weeks ago ??
Thanks.
Theo Lockefeer
----- Original Message -----
From: "PD Manager" <pdmanager@xxxxxxxxxxxxxxxxx>
To: <metastock@xxxxxxxxxxxxx>
Sent: Wednesday, July 19, 2000 4:47 PM
Subject: RE: Question on calculation
> The MSX capability was added to the MetaStock formula language for just
such
> a purpose. The built-in formula language in MetaStock was designed to
make
> it easy for simple calculations to be quickly and easily coded. Because
of
> this, many complex calculations are extremely difficult or absolutely
> impossible to code in the formula language.
>
> Without the addition of MSX, it was virtually impossible for us to add the
> capabilities to the formula language that were demanded by our power
users,
> while preserving the simplicity and ease of use for our less experienced
> users. While some of our users have been asking for traditional
programming
> structures to be added to our formula language (loops, array indexing,
etc)
> most of our users have no concept of these programming techniques.
>
> MSX adds the ability for users, who may have a programming background, to
> write virtually any complex indicator calculation. When a user creates an
> MSX DLL, it actually allows them to add new functions to the MetaStock
> formula language itself. This means that once written, an MSX function
can
> be used in a custom indicator, system test, exploration or expert. These
> new functions can also be easily shared with other users by simple
transfer
> of the MSX DLL. Once the DLL appears on the other users machine, the new
> functions are automatically added to the formula language for that
machine.
>
> MSX indicators are also extremely fast to calculate.
>
> Ken Hunt
> Programming Manager
> Equis International
>
>
>
> -----Original Message-----
> From: Michel Amelinckx [mailto:Michel.Amelinckx@xxxxxxxxxx]
> Sent: Wednesday, July 19, 2000 5:11 AM
> To: metastock@xxxxxxxxxxxxx
> Subject: RE: Question on calculation
>
>
> Guy,
> Why don't you get MSX, then you can make the add on your self.
> I don't think it is too complicated if you know C or C++ Pascal , Power
> Basic.
>
>
>
> > -----Original Message-----
> > From: owner-metastock@xxxxxxxxxxxxx
> > [mailto:owner-metastock@xxxxxxxxxxxxx]On Behalf Of Guy Tann
> > Sent: woensdag 19 juli 2000 1:19
> > To: Metastock User Group
> > Subject: Question on calculation
> >
> >
> > List,
> >
> > Well I'm in the process of trying to move our Intermediate
> > Term Signals into
> > MetaStock and need a little help.
> >
> > First, here are a few of my assumptions I made after
> > reviewing the latest
> > manual (v7.01).
> >
> > 1. Variables go away after each day (we're EOD traders, so
> > daily is our time
> > frame).
> > 2. The only way you can reference a prior day's value is by
> > using PREV or by
> > plotting the indicator and using the "P" Data Array Identifier.
> > 3. The only way to reference the previous 20 values of an
> > indicator is by
> > using the "P" Data Array Identifier.
> > 4. Plotting of indicators is irrelevant for our system, so I'm only
> > interested in a programming solution.
> >
> > Questions:
> >
> > 1. Is there any way to build an array or list of variables
> > that you can
> > programmatically control? For instance, I want to maintain
> > the last 20
> > values of a specific indicator and keep them for use on the
> > next day. At
> > then end of each days processing, I would move X17 to X18,
> > thereby dropping
> > the previous X18. X16 to X17, etc., thereby getting ready
> > for the next days
> > result, which I would store in X.
> > 2. Is there any way that I can maintain multiple PREV values for an
> > indicator? What about PREV -1 and PREV -2?
> >
> > In our Intermediate Term System, we have an indicator we
> > calculate whereby
> > we maintain the last 18 results, always keeping the last 18
> > values available
> > to us for calculations. We use the first 6 for a short-term
> > indicator, the
> > second six for an intermediate-term indicator and the final six for a
> > long-term indicator.
> >
> > I'm trying to avoid having to do much additional programming
> > outside of
> > MetaStock, if possible, so I would appreciate any assistance.
> > Does anyone
> > know of an add-in that's available that would provide array or table
> > capabilities to MetaStock?
> >
> > Thanks for any help.
> >
> > Guy
> >
> > Paranoia...you only have to be right once to make it all worthwhile!
> >
> >
> >
>
|