Lee <[EMAIL PROTECTED]> writes:
> I'm trying to come to terms with something here. It has to do with the
> 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? Should they check
> to see if say libXMI has been added to the visual before using these library
> routines? What we have works for small demo programs but for a large scale
> project will it disintegrate into chaos?
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.
Then again, if you think it's worth the overhead you're free to
skip the attach API function in your extension and have all the
extension functions do an "auto-attach" to visuals which it haven't
been attached to already.
//Marcus
--
-------------------------------+------------------------------------
Marcus Sundberg | http://www.stacken.kth.se/~mackan
Royal Institute of Technology | Phone: +46 707 452062
Stockholm, Sweden | E-Mail: [EMAIL PROTECTED]
