From:	Doug Eleveld <D DOT J DOT Eleveld AT anest DOT azg DOT nl>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Suggestion for Allegro...
Date:	Wed, 15 Oct 1997 22:20:26 +0100
Organization:	Rijksuniversiteit Groningen
Lines:	28
Message-ID:	<3445339A.7F98CE24@anest.azg.nl>
NNTP-Posting-Host:	client36-65.oprit.rug.nl
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Hi Everybody,

Normally I'd email this directly to Shawn, but I'm at home now (where I
have mews but no mail) and also I'd like other peoples vews on this...

I know that Shawn has been putting some work into making Allegro's lib
smaller and I just got (maybe) some kind of brainwave...

I know that the DAT files can carry code because you can put compiled
sprites into the DAT files. Now, isn't it possible to also put some mode
changing code or driver code into a dat file and have some small kernal
always in memory that takes the requests, searches for the right DAT
file and driver and load that into memory?  The memory footprint gets
alot smaller and only the necessary stuff gets loaded.  

Is this a crazy idea?  Is normal code too complex to go into a DAT file? 

Any ideas?

Doug Eleveld

P.S. Shawn, if you are reading this, the docs for the gui stuff doesn't
seem to mention that if an d_xxx_proc returns D_WANTFOCUS from a
MSG_LOSTFOCUS, that the focus will only be actually taken away if the
destination object has retuned D_WANTFOCUS to it's MSG_WANTFOCUS.  That
means that if an object returns D_WANTFOCUS from a MSG_LOSTFOCUS, that
the focus has to be forced away to another d_xxx_proc that wants the
focus.

- Raw text -