[comp.sys.acorn] DSEdit patch

jwil1@cs.aukuni.ac.nz (JasonCarlyle Williams ) (04/11/91)

If you are a compulsive flamer, now would be the time to reach for your 'r'
key...

Due to a high demand (well, actually, very little demand, but a lot of
complaints and bellyaching behind my back on certain UK BBSes (Yes, The
Master of the Arcane sees all!)...), I have decided to post this patch for
DSEdit, which fixes the problem of it crashing (Zero STEP error) if a screen
mode with a larger number than 21 is selected.

To all those puritans out there who think this posting should be to
comp.{sources/binaries}.acorn. Stiff cheeze.

It's only a few lines, so I can't see any valid reason for just posting it.
		    
O.K. To get the latest release version of DSEdit, get your hands on version
0.97 (or 0.96 will do, only it has a few more bugs...!), and then add in a
teensy bit of code as follows:

These lines were taken from the (unreleased as yet) latest version of
DSEdit, 1.00, so the line numbers might not coincide with the same code in
your !RunImage file. Basically, you need to remove the procedure
PROCgetsteps, and replace it with the following:

 1840 DEF PROCgetsteps(RETURN xstep%,RETURN ystep%)
 1850 xstep%=2^FNmodeinfo(4)
 1860 ystep%=2^FNmodeinfo(5)
 1870
 1880 xmax%=(FNmodeinfo(11)+1)*xstep%    :REM OS coords resolution x,y
 1890 ymax%=(FNmodeinfo(12)+1)*ystep%
 1900 
 1910 wleft%=16:wbott%=16                :REM Sound-display area of window
 1920 wwidth%=1024:wheight%=256          :REM (Don't change this!)
 1930 ENDPROC

And then add in the following function just below it:

 1950 DEF FNmodeinfo(V%)
 1960 SYS "OS_ReadModeVariable",MODE,V% TO ,,V%
 1970 =V%

I apologise for the bug, but back in 1989 when I wrote this part of the
DSEdit code, I had no idea of how to read VDU Variables to get the correct
screen sizes. Also, there weren't any wierd overscan modes, etc back then,
so my code ran fine on all the modes I could run it on!

Also, if you have an old version of DSEdit, check it's WimpSlot size. It
only needs around 96kB to actually run, so if yours has a 160kB WimpSlot,
change it. Another hangover from a long development period- By the time I
released it into the PD, I had completely forgotten my initial developmental
WimpSlot!

Version 1.00 is finished; I'm not sure if it's going to be PD, but if I do
release it into the PD, then I assure you that you'll be the first to get
the privilege of crashing your machine with it!

Jason Williams,
The Master of the Arcane.
-- 
New administrater uofa.