Dear Michael, You wrote: > OK, so what we need is a way to be able to activate > something that's already > activated, in essence, right?
correct so far. You wrote: so let's > just think about pressing the 6 key. I'm in note > mode, with 16th note > selected, I switch to erase, and want to go back to note > mode. I can't press > 6 to get there. > Incorrect. Using the keyboard shortcuts, we "can" go back into Note/Rest Inserter from any tool. There is no problem here. You wrote: > We apparently have a similar problem with the > buttons. 16th stays pressed, > and I can't re-press it to get back to note mode. > (I'm not looking at this. > Haven't done any new compiling yet today.) > > Is this the gist of it? This is the only remaining problem. If the 16th note is selected (pressed), it can not be pressed again. The GUI for exclusive groups, does not let a pressed button emit the clicked() signal or the pressed() signal. Toggle buttons, like chord mode act differently. One press turns it on and another turns it off. So, that is one route to go but but keeping track of all of that can get a little messy. I was looking for a clean solution. Somehow a clicked() or pressed() signal need to trigger the slotSetNoteRestInserter() slot. That is all that needs to happen. ... Ok. I think I just answered my own question: Button groups can be exclusive or not. http://doc.trolltech.com/4.5/qbuttongroup.html#exclusive-prop If we turn off the exclusive feature then pressing a pressed button will turn it off. ... [Note: Edited a stream of thought that lead me to this solution] ... I propose that this: * Use setExclusive ( false) on the Duration Toolbar->duration_toolbar group * place QString *m_pressedButton in class variable in NoteRestInserter to track which of the last button is pressed (strip "duration_" from name when appropriate). * compare the calling actions name to m_pressedButton - if equal, setChecked(true) the button and process the request. - if !equal, findAction(m_pressedButton)->setChecked(false) and process the request It's late and I'm certain there is an even more efficient method using QAction in NoteRestInserter instead. You wrote: > I can probably sort that out, but it would be helpful if > you could sweep away > all the big globs of surrounding discussion, and filter the > requirement down > to something very concise and simple. Sorry, If I have failed you in this regard. But that might be the "best" solution I can muster now. That is unless there is a real QT heavy hitter that has a better plan. But this sounds workable. What are your thoughts? I'm happy to code it. ...Now what about the accidentals menu? What are your thoughts about my idea of having the trigger the setNoteRestInserter()? Sincerely, Julie S. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
