Important: The Event Manager is a legacy System 7 technology. You should use the Mac OS X Carbon Event Manager instead. See Carbon Event Manager Programming Guide.
This appendix describes functions that are not recommended or are not available in Carbon and Mac OS X. The API documentation for these functions has been moved to Event Manager Legacy Reference.
Table B-1 lists Event Manager functions that are not recommended in Carbon and Mac OS X. You should avoid using any calls that poll the state of the mouse button, as they use excessive processor time and slow down the system. In most cases you are more interested in the transitions of the mouse button rather than its instantaneous state, so you should adopt Carbon events and take action on mouse-up and mouse-down events. If you need to track the mouse while down, consider using the Carbon Event Manager functions TrackMouseLocation
or TrackMouseRegion
. If you need to know the button state, you should call the GetCurrentEventButtonState
function.
Name |
Porting Notes |
---|---|
|
You should avoid using any calls that poll the state of the mouse button. |
|
You should avoid using any calls that poll the state of the mouse button. |
|
You should avoid using any calls that poll the state of the mouse button. |
|
You should avoid using any calls that poll the state of the mouse button. |
Table B-2 lists Event Manager functions that are not available in Carbon and Mac OS X.
Name |
Porting Notes |
---|---|
|
The High Level Event APIs ( |
|
FKEYs are not supported in Carbon because they involve loading code from resources, which isn't supported under Carbon, and because very few applications use them. |
|
|
|
The High Level Event APIs ( |
|
The |
|
The |
|
Returns a global system data structure, so it will not be supported in the future. |
|
|
|
OSEventAvail is not supported in Carbon. Use the EventAvail function instead. |
|
The |
|
FKEYs are not supported in Carbon because they involve loading code from resources, which isn't supported under Carbon, and because very few applications use them. |
|
|
|
The High Level Event APIs ( |
|
FKEYs are not supported in Carbon because they involve loading code from resources, which isn't supported under Carbon, and because very few applications use them. |
|
|
|
The High Level Event APIs ( |
|
The High Level Event APIs ( |
|
Posting events in the Operating System event queue is not supported in Carbon. |
|
Desk accessories are not supported in Carbon. |
|
Desk accessories are not supported in Carbon. |
|
In Carbon, the Event Manager automatically handles all task scheduling. |
© 2003, 2007 Apple Inc. All Rights Reserved. (Last updated: 2007-10-31)