[sc-users] [SwingOSC] order of compilation problem?

[Sciss]

ok i'll try to put it in the next release. thanks for providing the  
fix. ciao, -sciss-

Am 05.01.2007 um 21:03 schrieb Ryan Brown:

>> Could this be related to the recent order of compilation fix?
>
> It does. SwingOSC assumes that OSCresponder has already been  
> initialized in it's initClass, which is not guaranteed. It happened  
> to work before because OSCResponder was initialized before  
> SwingOSC. To fix this add the following to the beginning of the  
> *initClass method in the SwingOSC class in SwingOSC.sc:
> Class.initClassTree(OSCresponder);
>
> Ryan
>
>
> _______________________________________________
> sc-users mailing list
> sc-users at create.ucsb.edu
> http://www.create.ucsb.edu/mailman/listinfo/sc-users