On 26 Sep 2003 at 0:04, P Witte wrote: (...) > Are you thinking of buffering output sent to each scr/con channel, or are > you thinking of using OCR, as in Qlip, or something else?
and On 25 Sep 2003 at 17:25, [EMAIL PROTECTED] wrote: (...) > The prblem comes when you want to highlight an area of text to copy :-) > Whoa there! This is all much too complicated. This little trick only does the following: put into the stuffer buffer (all of) the characters that have been entered in a read/edit line trap so far. No OCR, no QLip, no highlighting, no fancy stuff. This is all not needed because the trap "knows" what characters there are. Per : > I think it is a good idea. Great that you are prepared to do it! Might it be > an idea to add some kind of test for this functionality (eg set a bit on > some sysvar), as application programmers may wish to eg provide a limited > functionality on systems that dont support it. Do you mean that the application programmer will build this facility into his program (via some special keystroke or menu item?) so that , for example, in QDOS this can also be achieved? Well, then it would simply be possible to achive it with 2 different methods on an SMSQ/E system. (remember, as Marcel rightly points out, the keystroke is trapped anyway, the application doesn't even get it) > > CTRL-C is, of course, out of the question, as that is used elsewhere. > > Couldnt this also be an Smsq/e configurable item (Im aware that it is easy > enough to do as a POKE, but..) together with the Hotstuff keys, F10, and > anything else that may crop up? > > Per Yes, it could be. Personally, I'm not so sure that it is really such a good idea, I like the idea of systemwide unified keystrokes. Everybody knows not to use CTRL-C in one's applications because it is a fixed system wide keystroke. Same for CTRL F5 for screen freeze, or Alt Enter etc.... Some of these may be changeable via POKEs in the sysvars, but in general, they are fairly constant over all systems. For the new keystroke I'll probably foresee some kind of configuration item, since I realistically can't really know that it will work in all circumstances at all times.... Rich: > Hmm - I had forgotten this !! Mind you, as it is only copy into the current > buffer, perhaps the solution would be for the operating system to show up a > pop-up window (under WMAN) to select : > > 1. Copy current line into buffer > 2. Refresh screen > Again, this is much too complicated. Especially under programs that don't use the Pointer Environmant, you'll get all kinds of problems popping up a WMAN window in a non managed job. Talking about the specific problem (F10 = shift F5, used as screen refresh in some programs): These programs do not use the read/edit line trap. They would not benefit from my little extension anyway, and would have no problem with the use of this key. Wolfgang
