[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Okay, I'm going through some of the docs here. I haven't gone through
the majority of the docs yet, but I'll write this out as I see them.
In readme.txt, it mentions the Alleg5 mailing list. I don't really know
what Bob and Peter are planning to do with the list yet, but I
personally think it's safe to say it's rather defunct. I don't think we
have to remove the reference to it, but I think a little note about its
current status should go in.
In help.txt, there's this note in determining the cause of a problem:
"I'm afraid your only option is to get a better VESA driver, either by
hassling the manufacturer to fix their bugs, buying Display Doctor, or
writing a FreeBE/AF driver for your card (see
http://www.talula.demon.co.uk/freebe/)."
The good news is that SciTech Software has released Display Doctor (both
DOS and Windows versions) for free. There's a place on their website
where they provide you with the download and a serial key to register
with. They don't, however, provide support for the products anymore.
Near the end of help.txt here it has the example, it has the "user"
detailing his system: "I'm using Allegro 3.0 with djgpp 2.02 (gcc
version 2.8.1) on a p166, running under win95 and using the builtin VESA
2.0 driver, which the vesainfo program describes as "Matrox Graphics
Inc."" Granted it's not so much important, but do you think we could up
those version numbers and specs a bit? ;)
In const.txt, there's this in the closing paragraph: "I have only tested
this myself on DJGPP 2.95.2, so if you have experiences of it not
working (I have tried to get Linux and BeOS ports right, but I've no
guarantee it worked...) email me the *exact* error message and I will
fix it." I think we can safely say that Allegro is more or less
const-correct. :)
In allegro.txt, the function allegro_message has this as an example:
ret = allegro_init();
if (ret != 0) {
allegro_message("Sorry, couldn't init Allegro (%d).\n", ret);
exit(ret);
}
Is it alright to call allegro_message if allegro_init fails like that?
The cpu_* vars say this: "You can read this variable after you have
called check_cpu() (which is automatically called by allegro_init())."
It seems a little over-the-top to say you can only read it after running
check_cpu, then to immediately say check_cpu is called for you.
The PACKFILE typedef lists this as part of the struct:
int hndl; - DOS file handle
I think that would be better worded as 'system file handle'.
Okay, well I got up the the Unicode section, but am having trouble
staying awake. I may take another look tomorrow.
- Kitty Cat