Subclassing problems and ways to solve

[Tokelil]

As discussed a little in this thread http://www.quinnware.com/forum/showpost.php?p=6831&postcount=19 plug-in developers run into a little trouble when more than one plug-in is subclassing QCD. I guess it isn’t a problem in most cases but it crashes QCD when plug-ins are unloaded in a different order than they were loaded.

Does anyone a good suggestion on how to handle subclassing in a more robust way? Maybe QCD should handle this through ops?

[acozz]

Back in the old forums, Paul said he was working on an op to handle subclassing, but VP said he didn't like the idea. I guess it just fizzled out.

[Tokelil]

I just want to bring this issue up once more before you, Paul, release the next version, since I believe it could add a lot to the stability of the plug-in architecture. It might be that it is only “power users” that will experience crashes from loading/unloading plug-ins, but QCD should provide an op for subclassing. (IMhO)

[plover]

For vis plugins, Paul recently discovered that subclassing would always cause problems given the way QCD is currently organized. I don't know how much other plugin types were affected by what he found, but he said he was considering setting up an API to register subclasses through the player process.

[Paul]

I do think creating subclassing management functions will help plugin developers and users. But I'm not rushing to do it because for it to work all plugins would have to use the new system. Using just one plugin that didnt use the new system would break it. So, then, it becomes less enticing or critical.

[Tokelil]

Okay. Thanks for the response. I'll wait and see what happens then... :)