Re: [ql-users] Changing DISP_SIZE under SMSQ/e

2003-12-09 Thread RWAPSoftware
In a message dated 08/12/2003 22:16:46 GMT Standard Time, [EMAIL PROTECTED] writes: Coming to think about it, Rich, I think that the cursor is shut off on the non SMSQ/E versions to protect against garbled image... Surely if that crept by mistake into the QPC version (and the cursor

Re: [ql-users] Changing DISP_SIZE under SMSQ/e

2003-12-08 Thread Phoebus Dokos
[EMAIL PROTECTED] wrote: On 8 Dec 2003 at 5:49, [EMAIL PROTECTED] wrote: (...) Surely if the screen resolution is altered, any jobs which have windows which fall outside the new area should be suspended rather than removed and only reinstated once the screen size is large enough to accomodate

Re: [ql-users] Changing DISP_SIZE under SMSQ/e

2003-12-08 Thread RWAPSoftware
In a message dated 08/12/2003 15:16:37 GMT Standard Time, [EMAIL PROTECTED] writes: On 8 Dec 2003 at 5:49, [EMAIL PROTECTED] wrote:(...) Surely if the screen resolution is altered, any jobs which have windows which fall outside the new area should be suspended rather than removed and

Re: [ql-users] Changing DISP_SIZE under SMSQ/e

2003-12-08 Thread Dilwyn Jones
I have made it configurable in QWord (similar to Launchpad) as to whether it can alter the screens resolution and colour depth, but this does not help if SuperBASIC is killed off, even after the program resets the screen resolution and colour depth. I found out the hard way some of the

Re: [ql-users] Changing DISP_SIZE under SMSQ/e

2003-12-08 Thread Wolfgang Lenerz
On 8 Dec 2003 at 12:44, Phoebus Dokos wrote: I think it cannot be killed but CAN BE replaced (ie from another shell or whatever... at least I think that's what TT said at one point) (or something) ? It's a moot point here since that is not what is happening. (...) IIRC he is ie the

Re: [ql-users] Changing DISP_SIZE under SMSQ/e

2003-12-08 Thread Wolfgang Lenerz
On 8 Dec 2003 at 16:36, [EMAIL PROTECTED] wrote: Umpf, and how do you test for that? What happens if the user unsuspends the job whilst the screen is still too small? The unsuspend routine could surely check the screen dimensions and refuse to unsuspend the job if the screen is too small...