[Openal] Weird AL_INVALID_NAME error
garinh at turkeytrot.dhs.org
Wed Apr 7 09:09:55 PDT 2004
> 1. There's really a need for an updated documentation resource that
> includes possible error sources. Is there any such project somewhere
> I've missed?
No -- you haven't missed any available documentation. Better
documentation of the possible errors for each function and what causes
them is a to-do item on my personal OpenAL 1.1 list. Joe Valenzuela
will be coordinating a 1.1 effort soon, and so this will come up.
> 2. Wouldn't it be more appropriate to have another error there?
> AL_INVALID_NAME is supposed to occur if I send an invalid name to an al
> function - the error in this case was caused by a bug leading to that
> alSourceQueueBuffers wasn't called at all. That is, i never gave an
> invalid name as a parameter. Something like a new AL_INVALID_BUFFER or
> such would maybe be more true to what actually happens.
Good point -- I'll make sure that's on the list of things to think
about for 1.1.
Thanks Michailis for the extra detective work!
More information about the Openal