Programmer Guide/General Descriptions/SHELL messages - Revision history

Jw at 07:41, 15 March 2018

2018-03-15T07:41:00Z

← Older revision		Revision as of 09:41, 15 March 2018
Line 21:		Line 21:
	Note: the message is really generated by the Log window and placed in the message-queue of the master-shell. The master-shell translates and forwards the message to the shell running the application addressed in the DDE message.		Note: the message is really generated by the Log window and placed in the message-queue of the master-shell. The master-shell translates and forwards the message to the shell running the application addressed in the DDE message.

	===Debugger===		==Debugger==
	SHELL <var>shellid</var> DEBUG		SHELL <var>shellid</var> DEBUG

	Sent to the shell if the Debugger is started with the key combination Ctrl+D Ctrl+D.		Sent to the shell if the Debugger is started with the key combination Ctrl+D Ctrl+D.

	===Log Window===		==Log Window==

	The messages sent by the Log window to the master shell are a special kind of shell-to-shell communication. All Log window messages are processed by the master shell. The id of the master shell is stored in the global variable <code>@MASTER</code>. The master shell is implemented in the standard macro library.		The messages sent by the Log window to the master shell are a special kind of shell-to-shell communication. All Log window messages are processed by the master shell. The id of the master shell is stored in the global variable <code>@MASTER</code>. The master shell is implemented in the standard macro library.

Jw at 07:40, 15 March 2018

2018-03-15T07:40:45Z

← Older revision		Revision as of 09:40, 15 March 2018
Line 11:		Line 11:
	(via <code>GETMESSAGE</code>)		(via <code>GETMESSAGE</code>)

	For the shell-to-shell communication the message SHELL-RUN is used. It is generated by either the Log window (e.g. for DDE commands) or the command <code>MESSAGE RUN shellid command</code>. The format of SHELL-RUN depends on the message receive method. The macro <code>~~GetMessage~~</code> removes the keyword <code>RUN</code> from the message. Therefore a message handler macro receives the first word of command as <var>msgid</var> instead of <code>RUN</code>. For communication messages between shells, the macros <code>PostMessage</code> (for sending) and <code>GETMESSAGE</code> (for receiving) should be used. The <code>SHELL</code> messages are normally generated and processed in macros and used to implement a special data-exchange or communication mechanism between applications. Some of these messages are preprocessed by or handled directly in the macro <code>GETMESSAGE</code>.		For the shell-to-shell communication the message SHELL-RUN is used. It is generated by either the Log window (e.g. for DDE commands) or the command <code>MESSAGE RUN shellid command</code>. The format of SHELL-RUN depends on the message receive method. The macro <code>GETMESSAGE</code> removes the keyword <code>RUN</code> from the message. Therefore a message handler macro receives the first word of command as <var>msgid</var> instead of <code>RUN</code>. For communication messages between shells, the macros <code>PostMessage</code> (for sending) and <code>GETMESSAGE</code> (for receiving) should be used. The <code>SHELL</code> messages are normally generated and processed in macros and used to implement a special data-exchange or communication mechanism between applications. Some of these messages are preprocessed by or handled directly in the macro <code>GETMESSAGE</code>.

	==DDE==		==DDE==

Jw at 07:32, 15 March 2018

2018-03-15T07:32:12Z

← Older revision		Revision as of 09:32, 15 March 2018
Line 3:		Line 3:
	{{Shell}}		{{Shell}}
	==Run==		==Run==
	~~<code>~~SHELL <var>sendershellid</var> RUN <var>msgid msgparameters</var~~></code~~>		SHELL <var>sendershellid</var> RUN <var>msgid msgparameters</var>

	(via <code>MESSAGE LOOP</code>)		(via <code>MESSAGE LOOP</code>)

	~~<code>~~SHELL <var>sendershellid msgid msgparameters</var~~></code~~>		SHELL <var>sendershellid msgid msgparameters</var>

	(via <code>GETMESSAGE</code>)		(via <code>GETMESSAGE</code>)
