sam@neoucom.UUCP (Scott A. Mason) (04/28/89)
Hello,
I've just purchased the LSC 3.0 compiler, and am trying to compile some
of my programs that I wrote. I am having trouble with the event loop.
When the program is run, no mouse events are posted by the event manager.
(At least the command-Q autokey is set to quit, whew). What's the problem
here? This program worked with the Aztec C compiler which I no longer use.
(Comparison of compilers deleted)
While I'm at it, how does one go about updating a non-TextEdit window.
Do I have to use CopyBits, or is there some other easier way to do it?
--
--------------------------------------------------------------------------------
"If it ain't broke, don't fix it," and certainly don't blame me.
UUCP: {pitt, scooter, hal, cwjcc}!neoucom!sam INTERNET: sam@neoucom.UUCP
Scott A. Mason, Coordinator of Systems Operations, NEOUCOMsiegel@endor.harvard.edu (Rich Siegel) (04/30/89)
In article <1604@neoucom.UUCP> sam@neoucom.UUCP (Scott A. Mason) writes: >Hello, > >I've just purchased the LSC 3.0 compiler, and am trying to compile some >of my programs that I wrote. I am having trouble with the event loop. >When the program is run, no mouse events are posted by the event manager. How about a piece of code such as our GetNextEvent() call, which illustrates he problem? >While I'm at it, how does one go about updating a non-TextEdit window. >Do I have to use CopyBits, or is there some other easier way to do it? To update any kind of window, just call your routine which draws the window's contents. --Rich ~~~~~~~~~~~~~~~ Rich Siegel Staff Software Developer Symantec Corporation, Language Products Group Internet: siegel@endor.harvard.edu UUCP: ..harvard!endor!siegel "She told me to make myself comfortable, so I pulled down my pants and sat in the pudding." -Emo Phillips ~~~~~~~~~~~~~~~