|
PureBytes Links
Trading Reference Links
|
> The statement does not say the MetaStock Professional 7.0 and
> MetaStock for Windows 7.0 already support outside GUI functionality.
Hope that I do not "again(???) mis-interpret you" when you write that MSK
does not and will not (eg refuses to) support internal GUI functionality support.
1. You can hardly qualify PowerBASIC to be a helpfull addittion to the GUI,
a helping hand within the GUI that 99% of your users are looking for, and
which additionality is way overdue (and note again "that was promised
to be added" already way back in 1995) and what be of a real advantage
to your main stream of users(unlike PB, that will only be of an advantage
to some, if any at all...........).
2. PowerBASIC ill-logic poorly developped "programming language" just
turns anyone right off. Even off attempting to learn its heavy under-developped
"systamatics" for starters, eg for anyone who is willing to spend his valuable
time in yet again "learning yet another 'foreign' language" (where your formula
language can also be considdered to be a "foreign" language).
3. Since your own program is also -in an ancient fashion- dreadfully poorly
equiped with any GUI supporting tools, eg none are present and somehow
making your program alien (compared to advancees programs), therefore help
will always be required from outside (eg by applying third parties to) your program,
that will always have to done under 'messy conditions' (in a -user unfriendly- way).
4. On the side, as well, let PB be a first step to lending a (very costly) helping hand,
eg only in to extending a smaller part of the program only (formula handling) then
this sure is nowhere THE major step that is desperatly required, eg
a major (GUI) functionality overhaul would be well in its place here.
5. An automating tool is required, and for that job the PB extension is not the Tool.
Neither the MSX (for it being "ONLY" PB compatible).
I believe your sale figures will speak for themselves as to who is right here, eg
once the 7.0 version is on the market.
Since introduction of the new 7.0 -Pro version I cannot figure out what is realy
a driving force for anyone to upgrade from 6.52. It is an upgrade, in that some
"by many not wanted/useless to the majority of users" features have been added.
Perhaps I should spell it out liturarly for you what your users (and potentialy new users)
are/will be looking for (and what companies like Microsoft understand far much better,
eg look at the new Win2k):
Addding of
1. User definable Objects and related
2. User definable (window) Controls and related
3. User definable Menu's and related
4. User definable actions (to be choosen from these Menu's menu's)
5. User definable automating with and for the #'s 1 to 4
6. Company policy break in letting third parties enter in on these # 1 to 5
a. for having (and creation of) language definable versions
b. for having free programs like VBscript do what any user requires
from his/hers program's repitative tasks and therefore let other programs
enter on this "currently un-accesable tasks & routines".
Since these are part of the (any programs) Operating System, they were also
freely updated and added to the OS. Now, how about you?
-a locked up program and
-no intensions on program improvement(s) (requested/required by users
on the above and already for years in a row present functionalities)
So for now, must end and will see you perhaps in version 8.0 (somewhere
due in year 2002+, or v9.0) if you still have me around as a customer.
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
cc MetaStock List
----- Original Message -----
From: Equis Support <support@xxxxxxxxx>
To: 'A.J. Maas' <anthmaas@xxxxxxxxx>
Sent: zondag 5 december 1999 1:26
Subject: RE: Support = required
The statement in the message is in reference to MSX DLL. What the statement
says is that MetaStock Professional 7.0 already contains MSX DLL support as
will MetaStock for Windows end of day. The statement does not say the
MetaStock Professional 7.0 and MetaStock for Windows 7.0 already support
outside GUI functionality.
Equis Support
http://www.equis.com/
http://www.equis.com/customer/support/
Please include previous email answers and questions in your response.
Please ask only one question per email. If you have to ask several
questions please send each question as a separate email.
Equis and MetaStock and MetaStock Professional are registered trademarks of
Equis International. Achelis Binary Wave, The DownLoader, Expert Advisor,
OptionScope, Quotecenter, and Smart Charts are trademarks of Equis
International.
> -----Original Message-----
> From: A.J. Maas [SMTP:anthmaas@xxxxxxxxx]
> Sent: Monday, November 29, 1999 5:04 PM
> To: Equis Support
> Cc: Metastock-List
> Subject: Re: Support = required
>
> Hello Equis Support,
>
> My 1st question's "The qoute to be completed" as you refer to it, stems
> from my original reply mail
> (printed right here below) to Cheryl's original "PowerBASIC"-mail that she
> had send to the MetaStock-List
> and which reply-mail I forgot to also send on SEPERATLY to her at Equis
> Support as well. Anayway, that
> mail is also printed -more further down- below.
> The issue here at stake is Cheryl's statement at the bottom of her mail,
> right below the "new MSX's
> non-accessability to the GUI/DLL"-section, eg about the functionalities
> that MSX cannot and the newer
> MetaStock PRO 7.0 and EOD 7.0-versions supposeably CAN perform. We, your
> buyers+users, are here
> sort of left in the dark as to the clearity of the statement:
>
> > Things that you cannot do with an MSX DLL include:
> > * GUI functions including plotting and user dialogs.
> > * Access the standard MetaStock built-in functions from within your DLL
>
> > This capability is already in MetaStock Professional 7.0 and will be in
> the
> > upcoming MetaStock End-Of-Day 7.0.
>
> So far, your users/buyers unawareness of this "capability to access the
> GUI or my DLL already being included or
> to be included in the newer programs" requires a more detailed explanation
> to the extend of how this can
> be seen in relation to what your users already had (read: I do not know of
> it and so do many other users not know about it),
> and since this will be a new feature:
> -than how is this been added, eg previous program versions
> weren't equiped with these features.
> Sometime back in 1995, in your Spring 1995 No.2 (or 3) Monitor-NewsLetter
> you made already a public announcement
> to that extend, "that Visual Basic as a programming language is being
> added", but up till now, so far, have yet to see
> the "prosperous deeds being put into action".
>
> Therefore again please 'end' the "unfinished quote":
> "For accessing the above functionalities, wich are most intresting to
> users in/for their automation
> +programming efforts on program's 'daily usage' functionalities and of
> which most of these are
> held in dll, ocx or com files and for which most are also commonly shipped
> with any other
> applications/programs and which access is therefore also usualy provided
> for free by most
> software-makers, eg via their program's being (VB) Visual
> Basic-compatable, you can...............
> ..........................................................................
> .........................................................".
>
> If this answering is to pre-mature, impossible and front running on later
> this year to be announced news that you will
> finally add the missing "straight-forward programming access to your
> program" feature, than I am afraid "that's to late", eg
> overhere it is the talk of the town (but will be a major dessalution if
> adding it gets posponed again, eg and a tremoundous
> slap in the face for the advancees having had bought program on
> "programming features" recommendations).
>
> I think it also calls for you to explain the working structure and its
> future of the earlier announced (see Cheryl's mail below)
> but on pure DOS based PowerBASIC program that had a virtual Windows
> compatabillity (Win32s) added (DOSbox), but
> which very old DOS and Win3.11 techniques will be limited + cut down in
> use and cease to exist in the future Windows OS
> versions (2k+, 64-bit).
> (Microsoft has announced that in future programs it will not allow these
> virtual machines to operate anymore, eg access
> to DOS (Win3.1) will not be available anymore either (perhaps not on start
> up)).
>
> Thank you kindly for forwarding the other 2 questions on to your design
> dep., of which only the latter 3td-?URO
> is "cosmetic and of a less pranging importance" urgence, but surely know
> that you+your designers can see the
> importance in adding the 2nd question's (also cosmetic(?))
> Switches&Parameters features to the program.
>
> Regards,
> Ton Maas
> ms-irb@xxxxxxxxxxxxxxxx <mailto: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: A.J. Maas < anthmaas@xxxxxxxxx <mailto:anthmaas@xxxxxxxxx>>
> To: Metastock-List < metastock@xxxxxxxxxxxxx
> <mailto:metastock@xxxxxxxxxxxxx>>
> Sent: donderdag 4 november 1999 1:33
> Subject: Re: Increasing the MetaStock(R) Formula Language with MetaStock 7
>
> > Dear Cheryl + EquisSupp,
> >
> > > Things that you cannot do with an MSX DLL include:
> > > * GUI functions including plotting and user dialogs.
> > > * Access the standard MetaStock built-in functions from within your
> DLL.
> >
> > For accessing the above functionalities, wich are most intresting to
> users in/for
> > their automation +programming efforts on program's 'daily usage'
> functionalities
> > and of which most of these are held in dll, ocx or com files and for
> which most
> > are also commonly shipped with any other applications/programs and which
> > access is therefore also usualy provided for free by most
> software-makers, eg
> > via their program's (VB) Visual Basic-compatabilitiness, you
> can.......................
> >
> ..........................................................................
> ......................................... .
> >
> > The above was missing in your excellent explanation briefing (at the
> finishing
> > end) on the new in MS v7 included MSDK's "MSX-API"-functionality
> extension
> > feature.
> >
> > Hope this time around you can finish it, by providing us the "missing
> dotted"
> > line(s) at the end!.
> >
> > Adding the PowerBASIC compatabliness is surely an attractive programming
> tool,
> > but is much for the very advanced users that are looking for "Accounting
> Programming"
> > ways within the MS program, and not for the majority of users who would
> like programming
> > and automating the average Accounting- and most of the Technical
> functionalities of
> > the program, eg accessable through the parts mentioned at the top (and
> mentioned
> > here above in the "Things you cannot do
> with.................."-section).
> >
> > Regards,
> > Ton Maas
> > ms-irb@xxxxxxxxxxxxxxxx <mailto: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>
> >
> > ------snip------
> >
>
> ----- Original Message -----
> From: Equis Support < support@xxxxxxxxx <mailto:support@xxxxxxxxx>>
> To: < metastock@xxxxxxxxxxxxx <mailto:metastock@xxxxxxxxxxxxx>>
> Sent: woensdag 3 november 1999 0:13
> Subject: Increasing the MetaStock(R) Formula Language with MetaStock 7
>
> > I've noticed several emails lately discussing MetaStock's Formula
> Language
> > capabilities. I would like to take this time to introduce you to a new
> > feature added in MetaStock 7. The new MetaStock External Function (MSX)
> > Application Programming Interface (API), available in the MetaStock
> > Developer's Kit, allows software developers to dynamically add
> externally
> > defined functions to the MetaStock Formula Language, in MetaStock
> version
> > 7.0 and later.
> >
> > When MetaStock initializes, it scans a pre-defined folder, looking for
> any
> > DLLs that correctly implement the MSX API. When an MSX DLL is found,
> the
> > functions that it implements are automatically added to the MetaStock
> > Formula Language.
> > These new functions can be used to create Custom Indicators,
> Explorations,
> > System Tests and Expert Advisors using MetaStock's formula tools.
> > The MSX API supports any programming language that meets the following
> > criteria:
> > * exports DLL functions by name
> > * supports the stdcall stack frame convention
> > * creates 32-bit DLLs for Windows 95, Windows 98, or Windows NT
> > version 4.0 or greater
> > This type of DLL is commonly called a Win32 DLL.
> >
> > Note: Microsoft Visual Basic does not have the capability to produce a
> Win32
> > DLL. Therefore, MSX DLLs cannot be written in Microsoft Visual Basic.
> A
> > good alternative for VB programmers is PowerBASIC, an inexpensive
> compiled
> > Basic that is syntax-compatible with VB and can produce Win32 DLLs.
> > MSX DLL Capabilities
> > The functions that can be implemented in MSX DLLs are similar in
> behavior to
> > the Standard built-in MetaStock functions. In other words, MSX
> Functions
> > can be written to perform calculations based on any available price data
> or
> > results of other functions. All MSX DLL functions return a data array.
> > This exactly parallels the behavior of the MetaStock built-in functions.
> > The returned data array can be plotted by Custom Indicators or used in
> any
> > way that a standard built-in function can be used.
> > MSX DLLs can perform calculations of virtually unlimited complexity.
> You
> > have the full power of conventional programming languages like C or
> Pascal
> > with all of their logic, data manipulation and rich flow-control
> > capabilities.
> > Things that you can do with an MSX DLL include:
> > * Implement functions not provided with MetaStock.
> > * Perform complex calculations on price data.
> > * Provide multiple functions in a single MSX DLL.
> > * Access stored MetaStock price data using MSFL (included in the
> > MetaStock Developers Kit - see the MSFL documentation for details).
> > * Create functions that can be used by Custom Indicators, System
> > Tests, Explorations, and Experts.
> > * Distribute your compiled MSX DLL to other users.
> >
> > Things that you cannot do with an MSX DLL include:
> > * GUI functions including plotting and user dialogs.
> > * Access the standard MetaStock built-in functions from within your
> > DLL.
> >
> > This capability is already in MetaStock Professional 7.0 and will be in
> the
> > upcoming MetaStock End-Of-Day 7.0. The MetaStock Developer's Kit is
> expected
> > to be available in late November. For the latest details periodically
> check
> > <http://www.equis.com/partners/developers/>
> >
> > Cheryl Elton
> > Product Development
> > Equis International, Inc
> > <http://www.equis.com>
> >
>
>
> ----- Original Message -----
> From: Equis Support <mailto:support@xxxxxxxxx>
> To: 'A.J. Maas' <mailto:anthmaas@xxxxxxxxx>
> Sent: maandag 29 november 1999 18:53
> Subject: RE: Support = required
>
> Mr. Maas,
>
> For the first question, we're not sure where you received the quote
> that you are trying to have completed. That quote has nothing to do with
> the MSX since it does not interface to VB or VBA.
>
> The second and third are design issues. They have been forwarded to
> our design department and will be left in their hands.
>
> Sincerely,
>
> Equis Support
> <http://www.equis.com/>
> <http://www.equis.com/customer/support/>
>
> Please include previous email answers and questions in your
> response.
>
> Equis and MetaStock and MetaStock Professional are registered
> trademarks
> of Equis International. Achelis Binary Wave, The DownLoader, Expert
> Advisor, OptionScope, Quotecenter, and Smart Charts are trademarks
> of
> Equis International.
>
>
>
>
> -----Original Message-----
> From: A.J. Maas [mailto:anthmaas@xxxxxxxxx]
> Sent: Monday, November 22, 1999 4:15 PM
> To: Equis Support
> Cc: Metastock-List
> Subject: Support = required
>
>
> The following are 3 very urgent questions!!
> Can you please reply ?
>
> 1. Question that was recenty raised in my 19991104-mail to
> you, Equis Support, with subject:
> "Re: Increasing the MetaStock(R) Formula Language with
> MetaStock 7", which
> up till now, unfortunately, is still left unanswered (by
> your Support Dep.).
>
> > Things that you cannot do with an MSX DLL include:
> > * GUI functions including plotting and user dialogs.
> > * Access the standard MetaStock built-in functions from
> within your DLL.
>
> "For accessing the above functionalities, wich are most
> intresting to users in/for their automation
> +programming efforts on program's 'daily usage'
> functionalities and of which most of these are
> held in dll, ocx or com files and for which most are also
> commonly shipped with any other
> applications/programs and which access is therefore also
> usualy provided for free by most
> software-makers, eg via their program's being (VB) Visual
> Basic-compatable, you can...............
>
> ..........................................................................
> .........................................................".
>
> The above was missing in your excellent explanation briefing
> (at the finishing end) on the new
> in MSK v7 included MSDK's "MSX-API"-functionality extension
> feature.
>
> Hope this time around you can finish it, by providing us the
> "missing dotted" line(s) at the above end!.
>
> 2. Why do the MetaStock and Downloader programs on 'Run' do
> not have any
> command line Switches/Parameters ?
>
> Many programs have switches/parameters added to their
> command lines, that can be used
> by user to run/open the program with/on certain conditions.
>
> For example adding an /E switch/parameter to the standard
> MSK command line could then
> enable user to open up with the MSK's Explorer :
> C:\Equis\Mswin\mswin.exe /E
> or an /S to open up with the MSK's SystemTest :
>
> C:\Equis\Mswin\mswin.exe /S
> or for the DLR's Convert Tool for the daily file updates :
> C:\Equis\Dlwin\dlwin.exe /C
>
> I usualy work with Layouts so I won't go further in to the
> fact that Charts+Layouts can be
> opened directly from the (Run) command line :
> C:\Equis\Mswin\Charts\MyChart.mwc
> or the equivelant :
> "C:\Equis\Mswin\mswin.exe
> C:\Equis\Mswin\Charts\MyChart.mwc"
> will both open the Chart named MyChart in the Charts folder.
>
> But advanced programs do also have advanced command-line
> procedures (switches and parameters)
> to directly open a program with a by user desired Tool (a
> sub program).
> These via parameters and switches (common in most PC
> programs) advanced commands procedures
> are up till now not been added/available. They are not
> available to user :
> neither for the stand-alone MSK program and not for the
> covered DLR program.
>
> 3. Tho slightly cosmetic of nature, is this question: are
> MSK/DLR also EURO (?) Compatible ?
>
> Refering to your previous mailings/billboard announcements,
> in which you stated that
> the MetaStock/Downloader programs are ?URO ready, and with
> the excellent new version
> of the AutoIt program being capable to add(send)
> the ASCII-codes(characters) to a security's Name field
> ----------
> "like when using using the ALT key and the numeric keypad
> (e.g. ALT+65 = 'A' or ALT+0128 = '?' or ALT+0165 = ' ')"
> ----------
> and have noticed that once one of the ASCII (via
> ALT+Numblock) characters is required, the Downloader
> will reflect and produce the sign correctly, but that
> the MSK/DLR-programs will not ever produce
> the ? sign, let alone correctly. All that can be seen is a
> single fat Bold vertical bar. As you can see above,
> here on my PC and for in this at the moment used Outlook
> Express mail-program, the ? sign does come
> up very nicely. It will also work very well and come up
> nicely in all of the other ? sign-compatible programs.
>
> From me here typing these charcters into this mail, you can
> notice that my keyboard's numeric
> keypad-functionality and the input + procedure (see "ALT+"
> above) are here working perfectly, eg
> upose to the fat 'bar' produced in MSK's or DLR's Name
> fields (see inserted gif below).
> However, thus not within the Downloader v7.0 and not within
> the Metastock v6.52 programs.
>
> To test for the EURO (?) sign Compatibility - using the
> "ALT+0128" procedure:
> -in MetaStock: create a New Custom Indicator and
> send above code to its Name field.
> -in the Downloader: create a New Security and send
> above code to its Name field.
>
> Regards,
> Ton Maas
> ms-irb@xxxxxxxxxxxxxxxx <mailto: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>
>
>
>
>
>
>
> AutoIt v2.21 released
>
> AutoIt v2.21 has been released at
> <http://www.hidden.demon.co.uk/AutoIt/index.html>.
> The recent history file is listed below.
>
> ------------snip-------------
>
> AutoIt History
>
> 20/11/99 - v2.21
>
> * Can now Send decimal ASCII codes, like when using using the ALT key
> and the
> numeric keypad (e.g. ALT+65 = 'A'). Very useful for sending characters
> that don't
> usually work (e.g. '~' on an Italian keyboard).
>
> 18/11/99 - v2.2
>
> * Can now Run programs as either hidden, maximized or minimized (great
> for avoiding black
> screens when executing DOS commands)
> * RunWait will put a program's return code in %ERRORLEVEL%
> * The WinWait group of functions can be set to timeout after a period
> of time
> (%ERRORLEVEL% can be checked to see if the function timed out or not)
> * WinShow command added (previously, there was no way to "undo" a
> WinHide!!!!)
>
> -------------snip-------------
>
> AutoIt Homepage: <http://www.hidden.demon.co.uk/AutoIt/index.html>
>
|