Xref: news2.mv.net comp.os.msdos.djgpp:6233
From: jpdelprat AT teaser DOT fr (Jean-Pierre Delprat )
Newsgroups: comp.os.msdos.djgpp
Subject: Re: GNU Make, DJP, JPTUI etc.
Date: Sun, 21 Jul 1996 15:54:09 GMT
Organization: Guest of France-Teaser
Lines: 49
Message-ID: <4stqo9$6e9@news.teaser.fr>
References: <Pine DOT SOL DOT 3 DOT 91 DOT 960718163607 DOT 16050B-100000 AT zveris> <Pine DOT NEB DOT 3 DOT 93 DOT 960719163634 DOT 2019D-100000 AT ananke DOT amu DOT edu DOT pl> <4sp310$qlk AT news DOT teaser DOT fr> <Pine DOT SOL DOT 3 DOT 91 DOT 960720152820 DOT 20831A-100000 AT zveris>
NNTP-Posting-Host: ppp2816-ft.teaser.fr
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

>> >Conerning JPTUI, I have two further suggestions:
>> >  1. Why does it require mouse driver to be installed - pretty annoying when
>> >one (as me) doesn't have mouse driver installed in AUTO*.BAT - I need to
>> >install the driver everytime. The library should work also without driver in
>> >memory.
>> 
>> Ok, I'll fix that.
>> 

>  I've been thinking about that kinda stuff too, but... [1] How will you 
>determine port and irq settings? [2] are you aware that different kinds of
>mice (eg. PS/2 vs Logitech) send data to ports in different formats? Anyway,
>if you are still willing to try, I've some documentation on that, let me 
>know and I'll mail it to you.

What I intend to do is only ignoring the mouse if a mouse driver is
not installed. I don't want to write a mouse driver myself whereas
some very good ones exits.

>  BTW, sorry for the misleading post about seeing jptui32s.zip. I never 
>saw it, I just thought I saw it. There were so many jptui* files in v2tk 
>that I got mistaken... sorry again.

Don't worry. It doesn't matter at all.

>  Now about that video mode stuff... You see, non-standard video modes use
>different sizes of character bitmaps. It should all be in your video card's
>documentation. Aside from that I believe there are int $0x10 subfunctions
>to determine the size of the character. Determining the dimensions of the
>screen is even simplier: see source for ScreenLines() and ScreenColumns() in
>libc. BTW, did you know most video cars have 9x16 fonts these days? E.g. on
>my TGUI9440, mode 03h is 80x25, 9x16. Mode 58h is 132x30, 9x16, while mode
>54h is 132x30, 8x16 and the characters look much nicer in 9x16. Somehow BIOS
>font reloading functions work with 9x16 as well, though the mouse pointer
>acts like "wider-thinner" when being dragged horizontally arcross character
>cell boundaries.

It shouldn't be a problem. The problem is that I use direct memory
access to define chars and put characters to screen. I hope the memory
organization is the same in non-standard video modes. I'll check and
add a text mode at a time. For the time being I've nearly added
support for 80x50 and I've defined fonts 9x16 (8x16 in fact) and 8x8.

Regards
---------------------------------------------------
Jeepy (Jean-Pierre Delprat)
email : jpdelprat AT teaser DOT fr
web : www.teaser.fr/~jpdelprat