[fpc-devel] (no subject)

[Tomas Hajny]

On Thu, 13 Jan 2005 14:04:10 +0100 (CET), Ladislav  Lacina wrote
> Message: 2
> Date: Wed, 12 Jan 2005 17:31:41 +0100
> From: "Tomas Hajny" <XHajT03 at mbox.vol.cz>
> Subject: Re: [fpc-devel] The new 1.9.6 release
> To: FPC developers' list <fpc-devel at lists.freepascal.org>
> Message-ID: <20050112162823.M95937 at mbox.vol.cz>
> Content-Type: text/plain; charset=iso-8859-2
> 
> > Ladislav Lacina wrote:
> >
> > > There are many problems in this version - at least under the GO32V2
> > > target. Mainly the things asociated with the FreeVision. Even the
> > > installer doesn't work properly. The mouse is not visible and the 'OK'
> > > button is in strange way hidden. Nor in the IDE is the mouse not shown.
> > > Interresting is, that if you go to the Dosshell and return, the mouse
> > > works properly. And there are many other problems.
> > > Anyway thanks for the FreeVision. Finally. I modified it to use with the
> > > previous 1.0.10 version.
> > > And the last thing - will be in IDE in the official 2.0 version support
> > > for VESA modes?
> > > I very miss it.
> 
> >1) The mouse cursor issue is already known, it will be researched and
> >hopefully fixed.
> 
> >2) For the other problems, please, report them using the bug repository
> >accesible from our WWW pages.
> 
> >3) Regarding VESA modes, what exactly do you miss there - extended text modes
> >(132x50, 132x60 etc.), or something else?
> 
> >Regards
> >Tomas
> 
> Yes, I mean the extended text modes (132x50, 132x60,...)

I guess that implementing this functionality shouldn't be that hard, in fact.
It needs the following changes in video.pp for GO32v2 as far as I can see:

- New function checking for VESA availability and adding the found text modes
to SysVMD table (which must be extended to be able to accomodate the new
modes) - let's call it GetVESAModes. This function can be derived from
vesa.inc located in the GO32v2 directory in RTL sources (GetVESAInfo,
GetVESAModeInfo). The found information should be kept in (copied to) global
structure to allow finding mode number when switching to this mode.

- Add call to this new function to unit initialization (after SetVideoDriver
call).

- Provide new DoSetVESAMode function which can find the requested mode in the
list of all available VESA modes (kept from GetVESAModes call), derive the
appropriate mode number from it and change to this video mode using function
4F02h on interrupt 10h (see SetVESAMode in vesa.inc).

- Change SysSetVideoMode to call DoSetVESAMode for video modes placed in
SysVMD with index 5 and above.

I don't have time to do that myself, but I'm willing to assist anybody in
resolving encountered problems etc. (you can contact me directly).


Tomas