Line 15:		Line 15:
	==DDE==		==DDE==

	~~<code>~~SHELL <var>shellid</var> DDE <var>ddecommandstring</var~~></code~~>		SHELL <var>shellid</var> DDE <var>ddecommandstring</var>

	This message is generated when {{STX}} receives a DDE-execute command from the operating system.		This message is generated when {{STX}} receives a DDE-execute command from the operating system.

	Note: the message is really generated by the Log window and placed in the message-queue of the master-shell. The master-shell translates and forwards the message to the shell running the application addressed in the DDE message.~~'''Debugger'''~~		Note: the message is really generated by the Log window and placed in the message-queue of the master-shell. The master-shell translates and forwards the message to the shell running the application addressed in the DDE message.

	~~<code>~~SHELL <var>shellid</var> DEBUG~~</code>~~		===Debugger===
			SHELL <var>shellid</var> DEBUG

	Sent to the shell if the Debugger is started with the key combination Ctrl+D Ctrl+D.~~'''~~Log Window~~'''~~		Sent to the shell if the Debugger is started with the key combination Ctrl+D Ctrl+D.

			===Log Window===

	The messages sent by the Log window to the master shell are a special kind of shell-to-shell communication. All Log window messages are processed by the master shell. The id of the master shell is stored in the global variable <code>@MASTER</code>. The master shell is implemented in the standard macro library.		The messages sent by the Log window to the master shell are a special kind of shell-to-shell communication. All Log window messages are processed by the master shell. The id of the master shell is stored in the global variable <code>@MASTER</code>. The master shell is implemented in the standard macro library.

	~~<code>~~MAIN MAIN MINIMIZE\|MAXIMIZE\|RESTORE\|CLOSE <var>par</var~~></code~~>		MAIN MAIN MINIMIZE\|MAXIMIZE\|RESTORE\|CLOSE <var>par</var>

	This message is sent to the master shell when an item in the Log window's system menu is selected. The parameter <var>par</var> can be ignored.		This message is sent to the master shell when an item in the Log window's system menu is selected. The parameter <var>par</var> can be ignored.

	~~<code>~~MAIN MAIN POPUP <var>menuitem</var~~></code~~>		MAIN MAIN POPUP <var>menuitem</var>

	This message is sent to the master shell when a popup menu item is selected by the user. The parameter <var>menuitem</var> is computed in the same way as for displays and dialogs (100.menuindex + itemindex).		This message is sent to the master shell when a popup menu item is selected by the user. The parameter <var>menuitem</var> is computed in the same way as for displays and dialogs (100.menuindex + itemindex).

Jw at 07:24, 15 March 2018

2018-03-15T07:24:32Z

← Older revision		Revision as of 09:24, 15 March 2018
Line 1:		Line 1:
	{{DISPLAYTITLE:{{SUBPAGENAME}}}}		{{DISPLAYTITLE:{{SUBPAGENAME}}}}
	{{PG_GeneralDescriptions}}		{{PG_GeneralDescriptions}}
			{{Shell}}
	==Run==		==Run==
	<code>SHELL <var>sendershellid</var> RUN <var>msgid msgparameters</var></code>		<code>SHELL <var>sendershellid</var> RUN <var>msgid msgparameters</var></code>

Jw at 09:29, 29 February 2016

2016-02-29T09:29:08Z

← Older revision		Revision as of 11:29, 29 February 2016
Line 1:		Line 1:
	{{DISPLAYTITLE:{{SUBPAGENAME}}}}		{{DISPLAYTITLE:{{SUBPAGENAME}}}}
	{{PG_GeneralDescriptions}}		{{PG_GeneralDescriptions}}
	~~'''~~Run~~'''~~		==Run==

	<code>SHELL <var>sendershellid</var> RUN <var>msgid msgparameters</var></code>		<code>SHELL <var>sendershellid</var> RUN <var>msgid msgparameters</var></code>

Line 13:		Line 12:
	For the shell-to-shell communication the message SHELL-RUN is used. It is generated by either the Log window (e.g. for DDE commands) or the command <code>MESSAGE RUN shellid command</code>. The format of SHELL-RUN depends on the message receive method. The macro <code>GetMessage</code> removes the keyword <code>RUN</code> from the message. Therefore a message handler macro receives the first word of command as <var>msgid</var> instead of <code>RUN</code>. For communication messages between shells, the macros <code>PostMessage</code> (for sending) and <code>GETMESSAGE</code> (for receiving) should be used. The <code>SHELL</code> messages are normally generated and processed in macros and used to implement a special data-exchange or communication mechanism between applications. Some of these messages are preprocessed by or handled directly in the macro <code>GETMESSAGE</code>.		For the shell-to-shell communication the message SHELL-RUN is used. It is generated by either the Log window (e.g. for DDE commands) or the command <code>MESSAGE RUN shellid command</code>. The format of SHELL-RUN depends on the message receive method. The macro <code>GetMessage</code> removes the keyword <code>RUN</code> from the message. Therefore a message handler macro receives the first word of command as <var>msgid</var> instead of <code>RUN</code>. For communication messages between shells, the macros <code>PostMessage</code> (for sending) and <code>GETMESSAGE</code> (for receiving) should be used. The <code>SHELL</code> messages are normally generated and processed in macros and used to implement a special data-exchange or communication mechanism between applications. Some of these messages are preprocessed by or handled directly in the macro <code>GETMESSAGE</code>.

	~~'''~~DDE~~'''~~		==DDE==

	<code>SHELL <var>shellid</var> DDE <var>ddecommandstring</var></code>		<code>SHELL <var>shellid</var> DDE <var>ddecommandstring</var></code>

