Dilwyn wrote :
>> Remember that Aurora screens are different - the bytes per line
>> increment may not be the same as the number of bytes used to store one
>> line of pixels in mode 4.
Does this mean that the width of a display line as returned by DISPLAY_WIDTH
could be, for example, 200 bytes, but in the resolution/mode being used
currently, only the first 100 bytes of each display line is being used ?
If this is so, then SS3 will snatch all 200 bytes for each display line -
this shouldn't be a problem, because the first 100 bytes are being used but
the second 100 isn't. Ok, there will be a waste of 100 bytes per screen line
on the resulting file, but ......
>> Yes please! I'd like to be able to save in both formats.
Can you, or someone, remind me of the format again please :o)
>> Outline being saved perhaps (try setting the window to 2x1 pixels to
>> see)
Not sure I understand, I basically do this :
open #3,con_
MDRAW #3,menu
MCALL ......
if ACTIVATE hit then I
MCLEAR #3 <-- This works in the old version but not in the new
version :o(
CLOSE #3
REPeat monitor
if keys pressed = snatch combination, then
grab screen
save to file
OPEN #3
MDRAW #3,menu
etc ...
end if
end repeat
end if
Where would I redefine to 2 by 1, and why ?
>> I could test it on Aurora, up to 1024x512, my monitor can't handle
>> Aurora 1024x768 or 1024x576.
Sent zip file under separate email.
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
----------------------------------------------------------------------------
----
