Intuition Input and Output Methods - Revision history

Costel Mincea: Text replacement - "" to ""

2025-01-26T19:26:50Z

Text replacement - "<syntaxhighlight>" to "<syntaxhighlight lang="C" line>"

← Older revision		Revision as of 19:26, 26 January 2025
Line 128:		Line 128:
	This example shows how to receive Intuition events. It reports on a variety of events: close window, keyboard, disk insertion and removal, select button up and down and menu button up and down. Note that the menu button events will only be received by the program if the WA_RMBTrap attribute is set for the window.		This example shows how to receive Intuition events. It reports on a variety of events: close window, keyboard, disk insertion and removal, select button up and down and menu button up and down. Note that the menu button events will only be received by the program if the WA_RMBTrap attribute is set for the window.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	/*		/*
	** eventloop.c - standard technique to handle IntuiMessages from an IDCMP.		** eventloop.c - standard technique to handle IntuiMessages from an IDCMP.
Line 341:		Line 341:
	As promised in the last section, this example shows the CloseWindowSafely() function. Use this function to close any windows that share an IDCMP port with another window.		As promised in the last section, this example shows the CloseWindowSafely() function. Use this function to close any windows that share an IDCMP port with another window.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	/* CloseWindowSafely		/* CloseWindowSafely
	**		**
Line 389:		Line 389:
	The IntuiMessage structure is an Exec Message that has been extended to include Intuition specific information. The ExecMessage field in the IntuiMessage is an actual instance of a Message structure and is used by Exec to manage the transmission of the message. The Intuition extensions of the IntuiMessage are used to transmit specialized Intuition data to the program.		The IntuiMessage structure is an Exec Message that has been extended to include Intuition specific information. The ExecMessage field in the IntuiMessage is an actual instance of a Message structure and is used by Exec to manage the transmission of the message. The Intuition extensions of the IntuiMessage are used to transmit specialized Intuition data to the program.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct IntuiMessage		struct IntuiMessage
	{		{

Steven Solie: /* IntuiMessages */

2015-11-03T23:01:06Z

IntuiMessages

← Older revision		Revision as of 23:01, 3 November 2015
Line 407:		Line 407:

	; ExecMessage		; ExecMessage
	: This field is maintained by Exec. It is used for linking the message into the system and broadcasting it to a message port. See ~~the chapter "~~Exec Messages and Ports" for more information on the Message structure and its use.		: This field is maintained by Exec. It is used for linking the message into the system and broadcasting it to a message port. See [[Exec_Messages_and_Ports\|Exec Messages and Ports]] for more information on the Message structure and its use.

	; Class		; Class

Steven Solie: /* Intuition Output */

2015-11-03T23:00:12Z

Intuition Output

← Older revision		Revision as of 23:00, 3 November 2015
Line 65:		Line 65:
	* Imagery may be sent to the graphics library primitives. Graphics library includes functions for line drawing, area fill, specialized animation and output of text. See [[Graphics_Primitives\|Graphics Primitives]], [[Graphics_Library_and_Text\|Graphics Library and Text]] and [[Graphics_Sprites,_Bobs_and_Animation\|Graphics Sprites, Bobs and Animation]] for more information on these functions.		* Imagery may be sent to the graphics library primitives. Graphics library includes functions for line drawing, area fill, specialized animation and output of text. See [[Graphics_Primitives\|Graphics Primitives]], [[Graphics_Library_and_Text\|Graphics Library and Text]] and [[Graphics_Sprites,_Bobs_and_Animation\|Graphics Sprites, Bobs and Animation]] for more information on these functions.

	* Use the Intuition library support functions for rendering text, graphical imagery, and line drawing. These provide some of the same functions as the graphics library routines, but the Intuition functions perform more of the detail work for you. See [[Intuition_Images,_Line_Drawing_and_Text\|Intuition Images, Line Drawing and Text]] for more information on Intuition rendering functions. Also see, of course, the ~~chapters~~ on screens, windows, gadgets menus and requesters for information on managing the display.		* Use the Intuition library support functions for rendering text, graphical imagery, and line drawing. These provide some of the same functions as the graphics library routines, but the Intuition functions perform more of the detail work for you. See [[Intuition_Images,_Line_Drawing_and_Text\|Intuition Images, Line Drawing and Text]] for more information on Intuition rendering functions. Also see, of course, the articles on screens, windows, gadgets menus and requesters for information on managing the display.

	* Output character-based data via the console device. The console device is discussed in the next section.		* Output character-based data via the console device. The console device is discussed in the next section.