Jw at 09:28, 29 February 2016

2016-02-29T09:28:09Z

← Older revision		Revision as of 11:28, 29 February 2016
Line 1:		Line 1:
	{{DISPLAYTITLE:{{SUBPAGENAME}}}}		{{DISPLAYTITLE:{{SUBPAGENAME}}}}
	{{PG_GeneralDescriptions}}		{{PG_GeneralDescriptions}}

	'''Run'''		'''Run'''

Jw: /* SHELL messages */

2016-02-29T09:25:48Z

SHELL messages

← Older revision		Revision as of 11:25, 29 February 2016
Line 1:		Line 1:
	{{DISPLAYTITLE:{{SUBPAGENAME}}}}		{{DISPLAYTITLE:{{SUBPAGENAME}}}}
	~~====SHELL messages====~~		{{PG_GeneralDescriptions}}

	'''Run'''		'''Run'''

Christian: Text replace - "S_TOOLS-STx" to "{{STX}}"

2011-04-05T15:56:59Z

Text replace - "S_TOOLS-STx" to "{{STX}}"

← Older revision		Revision as of 17:56, 5 April 2011
Line 18:		Line 18:
	<code>SHELL <var>shellid</var> DDE <var>ddecommandstring</var></code>		<code>SHELL <var>shellid</var> DDE <var>ddecommandstring</var></code>

	This message is generated when ~~S_TOOLS-STx~~ receives a DDE-execute command from the operating system.		This message is generated when {{STX}} receives a DDE-execute command from the operating system.

	Note: the message is really generated by the Log window and placed in the message-queue of the master-shell. The master-shell translates and forwards the message to the shell running the application addressed in the DDE message.'''Debugger'''		Note: the message is really generated by the Log window and placed in the message-queue of the master-shell. The master-shell translates and forwards the message to the shell running the application addressed in the DDE message.'''Debugger'''

Admin: 1 revision: Initial import

2010-11-18T16:31:45Z

1 revision: Initial import

← Older revision	Revision as of 18:31, 18 November 2010
(No difference)

193.171.195.8: initial import

2010-05-17T13:05:27Z

initial import

New page

{{DISPLAYTITLE:{{SUBPAGENAME}}}}
====SHELL messages====

'''Run'''

<code>SHELL <var>sendershellid</var> RUN <var>msgid msgparameters</var></code>

(via <code>MESSAGE LOOP</code>)

<code>SHELL <var>sendershellid msgid msgparameters</var></code>

(via <code>GETMESSAGE</code>)

For the shell-to-shell communication the message SHELL-RUN is used. It is generated by either the Log window (e.g. for DDE commands) or the command <code>MESSAGE RUN shellid command</code>. The format of SHELL-RUN depends on the message receive method. The macro <code>GetMessage</code> removes the keyword <code>RUN</code> from the message. Therefore a message handler macro receives the first word of command as <var>msgid</var> instead of <code>RUN</code>. For communication messages between shells, the macros <code>PostMessage</code> (for sending) and <code>GETMESSAGE</code> (for receiving) should be used. The <code>SHELL</code> messages are normally generated and processed in macros and used to implement a special data-exchange or communication mechanism between applications. Some of these messages are preprocessed by or handled directly in the macro <code>GETMESSAGE</code>.

'''DDE'''

<code>SHELL <var>shellid</var> DDE <var>ddecommandstring</var></code>

This message is generated when S_TOOLS-STx receives a DDE-execute command from the operating system.

Note: the message is really generated by the Log window and placed in the message-queue of the master-shell. The master-shell translates and forwards the message to the shell running the application addressed in the DDE message.'''Debugger'''

<code>SHELL <var>shellid</var> DEBUG</code>

Sent to the shell if the Debugger is started with the key combination Ctrl+D Ctrl+D.'''Log Window'''

The messages sent by the Log window to the master shell are a special kind of shell-to-shell communication. All Log window messages are processed by the master shell. The id of the master shell is stored in the global variable <code>@MASTER</code>. The master shell is implemented in the standard macro library.

<code>MAIN MAIN MINIMIZE|MAXIMIZE|RESTORE|CLOSE <var>par</var></code>

This message is sent to the master shell when an item in the Log window's system menu is selected. The parameter <var>par</var> can be ignored.

<code>MAIN MAIN POPUP <var>menuitem</var></code>

This message is sent to the master shell when a popup menu item is selected by the user. The parameter <var>menuitem</var> is computed in the same way as for displays and dialogs (100.menuindex + itemindex).