Couple o' questions...

In order to receive messages from a 3rd party .DLL I was trying to wedge
a non-system message number into the default Swiftforth window message
loop, and tried the method proferred on page 161 of the manual to add to
the message handler as follows:

[+SWITCH SFMESSAGES ... etc

...but it seems that there is no SFMESSAGES switch anywhere. What is the
name of SwiftForth's default console window message loop switch
structure? Is this declared in another vocabulary? I hunted around, but
to no avail.

And this leads me to my next question... Those WM_CREATE and other
constants in the switch structures are values that can not be computed
at run time right? That is to say, those values that are tested in the
switch have to be put in the structure at compile time, it looks like.
So, just what is the best way to reserve a message number for use in my
apps without any danger of conflict. I thought maybe that the Windows
RegisterWindowMessage function would offer hope, but the message number
is captured at run time, and so it can't go into the switch, which is
created at load time. Uh, does this make any sense? The question is, how
can I really be sure I am using a unique message number if I make one up
within the range of values above WM_USER?

Aside: I've been pleased with how easy Windows programming is, but also
amazed at how similar to Amiga 'Intuition' programming it is, even down
to the names of functions and stuff. Anybody else notice this?

Bob
*****************************************************
**** Bob Dickow (dickow_at_uidaho.edu) ******
*** Hampton School of Music, Univ of Idaho *
** USDA Zone 5 *********************************
Received on Tue Jun 27 2000 - 23:34:24 PDT