"The problem is SuperBASIC. Any suggestions as to why this happens??"
Aren't Jobs with windows outside the active screen area are killed after a resize? Dont know why. Alternative to resizing SBASIC windows is to put it asleep in a button before resizing and wake after screen resolution is restored. Duncan Neithercut -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Rich Mellor Sent: 27 November 2004 21:00 To: [EMAIL PROTECTED] Subject: [ql-users] Changing display size in QPC2 I know I shouldn't but QWord can be configured to allow it to change the screen resolution and colour depth to suit - it reads the parameters and resets the settings when it quits. The problem lies with SuperBASIC. The button frame can cope with this (although you buttons which could not be displayed on screen at the resolutions set by QWord). The problem is SuperBASIC. QWord uses a resolution of 640x480 If the 3 superBASIC windows (in standard WMON layout) are 640x480 or less, there is no problem. However, if the 3 SuperBASIC windows exceed this, when you quit QWord, you cannot see the SuperBASIC windows at all (even though they would now fit on the screen). Instead you get an empty square as the cursor. The button frame is still working. CTRL C can be used to get to see the SuperBASIC windows. Sometimes the cursor is active, but if you enter a command such as ED or PRINT free_mem - it hangs the system PRINT #0,free_mem works however !! Any suggestions as to why this happens?? -- Rich Mellor RWAP Services 26 Oak Road, Shelfield, Walsall, West Midlands WS4 1RQ http://www.rwapservices.co.uk/ _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
