Albert Santoni wrote: > Were qScriptConnect/Disconnect simply non-existent in 4.3? What are our > options?
That is correct. They don't exist there. We have the option of making every interesting ControlObject available to the scripts, then the scripts can do the (dis)connections themselves. Or we can try having a generic function that makes a requested ControlObject available under a requested name, which the script can then (dis)connect at will. Note that I tried both of these methods and they didn't work for me (due to the strange problem of having to connect every signal I want to use at script init time.) So we'll have to figure that one out first. (And doing so may solve the segfault problem.) "What a tangled web we weave..." Sean <<--------------------------------------------------------------------------------->> This E-Mail message has been scanned for viruses and cleared by >>SmartMail<< from Smarter Technology, Inc. <<--------------------------------------------------------------------------------->> ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
