DosSMNotifyDD2: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Legacy | |||
|RepFunc= | |||
|Remarks=This page list the older version of the function for reference. | |||
}} | |||
This will issue an ioctl to the registered DDs for an incoming screen event. The IOCTL that will be called is category 0x0b, function 0x41. In contrast to DOSSMNOTIFYDD, this is called directly (basically it will be called by the HARDERR.EXE daemon). | This will issue an ioctl to the registered DDs for an incoming screen event. The IOCTL that will be called is category 0x0b, function 0x41. In contrast to DOSSMNOTIFYDD, this is called directly (basically it will be called by the HARDERR.EXE daemon). | ||
Revision as of 03:54, 16 September 2017
 Legacy Function Warning
| |
|---|---|
| It is recommended to use a newer replacement for this function. | |
| Replacement: | |
| Remarks: | This page list the older version of the function for reference. |
This will issue an ioctl to the registered DDs for an incoming screen event. The IOCTL that will be called is category 0x0b, function 0x41. In contrast to DOSSMNOTIFYDD, this is called directly (basically it will be called by the HARDERR.EXE daemon).
Syntax
DOSSMNOTIFYDD2(short type,short newsgroup,short currsgroup)
Parameters
- type
- type of event. corresponds to the bitmap of DOSSMREGISTERDD.
- newsgroup
- screen group to be active next (after save)
- currsgroup
- current screen group
Return Code
APIRET16 Pascal far