Some things always creep up again :)
If you experience lockups when using ClassAct (or the ClassAct-version
included in "OS" 3.5), you're experiencing the reason why, from a
programmer's point of view, the general design approach of the boopsi
gadget class is not viable and will never yield a usable result (by design,
not by implementation, thus this cannot be "fixed" either. The fix
would be to use a different design of the message handling, and this
is already present, for years. It's called MUI)
Just go back in time, find a distribution archive of Grapevine and find out
about the ObtainGIRPort() "fix" and try to understand the implications
of what is going on there.
The reason that AmIRC is esspecially suspectible to this ClassAct-induced
race condition is simply because AmIRC is one of the few applications which
will initiate rendering operations without user interactions, by means
of network events.
Other than that, there's no reason to blame any of mine (or Jamie's,
or David's) bugs on MUI.
Olli
(running MUI 4 beta)
__________________________________________________________
AmIRC Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
