Michael: I think I've found the problem and can fix it.
Summary: A signal (selectionChanged) is emitted (in
MatrixScene::setSelection) but never acted on (by slotUpdateMenuStates)
There is code to connect that signal and that slot, but I am not convinced
it's right. There are two prototypes for the selectionChanged signal.
My hypothesis is that we emit the signal with one prototype, but actually
connect the other signal prototype. Result: No connection.
NotationView does almost the same without a problem, which made me unsure.
But NotationScene::setSelection emits on *both* signal prototypes.
So I'm going to try connecting with the right prototype. I think this is
the right way and NotationScene::setSelection is doing more than it needs
to. If that fails, then I'll emit both signals.
PS: Thanks for correcting my style on the wiki and in the .rc. Now that I
know what style is expected I'll do it your way in the future.
Tom Breton (Tehom)
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
