Currently we support a single text viewport, and corresponding text cursor.
It might be nice to add support for multiple text viewports. Each viewport would probably need to keep track of its own text cursor.
To support this we'd want at least a "select text viewport" call to swap to a different viewport. (We may not need a "create viewport" - picking one that doesn't exist would just be a default full-screen text viewport.) Once a viewport is selected, all text output would go to the cursor in that viewport. No management of overlaps need exist - we'd rely on user to define their viewports accordingly.
Acorn systems don't support this - but RISC OS of course had a windowing system which kinda removes the need. :grin:
Currently we support a single text viewport, and corresponding text cursor.
It might be nice to add support for multiple text viewports. Each viewport would probably need to keep track of its own text cursor.
To support this we'd want at least a "select text viewport" call to swap to a different viewport. (We may not need a "create viewport" - picking one that doesn't exist would just be a default full-screen text viewport.) Once a viewport is selected, all text output would go to the cursor in that viewport. No management of overlaps need exist - we'd rely on user to define their viewports accordingly.
Acorn systems don't support this - but RISC OS of course had a windowing system which kinda removes the need. :grin: