home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!microsoft!hexnut!ericsc
- From: ericsc@microsoft.com (Eric Schlegel)
- Subject: Re: Button() not callable from interrupt ?
- Message-ID: <1992Nov10.163653.1554@microsoft.com>
- Date: 10 Nov 92 16:36:53 GMT
- Organization: Microsoft Corporation
- References: <ROBERT.92Nov9103642@wsooti11.info.win.tue.nl>
- Distribution: comp
- Lines: 19
-
- In article <ROBERT.92Nov9103642@wsooti11.info.win.tue.nl> robert@wsooti11.info.win.tue.nl (Robert Lukassen) writes:
- >I ran into a bit of trouble the other day when I tried to read the state of the
- >mouse-button from an interrupt-routine. I know that the state of the button
- >is represented by a single bit in some low-memory variable and this works well,
- >but why does (the old version of) Inside Macintosh claims that Button() can
- >move or purge memory. That is absolutely insane! A simple fetch of a low-memory
- >variable can't trigger a memory move or memory purge. What are they doing that
- >makes calling Button() so dangerous?
-
- Unfortunately, they're checking to see if journalling is on, and if so, making
- a call to the journalling driver, which CAN move memory. It's not just a simple
- fetch.
-
- I had the same problem - currently I'm reading MBState directly, for lack of
- a better solution, but I sure wish there was a better way...
-
- -eric
- ------
- My opinions, not Microsoft's.
-