Norman Dunbar wrote:
>I've made my changes to allow Screen Snatcher to grab an entire
screen
>regardless (?) of the resolution, colour depth etc. Now when I run
this
>version, I get a 'Value out of range' error as follows :
>
>Job 13 SS3 Line 2160 SCR_YLIM
>value out of range
>Retry Continue Abort R/C/A
>
>The line(s) in question are :
>2145 ScreenDepth = 256
>2150 ScreenWidth = 512
>2155 IF CHECK("scr_ylim")
>2160 ScreenDepth = SCR_YLIM
>2165 ScreenWidth = SCR_XLIM
>2170 END IF
>
>But when I build a small test program which has those lines in it, it
>compiles and runs ok.
>I'm rapidly going off QLiberator :o(
>
>The variable has *not* been declared elsewhere in the program - other
that
>at line 2145 as shown above.
>I'm not running with REMARK $$i to use full integer mode (so it
defaults to
>$$f for full float mode).
>Screen resolution is currently 800 by 600 in full colour mode.
>
>What's going on ??????
QLiberator can have an automatic integer feature under some
circumstances. Best option is to keep adjusting until you can isolate
the construct in which it occurs. Does SCR_YLIM open a temporary
channel or is it looking for a primary channel - does your program
have windows open when you test screen sizes or do you open them
afterwards? Compile with windows copied to see if it makes a
difference to when you compile with no windows copied from basic.
Probably won't be helpful to say this - I still prefer QLiberator even
to the new Turbo, but probably because I'm more familiar with it. The
only problem I had was with compiling programs into toolkit-style
extensions (I think they're called externals?) with it, which I've had
little success with under SMSQ/E although OK under QDOS.
--
Dilwyn Jones
[EMAIL PROTECTED]
http://www.soft.net.uk/dj/index.html
