gixb@prism.cs.orst.edu (Brian Gerard Gix) (07/30/89)
I'm looking for documentation on WaitNextEvent, and aside from the references in the TechNotes, I can't find anything... Is there any alternate sources of truth I could look into, aside from Inside Mac, (unless it is documented there and I just haven't been able to find it) or can anyone give me a good and thorough run down on when to use it, what all the fields are for, etc. Please post or send me e-mail at: gixb@prism.cs.orst.edu Thanks --Brian
jpd00964@uxa.cso.uiuc.edu (08/01/89)
> I'm looking for documentatI'm looking for documentation on WaitNextEvent
I actually first came across that routine in the Book Mac Programmer Primer.
The book is very well written and all of its source code is in LSC.
Michael Rutman
Softmed
tim@hoptoad.uucp (Tim Maroney) (08/03/89)
Does anyone have any example code which illustrates the use of the mouse region argument to WaitNextEvent? -- Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com "As I was walking among the fires of Hell, delighted with the enjoyments of Genius; which to Angels look like torment and insanity. I collected some of their Proverbs..." - Blake, "The Marriage of Heaven and Hell"
earleh@eleazar.dartmouth.edu (Earle R. Horton) (08/03/89)
In article <8211@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes: >Does anyone have any example code which illustrates the use of the >mouse region argument to WaitNextEvent? Yes, this example is from the main event parsing area of my pulsar simulation program. It is based on examples in Apple Sample Code, but it is a little more involved, I like to think, because it handles multiple application window types. The code which I based this on is in TESample.c, which is part of Sample Code number 2. The mouse region argument is used by MultiFinder to wake up your application when it is in front, and the cursor moves out of this region. This lets you wake up, change the cursor, and go back to sleep again. Disclaimer: This source code works. It is, I think, thoroughly debugged. Your mileage may differ. Earle R. Horton /* * The ww_pwindow data type is a pointer to a structure which has * first a WindowRecord, a DialogRecord, or a TPrPort at byte * offset zero. Then, there are all kinds of goodies like * cursor Handles, TextEdit Handles, ProcPtrs, Print Record * Handles, and an endless variety of pointers to specialized * data structures for the manipulation of window and document * contents. The cursor modification routine knows enough about * the contents of the various windows I have in my program to be * able to make an educated guess as to which cursor should be * used. */ RgnHandle cursorRgn; /* * The routine for getting events from the event queue. Returns what * kind of event was received, in case it gets called from a background * procedure. */ short doevents() { EventRecord myEvent; register ww_pwindow activeWindow; short result; /* * See if there's an event. Toss {Wait|Get}NextEvent's return value, 'cause * a false is the same as getting a nullEvent, and a true any other * event. */ if(WNEExists){ activeWindow = (ww_pwindow) FrontWindow(); if (wwmine(activeWindow)) { SetPort(activeWindow); SetupCursor(activeWindow,cursorRgn); } (void)WaitNextEvent(everyEvent,&myEvent,sleeptime(),cursorRgn); }else{ SystemTask(); (void)GetNextEvent(everyEvent, &myEvent); } /* * Make sure we have the right cursor before handling the event. */ activeWindow = (ww_pwindow) FrontWindow(); if (wwmine(activeWindow)) { SetPort(activeWindow); SetupCursor(activeWindow,cursorRgn); } /* * Stash result, 'cause eventparser() just might change it. */ result = myEvent.what; /* * Pass the event to the event parser. */ eventparser(&myEvent); return result; } /* * Set up the cursor if one of our windows is frontmost. Also calculate * the mouse-moved region for WaitNextEvent(). Three possibilities exist * for the mouse region. These are a region containing our window's visRgn, * a region containing active text, and a region which is everything but * one of the first two. * Caller has to do a SetPort() to the target window first. * * A major shortcoming of this approach is that this routine has to know * something about the structure of the window contents, and allows for * only one cursor to be defined per window. An improvement would be * to have a special routine like this for each window type, with most * windows using the default. Then, one could have a real fancy window * with lots of logical regions and a different cursor for each. * * Implementation is left as an exercise for the reader. */ SetupCursor(wptr,region) ww_pwindow wptr; RgnHandle region; { RgnHandle arrowRgn,windowRgn; /* Scratch regions. */ Rect cursRect; /* Active Rect. */ Point mouse; /* Mouse location in global coordinates. */ Boolean useSpecialCursor; /* We have a special cursor for use in this window. */ Point originPt; /* TopLeft of our portRect in global coordinates. */ useSpecialCursor = false; /* * Allocate scratch regions. */ arrowRgn = NewRgn(); windowRgn = NewRgn(); /* * Make a real big region for outside of our window. */ RectRgn(arrowRgn,&hugerect); /* * If the front window is ours, and if it has a special cursor * associated with it, then we will want to keep track of where * the mouse is in relation to the region where this cursor is * supposed to be active. */ if ( wptr->ww_cursor != nil ) { /* * Find out where the mouse is, globally speaking. */ GetMouse(&mouse); LocalToGlobal(&mouse); /* * A window with text. Use the TextEdit Record's viewRect. */ if( wptr->ww_text != nil ){ cursRect = (*wptr->ww_text)->viewRect; } /* * If it's a modeless dialog, try to find out if the mouse is in * an active editText item. If you are of the Maroney persuasion, * then you use FindDItem() here to determine if the mouse is in * ANY editText item. */ else if( wptr->textH != nil ){ cursRect = (*wptr->textH)->viewRect; } /* * If it's some other kind of window, assume the portRect. Subtract * width of standard scroll bars if present. */ else{ cursRect = wptr->ww_rec.port.portRect; if(wptr->ww_vScrollBar != nil){ cursRect.bottom -= SCROLLBARWIDTH - 1; } if(wptr->ww_hScrollBar != nil){ cursRect.right -= SCROLLBARWIDTH - 1; } } /* * Make a region corresponding to the visible part of our cursRect, * in global coordinates. */ RectRgn(windowRgn,&cursRect); SectRgn(windowRgn,wptr->ww_rec.port.visRgn,windowRgn); SetPt(&originPt,0,0); LocalToGlobal(&originPt); OffsetRgn(windowRgn,originPt.h,originPt.v); /* * Subtract our window region from the everything else region. */ DiffRgn(arrowRgn,windowRgn,arrowRgn); /* * Region parameter is the region the mouse is in. Special * cursor if it is our window region. */ useSpecialCursor = PtInRgn(mouse,windowRgn); } if(useSpecialCursor == true){ CopyRgn(windowRgn,region); SetCursor(*wptr->ww_cursor); }else{ CopyRgn(arrowRgn,region); SetCursor(&qd.arrow); } /* * Kill scratch regions. */ DisposeRgn(arrowRgn); DisposeRgn(windowRgn); }
shebanow@Apple.COM (Andrew Shebanow) (08/03/89)
DTS has published several pieces of code documenting the use of mouse
moved events. I recommend that you look at the TESample program, in
whichever form you feel most comfortable (Pascal, C, C++, Object Pascal).
These samples are available via anonymous ftp from apple.apple.com.
Have fun,
Andrew Shebanow
MacDTS
Andrew Shebanow, Amway Representative
Developer Technical Support, Apple Computer, Inc.
------------------------------------------------------------------------------
INTERNET: shebanow@apple.com
UUCP: {decwrl, hoptoad, nsc, sun, amdahl}!apple!shebanowwdh@well.UUCP (Bill Hofmann) (08/04/89)
In article <8211@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes: >Does anyone have any example code which illustrates the use of the >mouse region argument to WaitNextEvent? /* return a region handle which is either the content of the * window passed (we assume it's the active one) or everything * but. If the mouse is inside the window, set the cursor to * a plus cursor, otherwise, reset to arrow */ RgnHandle AdjustMaus(wp) WindowPeek wp; { RgnHandle mausRgn; Point mausLoc; Rect windowRect; if (mausRgn = NewRgn()) { GetMouse(&mausLoc); LocalToGlobal(&mausLoc); /* use the content region of the window: it's * almost what we want, in global coordinates. * To be absolutely correct, we should use the * visRgn, which is in coordinate local to wp, * but represents what is *actually* visible, but * then we'd have to LocalToGlobal it, and * I'm too lazy just now. */ CopyRgn(wp->contRgn,mausRgn); if (PtInRgn(mausLoc,mausRgn)) SetCursor(*GetCursor(plusCursor)); else { RgnHandle temp = NewRgn(); CopyRgn(GetGrayRgn(),mausRgn); RectRgn(temp,&screenBits.bounds); UnionRgn(mausRgn,temp,mausRgn); DisposeRgn(temp); /* now mausRgn is the *whole* screen, including * the menu bar */ DiffRgn(mausRgn,wp->contRgn,mausRgn); /* Now, mausRgn is everything *BUT* the content * of the window. */ InitCursor(); } } return(mausRgn); } The return value of this routine can be passed to WaitNextEvent(), which will notify us if the mouse leaves the region with a mouseMoved app4Evt. In my real code, I use visRgn and mausRgn is a global, so I don't have to keep disposing the region before I call this routine (and I don't alloc a new region every time). But this'll give you the idea. -Bill Hofmann >-- >Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com > >"As I was walking among the fires of Hell, delighted with the enjoyments of > Genius; which to Angels look like torment and insanity. I collected some of > their Proverbs..." - Blake, "The Marriage of Heaven and Hell" "Sacred cows make the tastiest hamburger" -Abbie Hoffman