Steven Solie: /* Intuition Output */

2015-11-03T22:59:52Z

Intuition Output

← Older revision		Revision as of 22:59, 3 November 2015
Line 65:		Line 65:
	* Imagery may be sent to the graphics library primitives. Graphics library includes functions for line drawing, area fill, specialized animation and output of text. See [[Graphics_Primitives\|Graphics Primitives]], [[Graphics_Library_and_Text\|Graphics Library and Text]] and [[Graphics_Sprites,_Bobs_and_Animation\|Graphics Sprites, Bobs and Animation]] for more information on these functions.		* Imagery may be sent to the graphics library primitives. Graphics library includes functions for line drawing, area fill, specialized animation and output of text. See [[Graphics_Primitives\|Graphics Primitives]], [[Graphics_Library_and_Text\|Graphics Library and Text]] and [[Graphics_Sprites,_Bobs_and_Animation\|Graphics Sprites, Bobs and Animation]] for more information on these functions.

	* Use the Intuition library support functions for rendering text, graphical imagery, and line drawing. These provide some of the same functions as the graphics library routines, but the Intuition functions perform more of the detail work for you. See ~~the chapter "~~Intuition Images, Line Drawing and Text" for more information on Intuition rendering functions. Also see, of course, the chapters on screens, windows, gadgets menus and requesters for information on managing the display.		* Use the Intuition library support functions for rendering text, graphical imagery, and line drawing. These provide some of the same functions as the graphics library routines, but the Intuition functions perform more of the detail work for you. See [[Intuition_Images,_Line_Drawing_and_Text\|Intuition Images, Line Drawing and Text]] for more information on Intuition rendering functions. Also see, of course, the chapters on screens, windows, gadgets menus and requesters for information on managing the display.

	* Output character-based data via the console device. The console device is discussed in the next section.		* Output character-based data via the console device. The console device is discussed in the next section.

Steven Solie: /* IDCMP Events and the Input Focus */

2015-11-03T22:58:56Z

IDCMP Events and the Input Focus

← Older revision		Revision as of 22:58, 3 November 2015
Line 50:		Line 50:

	=== IDCMP Events and the Input Focus ===		=== IDCMP Events and the Input Focus ===



	Although at any given time many applications may be waiting for input, in most cases only the active application (the one with the currently active window) will receive IDCMP messages.		Although at any given time many applications may be waiting for input, in most cases only the active application (the one with the currently active window) will receive IDCMP messages.
Line 57:		Line 55:
	Since the IDCMP messages are, in general, directed to a single window, this window is said to have the ''input focus''; the input from a variety of sources is focused on this single location.		Since the IDCMP messages are, in general, directed to a single window, this window is said to have the ''input focus''; the input from a variety of sources is focused on this single location.

	The active window is generally selected by the user, although it is possible for applications to change the active window. See ~~the "~~Intuition Windows~~" chapter~~ for information on selecting or setting the active window. Be aware that changing the active window will change the input focus. Usually this change is performed following user action; the user selects a window with the mouse, or activates a new application. Changes to the input focus without user control, such as activating another window while the user is working in an application, may confuse the user. Perform such changes with great care.		The active window is generally selected by the user, although it is possible for applications to change the active window. See [[Intuition_Windows\|Intuition Windows]] for information on selecting or setting the active window. Be aware that changing the active window will change the input focus. Usually this change is performed following user action; the user selects a window with the mouse, or activates a new application. Changes to the input focus without user control, such as activating another window while the user is working in an application, may confuse the user. Perform such changes with great care.

	Not all events are sent only to the active IDCMP. Some events, such as "disk inserted," may be useful to many programs, so Intuition translates these events into separate messages, one for each application.		Not all events are sent only to the active IDCMP. Some events, such as "disk inserted," may be useful to many programs, so Intuition translates these events into separate messages, one for each application.

