Yup, KEY is part of SwiftForth's console personality - which is vectored
in user memory. Each windows callback (ie MAG-MESSAGES) contains its
own user area with minimal initialization. Even if you were to vector
KEY with the word OPERATOR'S, KEY would loop waiting for yet another
keystroke.

Try

  WM_CHAR RUN: WPARAM ADJUST_MAGNIFICATION 0 ;

Mike

-----Original Message-----
From: sftalk-bounce_at_forth.com [mailto:sftalk-bounce_at_forth.com]On Behalf
Of Jos'h Fuller
Sent: Friday, September 27, 2002 1:18 PM
To: sftalk_at_forth.com
Subject: [sftalk] Re: Problem with [SWITCH ... SWITCH]

Hi!

> WM_CHAR RUN: KEY ADJUST_MAGNIFICATION 0 ;
                    ^^^

Are you sure that you can use KEY here? My understanding is that the
WM_CHAR message brings with it the keycode of the pressed key already
and
you want to interrogate one of the message variables for it. If I recall
correctly, KEY is more intended for console-mode applications, here it
might actually be causing your abort because of a bad BIOS call or
something.

You might check one of the other examples, specifically guitetris.f,
which
manages keypresses in a separate [SWITCH that is called by the main
event
handler...

I'm just playing with the demo and all my Windows programming books are
at
home, so this advice is worth what you've paid for it... ;-)

Jos'h

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe sftalk" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/sftalk -- check them out!
Search the archives! Visit http://www.forth.com/search for details.
Received on Fri Sep 27 2002 - 13:38:37 PDT