🚀 go-pugleaf

In article <4189@mindlink.UUCP>, a976@mindlink.UUCP (Ron Tarrant) writes:
>> BAXTER_A@wehi.dn.mu.oz writes:
>> 
>> >>handles the startup of multiplot which includes sizing an overscan screen
>> >>depending on the workbench screen size. This code does not break with
>> WB2.0.
>> >>You are welcome to it.
>> 
>> Regards Alan
> 
> 
> I took a look at the code for MultiPlot and unfortunately it doesn't do the
> kind of thing I'm trying to do. Like you said, it will create an overscan
> screen IF the WB screen is overscan (set by MoreRows, et al). What I want to do
> is create an overscan display from scratch so that the end product doesn't
> depend on MoreRows or something else to set up the overscan screen.
> 
> Is there an OFFICIAL CBM  way of doing this?
> Is anyone from Commodore still reading this news group?
> -Ron Tarrant
> a976@Mindlink.UUCP

In a sense, what you need to know to do this, is "What size is the bezel
of the monitor in pizels as defined by the horizontal and vertical size
controls on the monitor... and I don't want to calculate this from the
workbench default!"

This CAN NOT be derived from ANY system information. Under WB2.0 you can find
out the "text" and "overscan" sizes of the screen as selected by the user-
which are supposed to represent what you want to know, and these are used to
set the workbench size. But that in no way stops the user choosing to have
a one inch black boarder all round the active screen, which you won't know
about.

An alternative is just to open an overscanned screen (just use overdimensional
values when specifying screen size) and expect the user to reset the monitor,
but most people on finding the screen cut off by the bezel will assume
you are a shit programmer and not use your program.

Regards Alan