> > extension libs. I'm not sure I like this Attach business. It seems to
> > me that changing the nature of the visual after it has been created
> > could be confusing to a user. How do they know if attachments have
> > been made?
They don't need to. If they want to use an extension, they attach it, when
they don't need it anymore, they detach it.
> > Should they check to see if say libXMI has been added to the visual
> > before using these library routines?
No. They should have attached it in the first place.
> I see no problem with this, and neither should you...
> Knowing whether an extension has been attached is exactly the same
> issue as knowing whether a mode has been set or whether the visual
> has been opened at all, or whether the memory pointed to by your
> program's foobar pointer has actually been allocated. If you want
> to use an extension you attach it after opening the visual, it's
> that simple.
There is a small point where it is an issue, but an issue we have already
thought about:
Libraries that internally attach extensions.
They should not need to bother whether the user already attached it, doesn't
care, or attaches it later.
This situation is taken care of by having the ability to attach multiple
times. That is: The same extension can be attached to the same visual
multiple times. All this will do is increase a counter and detach at
counter==0. The point is, that lib and program become independent.
CU, ANdy
--
Andreas Beck | Email : <[EMAIL PROTECTED]>
