VioQueryConsole: Difference between revisions
m Ak120 moved page OS2 API:CPI:LEGACY:VioQueryConsole to VioQueryConsole |
No edit summary |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
This is an undocumented | [[Category:Undocumented]] | ||
This is an undocumented function of the API. | |||
According to some public discussion | According to some public discussion VioQueryConsole may return a [[HVIO]]. Since any other VIO routine will work with a hvio = 0 (with rare exceptions) this might be the reason why that function is of no value. | ||
Looks like IBM tried to implement multiple logical fullscreen video devices (like they did with keyboard and mouse) but didn't quite get to it or didn't see any use in doing so once they defined logical video buffers. | Looks like IBM tried to implement multiple logical fullscreen video devices (like they did with keyboard and mouse) but didn't quite get to it or didn't see any use in doing so once they defined logical video buffers. | ||
[[Category: | ==Syntax== | ||
VIOQUERYCONSOLE(void) | |||
[[Category:Vio]] | |||
Latest revision as of 19:08, 19 May 2025
This is an undocumented function of the API.
According to some public discussion VioQueryConsole may return a HVIO. Since any other VIO routine will work with a hvio = 0 (with rare exceptions) this might be the reason why that function is of no value.
Looks like IBM tried to implement multiple logical fullscreen video devices (like they did with keyboard and mouse) but didn't quite get to it or didn't see any use in doing so once they defined logical video buffers.
Syntax
VIOQUERYCONSOLE(void)