Hi all,
I've now converted my ancient QBX programmes into Powerbasic and they really fly (well, as much as any 20,000 line project hooked up to Novell3.2 can 'fly').
We have a couple of programmes that need 50 line mode, so I'm using Console Set Screen to switch and then switch back to 25 lines when I'm finished.
I'm now almost certain (having stuck debug code before and after) that Console Set Screen is coming back with occasional Illegal Function Calls - this doesn't happen every time, but is really worrying.
I'm not doing anything bizarre with screen sizes, I just want 50 line and 25 line modes.
As a last resort I've just re-written all my Console Set Screens to call a single function which checks the current screen size, and then only if it's different to what's been requested, the Console Set Screen is issued.
Has anyone else had anything similar?
Are there any other Windowsy ways to change screen size (which wouldn't report the error) - I'm know I could 'trap' this error, but it'd be nice to know what's causing it.
Regards, John
I've now converted my ancient QBX programmes into Powerbasic and they really fly (well, as much as any 20,000 line project hooked up to Novell3.2 can 'fly').
We have a couple of programmes that need 50 line mode, so I'm using Console Set Screen to switch and then switch back to 25 lines when I'm finished.
I'm now almost certain (having stuck debug code before and after) that Console Set Screen is coming back with occasional Illegal Function Calls - this doesn't happen every time, but is really worrying.
I'm not doing anything bizarre with screen sizes, I just want 50 line and 25 line modes.
As a last resort I've just re-written all my Console Set Screens to call a single function which checks the current screen size, and then only if it's different to what's been requested, the Console Set Screen is issued.
Has anyone else had anything similar?
Are there any other Windowsy ways to change screen size (which wouldn't report the error) - I'm know I could 'trap' this error, but it'd be nice to know what's causing it.
Regards, John
Comment