[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: === Looping constructs. Other Deficiencies in QP



PureBytes Links

Trading Reference Links

Other deficiencies in QP.

QP should have a standard designation for tickers that have more than one
class of issue.  For example Raytheon class A is usually given as RTN.A.  QP
uses RTN  A (ticker and 2 spaces).  Other tickers in the QP database can
have one, two, or three spaces between the main ticker and the class
designation. Better still use the more or less standard designation of RTN.A
(ticker+dot+class).

When QP cannot find a ticker in its data base, the error message should also
give the folder in which this occurred.
Related to this, the Report Of Changes is incomplete and during a download
QP does not show all the obsolete/changed tickers in my folders. That is, I
don't get a messages that certain tickers are not in the QP data base.
Periodically I have to manually scan my folders for obsolete tickers.

Some of the scans that are supplied with the program are useless, others are
erroneous or have incomplete commentary.

QP should have a hard copy manual. This should be written by a tech writer
and not by a programmer. Most programmers are poor writers. Metastock hard
copy manuals and on line help are examples of superior manuals and
documentation.
.
Lionel Issen
lissen@xxxxxxxxx
----- Original Message -----
From: Gary Lyben <gary@xxxxxxxxxxxxxxx>
To: <metastock@xxxxxxxxxxxxx>
Sent: Wednesday, February 23, 2000 7:34 AM
Subject: RE: === Looping constructs.


>
> What is it that you want to do in the system tester that you can't do
> now?
>
> Gary
>
> -----Original Message-----
> From: Daniel Martinez [mailto:DanM@xxxxxxxxxx]
> Sent: Tuesday, February 22, 2000 10:42 PM
> To: metastock@xxxxxxxxxxxxx
> Cc: Equis Suggestion Box
> Subject: Re: === Looping constructs.
>
>
> I think Equis, for it's next MetaStock version, should have built-in VBA
> support.  Also, MS should have a MS language converter for conversion to
> VBA.
> This way, experienced users can gradually move to VBA.  New users can
> start
> using VBA right away instead of learning MS.  VBA is becoming the
> standard
> language for users.  Even Corel is getting the message by including VBA
> support
> in their Office 2000.  While this may seem difficult, MicroSoft Word has
> macro
> AND VBA support.
>
> Right now, we must buy an extra SDK, Power Basic or equivalent, figure
> out how
> to create DLL's and learn how to link them to MS.
>
> About Traderware:  Something many on this List may not know.  Traderware
> will
> not work in Win9x.  You must use Win NT.  If you try to use Win9x, it
> will
> crash after about an hour.  Their salesman told me Win9x won't "return
> system
> resources" correctly.  I have never heard of this type of problem in
> Win9x
> before so it doesn't make much sense to me.  I doubt RadarScreen has
> this
> problem.
>
> Daniel.
>
>
>
> David Bozkurtian wrote:
>
> > At the least, it should do these things. Not to mention simple flow
> control
> > and repeating structures such as For Loops, While, Select Case. What
> about
> > passing parameters to custom indicators?
> >
> > It is probably futile to expect these enhancements in the near future
> from
> > Equis. Any Developers/Traders out there interested in putting our
> noggins
> > together to create a shareable version of what we want?
> >
> > I know the folks at Traderware have a very interesting product (M
> Brown, I
> > know you are reading), but the last time I checked the cost was way
> over my
> > budget.
> >
> > Hopefully helpful folks like yourselves will not only identify the
> problems
> > facing technical analysts, but bring to the table real workable
> solutions
> > (preferably turnkey) to benefit the entire list.
> > It's happening piecemeal now with people trading system, indicator,
> expert,
> > and explorer code. But still, you have to admit, that we are in the
> dark
> > ages.
> >
> > We have no accepted standards for measuring system effectiveness, no
> > standards for stop rules. Looks like the whole field is still
> evolving,
> > which is a good thing. I continue to believe that the Internet and the
> > sharing of ideas will revolutionize our field over the next few years.
> It's
> > an exiting time, and great to be part of this list group. I think
> other
> > agree that what some of us have learned on this list is not found in
> print
> > anywhere else, or at least not easy to come by.
> >
> > Thanks list.
> >
> > David
> >
> > From: "Kolade, Adeniyi" <adeniyi.kolade@xxxxxxxxxxxxxxx>
> > Reply-To: metastock@xxxxxxxxxxxxx
> > To: "'metastock@xxxxxxxxxxxxx'" <metastock@xxxxxxxxxxxxx>
> > Subject: === Looping constructs.
> > Date: Tue, 22 Feb 2000 16:14:01 -0000
> >
> > Hi all
> >
> > Do you not think that Equis should
> >
> > 1  Include looping constructs in the Metastock formula language
> >
> > and
> >
> > 2  Make the tiny screen area for programming in the Explorer, the
> System
> > Tester and the Expert Builder expandable to one page  at least
> >
> > Further can anyone tell me how to make the FFT function works in an
> > exploration. I've tried it out but it returns N/A
> >
> > Thanks
> > ade Kolade