Steven Solie: /* Receiving Input Events from Intuition */

2015-11-03T22:58:12Z

Receiving Input Events from Intuition

← Older revision		Revision as of 22:58, 3 November 2015
Line 45:		Line 45:
	There are many classes of IntuiMessages, and the application can control which classes of events are routed to its window's port by setting the appropriate IDCMP flags. When Intuition has an event to send, but the window does not have the corresponding IDCMP flag set, the event is generally passed along to the next input handler in the chain. One input handler that resides below Intuition's is the console device's handler. If your application's window has a console attached to it, the console device will generally convert events it receives into console code sequences, and send those to your console. In this manner, you can hear these events.		There are many classes of IntuiMessages, and the application can control which classes of events are routed to its window's port by setting the appropriate IDCMP flags. When Intuition has an event to send, but the window does not have the corresponding IDCMP flag set, the event is generally passed along to the next input handler in the chain. One input handler that resides below Intuition's is the console device's handler. If your application's window has a console attached to it, the console device will generally convert events it receives into console code sequences, and send those to your console. In this manner, you can hear these events.

	Because IntuiMessages and the IDCMP are the primary way in which applications receive communication from Intuition, discussions elsewhere in the manual frequently refer to events from Intuition as messages, IntuiMessages, or IDCMP messages. However, most of the information sent as IntuiMessages is also available through the console device, though that option is used less often. Elsewhere in this ~~chapter~~, you can learn how getting your events through the console differs from getting them through your IDCMP.		Because IntuiMessages and the IDCMP are the primary way in which applications receive communication from Intuition, discussions elsewhere in the manual frequently refer to events from Intuition as messages, IntuiMessages, or IDCMP messages. However, most of the information sent as IntuiMessages is also available through the console device, though that option is used less often. Elsewhere in this article, you can learn how getting your events through the console differs from getting them through your IDCMP.

	Whichever way an application chooses to get its messages, it is frequently designed to be event-driven. That is to say, after some amount of initialization, the application will go into a state where it is waiting for some event to happen. This event could be an input event, or some other kind of event. Based on the event received, the application would take appropriate action, and return to its waiting state.		Whichever way an application chooses to get its messages, it is frequently designed to be event-driven. That is to say, after some amount of initialization, the application will go into a state where it is waiting for some event to happen. This event could be an input event, or some other kind of event. Based on the event received, the application would take appropriate action, and return to its waiting state.

Steven Solie: /* Intuition Input and Output Methods */

2015-11-03T22:57:42Z

Intuition Input and Output Methods

← Older revision		Revision as of 22:57, 3 November 2015
Line 1:		Line 1:
	== Intuition Input and Output Methods ==		== Intuition Input and Output Methods ==

	This ~~chapter~~ discusses the input and output (I/O) techniques used with Intuition. I/O facilities are also available through Exec's device subsystems, such as the console, serial and parallel devices. For more information on these, see [[Devices\|Devices]].		This article discusses the input and output (I/O) techniques used with Intuition. I/O facilities are also available through Exec's device subsystems, such as the console, serial and parallel devices. For more information on these, see [[Devices\|Devices]].

	For graphical output to the Amiga's display, programs can use Intuition's drawing features or handle rendering directly through calls to the graphics library. See the ~~three~~ graphics library ~~chapters in this manual~~ for more information on display rendering. For more about Intuition's drawing features see [[Intuition_Images,_Line_Drawing_and_Text\|Intuition Images, Line Drawing and Text]].		For graphical output to the Amiga's display, programs can use Intuition's drawing features or handle rendering directly through calls to the graphics library. See the graphics library articles for more information on display rendering. For more about Intuition's drawing features see [[Intuition_Images,_Line_Drawing_and_Text\|Intuition Images, Line Drawing and Text]].

	== Overview of System I/O ==		== Overview of System I/O ==

