Re: The "magic" 0x80008001 ComponentResult

Subject: Re: The "magic" 0x80008001 ComponentResult
From: Kevin Marks <email@hidden>
Date: Tue, 21 Nov 2000 22:20:15 -0800

At 10:28 PM -0700 11/21/00, Chris Gehlker wrote:

I've seen this number as a result code in two different programs when I
screwed up and tried to operate on a closed component. I wonder if it is so
regular that it could be documented as the "attempt to operate on a closed
component" result code. It's a little disconcerting when routines return
undocumented results.

Nothing magic about it, its in MacErrors.h in UniversalInterfaces;
enum {
badComponentInstance = (long)0x80008001,
badComponentSelector = (long)0x80008002
};

Its been documented since the first QT book about the Component Manager came out in 1991 or thereabouts.

The confusing part is when these errors get truncated to a 16-bit OSErr, giving -32767 and -32766 respectively.

References:
	>The "magic" 0x80008001 ComponentResult (From: Chris Gehlker <email@hidden>)

Prev by Date: Resampling movie geometry
Next by Date: Resampling movie geometry, again
Previous by thread: Re: The "magic" 0x80008001 ComponentResult
Next by thread: Resampling movie geometry
Index(es):
- Date
- Thread

Home