Hmmm...
 
OK, I understand that if you use DISP_SIZE to alter the screens resolution to a smaller area, any jobs (inlcuding buttons) which have windows which fall outside that DISP_SIZE are removed.  However, there is a problem if the SuperBASIC's windows are larger than the new DISP_SIZE resolution - you cannot get back into SuperBASIC, even after resetting back to the original DISP_SIZE.
 
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 their windows......
 
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.
 
Also, if anyone has followed my work on QWord, they will notice that I now need to perform two main tasks if a QWord is QUIT - namely, remove the QTYP device driver and reset the colour depth and screen resolution if necessary.   Of course, it cannot do this if the job is killed from outside or loses focus  - we really need an event which can be monitored (aka Windows) to allow a program to take certain action when it is killed externally or loses focus.
 
--
Rich Mellor
RWAP Services
35 Chantry Croft, Kinsley, Pontefract, West Yorkshire, WF9 5JH
TEL: 01977 610509
Visit our website at:
URL:http://www.rwapsoftware.co.uk

In need of adventure?
URL: http://www.rwapadventures.com


Stuck with ordinary dial up internet connection ??

Read our review of internet accelerators and broadband at:
URL:http://www.rwapservices.co.uk

Reply via email to