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

Re: Simple VB example



PureBytes Links

Trading Reference Links



Regards,
Ton Maas
ms-irb@xxxxxxxxxxxxxxxx
Dismiss the ".nospam" bit (including the dot) when replying and
note the new address change. Also for my Homepage
http://home.planet.nl/~anthmaas


----- Original Message ----- 
From: Nicholas Kormanik <nkormanik@xxxxxxxxxx>
To: <metastock@xxxxxxxxxxxxx>
Sent: donderdag 13 januari 2000 20:47
Subject: Simple VB example


> This may seem simple-minded, but many of you folks have for a long time been
> talking about VB and VBA, but for the life of me I can't think of what in
> the world you guys are attempting to accomplish.  And I bet I'm not alone.

Accomplish is not the right word, since the underlay to design added functionalities
and tools is already available, only it is not included in the standard program, eg
equis will not allow you to have it (unless you want to fork out another $100 for the
VB compatible library file, a dll file that comes standard free with other programs).

Lets asume the Explorer wasn't included in the standard program, than with VB
you can "easy" build one yourself. This time Equis has build it for you, most likely
in C, so you will not have to re-invent this wheel, but the underlay+tools are also in
the same way available to you, the user, when coding it in VB AND if you have
the above missing library dll file.
  
> Could any of you give a clear example of what you are using VB for that
> somehow extends what MetaStock normally does? (or can not presently do by
> itself?)

MSK by itself cannot do anything, eg it does nothing unless you, the user,
give "input" to the program (interacting).
Currently the required "input" are the mouse clicks+keystrokes choosing and
answering to functions and giving click/key replies to the by program returned dialogs.
In the near future this will also include speach (that is if the program wants to
stay Windows compatible).

Using added automating features(ScriptIT,AutoIT,VB etc) , you can have most
of your "input", eg your daily effort and time consuming hand-jobs, automated.
Including VBA to the program would have also consist of a recorder, so that
un-aquinted users could simply record and play back their favourite actions in
the program or ref up another program/exit the program. 

Also you can use the other features of these automating programs/language
to write "systems" that work with formula's/experts/filters/systest/other ideas
the program isn't capable of doing by itself or that equis will not build-in or
equis will not let you have control off. 

> And how does it help with your decision making and trading?

First what do you think of less time spend on software and inabilities of the
standard MSK program and more free time for other things (coffee, trading,
testing,etc.) and making program user definable?

Second, how does the current standard program help you with your decision
making and trading?

Third, when you first bought the program and throughout future time later, you
had to (re-)configure the program right to your likings, eg to currently be able to
make the program your $'s worth that you spend on it.

Ofcourse that amount spend have not ever been a waste, but once working in/with
the program and also from experience working with/within other programs, you will
soon find out that you have also bought a very simple straight forward peace of
software program.

These days computers can do the mass workload for you, and that said, it gets
only very basicaly and very limited done in/with the current program.

Any added functionality(ies, esp. automating) will then further help you with your
program actions and directions, eg both in/for the time saving automating stuff as
well as for creating your own designable exceptional "systems", which could be
endless considdering the human brain's inventive capacities.

Fourth, I have as yet to learn enough of the VB language so as to esthablish the above.
Thus, for the moment, have to rely on my current configuration settings and live
with its limitations.

I am sort of at the moment in the same position when I first bought the program and
had to experiment for a while first, before I was later able to handle the
program+its features+its formula language.
This is also, cause VB slightly involves more than "just" reading a manual and starting
a formula.  

> Thanks,
> Nicholas
> 
>