BifiMSX wrote:
> Using Catapult pasting from the native OS to openMSX is available for
> years already, although only to machines with an international keyboard
> layout.
...or via the "type" command in the console.
I guess this FRQ is still open due to the "vice versa". That's a rather
tricky issue though:
* you'd probably need to differentiate between graphics and text modes.
In graphics mode you'd want to copy a rectangle of pixels, in text
mode, a selection of text. But that's not so simple either:
- What about screen 1?
That mode is used for text as well as for graphics!
- What about e.g jANSI?
That's a multi-colored text mode emulated in screen 7!
* Implementing the selection mechanism poses the very practical
problem, that the mouse might be 'captured' by the MSX. This could
be overcome by having the user press an extra keyboard button to
copy/paste, but that's highly non-standard.
Next to these issues, I wonder what practical purposes copy/paste
from openMSX to the OS might have. I think most use cases can be
covered by already implemented features:
* Need graphics? -> Use screenshot
* Need text? -> Direct MSX-output to the MSX-printer and log
the printer file.
Just my 2cts on an early sunday morning ;-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Paste-to options are nowadays:
- the Type feature in Catapult (which works with any keyboard layout nowadays)
- the type_from_file console command to type the contents of a file (also works for any keyboard layout)
Both use the type console command internally.
Copy-from options:
- the get_screen command on the console. Put to file e.g. via save_to_file test.txt [get_screen] (for text modes only)
- indeed via the printer (e.g. llist for a basic program in RAM)
- via the listing command if it's about a basic program in RAM
Last edit: Manuel Bilderbeek 2015-01-15
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=130840
Originator: NO
I vote for that. It would allow to easily paste MSX-Basic programs from the net directly on the MSX.
Same on the other side: I could copy texts from the output of any MSX-DOS program to the host OS.
Logged In: YES
user_id=790845
Originator: NO
Using Catapult pasting from the native OS to openMSX is available for years already, although only to machines with an international keyboard layout.
Logged In: YES
user_id=951315
Originator: NO
BifiMSX wrote:
> Using Catapult pasting from the native OS to openMSX is available for
> years already, although only to machines with an international keyboard
> layout.
...or via the "type" command in the console.
I guess this FRQ is still open due to the "vice versa". That's a rather
tricky issue though:
* you'd probably need to differentiate between graphics and text modes.
In graphics mode you'd want to copy a rectangle of pixels, in text
mode, a selection of text. But that's not so simple either:
- What about screen 1?
That mode is used for text as well as for graphics!
- What about e.g jANSI?
That's a multi-colored text mode emulated in screen 7!
* Implementing the selection mechanism poses the very practical
problem, that the mouse might be 'captured' by the MSX. This could
be overcome by having the user press an extra keyboard button to
copy/paste, but that's highly non-standard.
Next to these issues, I wonder what practical purposes copy/paste
from openMSX to the OS might have. I think most use cases can be
covered by already implemented features:
* Need graphics? -> Use screenshot
* Need text? -> Direct MSX-output to the MSX-printer and log
the printer file.
Just my 2cts on an early sunday morning ;-)
Paste-to options are nowadays:
- the Type feature in Catapult (which works with any keyboard layout nowadays)
- the type_from_file console command to type the contents of a file (also works for any keyboard layout)
Both use the type console command internally.
Copy-from options:
- the get_screen command on the console. Put to file e.g. via save_to_file test.txt [get_screen] (for text modes only)
- indeed via the printer (e.g. llist for a basic program in RAM)
- via the listing command if it's about a basic program in RAM
Last edit: Manuel Bilderbeek 2015-01-15