Dear all,

Firstly, QLiberator has behaved perfectly today - no compilation worries and
no crashes on running. I wish I knew what was causing the problems :o(

PER : I even managed to REDUCE the stack and heap size from 8K each to 4K
stack and 2K heap as the program only used about 1K stack in the end - good
those stats in Qliberator arn't they - thanks for the reminder.

Next, Screen Snatcher has been updated to save the correct size of a full
screen. It does this by working out the number of bytes per screen line and
the number of lines in the full screen depth, then it saves (line_width *
screen_depth) bytes to file.

Further updates planned are :

option to save in raw mode or _pic mode
option to save an area rather than the entire screen (in raw or _pic mode)


Known foibles :

When EX'd, the main screen appears AND a phantom black screen channel
appears behind it - who knows what this is all about then ?

When Activated (ie told to vanish from the screen and watch the keyboard
queue) it stays on screen !  In the old version, which runs find on QPC2v2,
it does vanish. The new version remains persistant - and I never changed
anything in that bit of the code ! All it is is a single line - MCLEAR #3 -
what's going on ? This happens in High Colour or QL colour mode.


If you fancy being a guinea pig, give me a shout and I shall send you a zip
file (QL Style) with the OBJ and source files for your amusement. I have
tested on QPC2v2 in QL and High Colour mode at 800 by 600 resolution -
nothing else so if you have another system I would be pleased to know if it
works ok for you (subject to the above foibles - which I intend to fix !)

Norman.

----------------------------------------------------------------------------
----
Norman Dunbar           EMail:  [EMAIL PROTECTED]
Database/Unix administrator     Phone:  0113 289 6265
Lynx Financial Systems Ltd.     Fax:    0113 201 7265
                        URL:    http://www.LynxFinancialSystems.com
----------------------------------------------------------------------------
----

Reply via email to