Pasting code into Matrix Brandy
Is it possible to paste code from the clipboard directly into Matrix Brandy's immediate mode? I tried typing Ctrl+V, but that seems to have no effect, nor is there an Edit.. Paste menu option like there is in BeebEm. I also tried right-clicking (often that produces a Edit Context Menu in Windows) but nothing.
0
Comments
-
In Linux you can paste into the controlling terminal (the one you ran Brandy from). Last time I tried this in Windows, it didn't work. Brandy itself has no interaction with the clipboard. Right-clicking will just send a right-click event via SDL into the MOUSE X,Y,B[,C] command.
But it's a thought on future functionality, I would probably implement it like a *CBEXEC command (like *EXEC, but sourcing from the clipboard instead of a file).0 -
In Linux you can paste into the controlling terminal (the one you ran Brandy from).But it's a thought on future functionality, I would probably implement it like a *CBEXEC command (like *EXEC, but sourcing from the clipboard instead of a file).
Whilst on that topic what 'control codes' does Matrix Brandy currently accept in immediate mode? I would have expected Ctrl+N (VDU 14, enter paged mode) to work at the very least, but on a quick test it doesn't. I tried typing LIST Ctrl+N <enter> but it doesn't pause the listing on each screen as it would on a BBC Micro (and I assume RISC OS).
0 -
Richard_Russell wrote: »But it's a thought on future functionality, I would probably implement it like a *CBEXEC command (like *EXEC, but sourcing from the clipboard instead of a file).Whilst on that topic what 'control codes' does Matrix Brandy currently accept in immediate mode? I would have expected Ctrl+N (VDU 14, enter paged mode) to work at the very least, but on a quick test it doesn't. I tried typing LIST Ctrl+N <enter> but it doesn't pause the listing on each screen as it would on a BBC Micro (and I assume RISC OS).
(Reason for deprecation: I shouldn't really trample on other OSBYTE numbers, even if they're implemented by an application ROM - 163 is for application support and nothing is allocated for X<128.)0 -
That would break any program looking for CTRL-V by checking if GET=22.
So if Ctrl+U has acted as a line-editing code 'forever' without impacting on GET, I can't see any reason why Ctrl+V shouldn't act as 'paste' without impacting on GET. There's no difference in principle, is there?
0 -
The difference I see is that CTRL-V to paste text, should GET return 22 or the first of the characters in the clipboard?
Additionally, it appears there's a catch, I woul;d need to write (or borrow an existing GPL library) to read the clipboard as SDL 1.2 has no knowledge. I did find this https://playcontrol.net/ewing/jibberjabber/SDL_ClipboardPrototype.html but that needs more investigation to see if it's suitable.0 -
The difference I see is that CTRL-V to paste text, should GET return 22 or the first of the characters in the clipboard?
It's true that the behaviour of 'paste' differs between my BASICs written in assembler code (BB4W and the 32-bit x86 editions of BBCSDL) and those written in C (the rest). But that's an accident of history.Additionally, it appears there's a catch, I woul;d need to write (or borrow an existing GPL library) to read the clipboard as SDL 1.2 has no knowledge.I did find this https://playcontrol.net/ewing/jibberjabber/SDL_ClipboardPrototype.html but that needs more investigation to see if it's suitable.
0