Steven Solie: /* Other Event Message Classes and Flags */

2015-10-29T18:47:14Z

Other Event Message Classes and Flags

← Older revision		Revision as of 18:47, 29 October 2015
Line 594:		Line 594:

	; IDCMP_DISKINSERTED and IDCMP_DISKREMOVED		; IDCMP_DISKINSERTED and IDCMP_DISKREMOVED
	: When the user inserts or removes a ~~floppy~~ disk from any drive, Intuition will send one of these message types.		: When the user inserts or removes a disk from any drive, Intuition will send one of these message types.

	: This message type is broadcast to all IDCMP that have this flag set, not just to the active window. If the application has this flag set, it should be prepared to handle the event even if it is not active.		: This message type is broadcast to all IDCMP that have this flag set, not just to the active window. If the application has this flag set, it should be prepared to handle the event even if it is not active.

Steven Solie: /* Other Event Message Classes and Flags */

2015-10-02T18:34:23Z

Other Event Message Classes and Flags

← Older revision		Revision as of 18:34, 2 October 2015
Line 589:		Line 589:
	: After receiving a message of class IDCMP_NEWPREFS, the application should call GetPrefs() to obtain a copy of the new Preferences.		: After receiving a message of class IDCMP_NEWPREFS, the application should call GetPrefs() to obtain a copy of the new Preferences.

	: Under the new Preferences scheme used in Release 2 and later versions of the OS, an IDCMP_NEWPREFS message will not always be sent when the user changes a Preferences setting. Only Preferences values available under V34, i.e., those that can be modified by a call to SetPrefs(), will cause an IDCMP_NEWPREFS message to be sent. New Preferences items such as overscan or font settings rely on ~~filesystem~~ notification for monitoring changes. See [[Preferences]] for more information.		: Under the new Preferences scheme used in Release 2 and later versions of the OS, an IDCMP_NEWPREFS message will not always be sent when the user changes a Preferences setting. Only Preferences values available under V34, i.e., those that can be modified by a call to SetPrefs(), will cause an IDCMP_NEWPREFS message to be sent. New Preferences items such as overscan or font settings rely on file system notification for monitoring changes. See [[Preferences]] for more information.

	: This message type is broadcast to all IDCMP that have this flag set, not just to the active window. If the application has this flag set, it should be prepared to handle the event even if it is not active.		: This message type is broadcast to all IDCMP that have this flag set, not just to the active window. If the application has this flag set, it should be prepared to handle the event even if it is not active.

Steven Solie: /* Other Event Message Classes and Flags */

2014-08-29T16:55:29Z

Other Event Message Classes and Flags

← Older revision		Revision as of 16:55, 29 August 2014
Line 606:		Line 606:

	; IDCMP_IDCMPUPDATE		; IDCMP_IDCMPUPDATE
	: Used for notification from BOOPSI custom gadgets. See the ~~chapter~~ ~~on "BOOPSI"~~ for more information. The IAddress field contains a pointer to a tag item list. Tag lists are described in [[Utility_Library\|Utility Library]].		: Used for notification from BOOPSI custom gadgets. See the [[BOOPSI_-_Object_Oriented_Intuition\|BOOPSI section]] for more information. The IAddress field contains a pointer to a tag item list. Tag lists are described in [[Utility_Library\|Utility Library]].

	; IDCMP_CHANGEWINDOW		; IDCMP_CHANGEWINDOW