From: Florian J. <flo...@we...> - 2012-05-06 19:11:20
|
Am 06.05.2012 20:52, schrieb Luis Garrido: > On 05/06/2012 08:38 PM, Tim E. Real wrote: > >> Something may be re-transmitting them to the gui >> and then we get them once more. >> > That may be some kind signal-slot loop, it is a very common problem in > GUI elements which may be changed both programatically (e.g. in response > to OSC messages) and by the user. > > When you change a control in response to an OSC message you must > deactivate its signalling (QObject::blockSignals), change it and > activate signalling again. Otherwise it will be taken as user input, > which will trigger unwanted OSC messaging. > not necessarily if done right. most controls have both a valueChanged() and a sliderMoved or similar signal the first is emitted whenever the value is changed (by the user or programmatically) the second is only emitted when _the user_ changes the value. but iirc not all controls (especially not muse's own widgets) have such. greetings flo > QWidgets have an internal signal block (won't signal back if the change > slot is invoked with the current value) but this is not enough sometimes. > > Luis > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > |