Re: [Mscore-developer] Keyboard usability and accessibility

2014-06-09 Thread Marc Sabatella
On 06/09/2014 11:33 AM, Andrei Tuicu wrote: > From the knowledge that I have so far, I don't know any way in which I > can say something like "start from here" for the tabbing order, at > least not provided out of the box by Qt. OK. If so, that means if the Inspector gains focus on simply click

Re: [Mscore-developer] Keyboard usability and accessibility

2014-06-09 Thread Andrei Tuicu
I've created this GoogleDoc[0] were I've assigned every action defined in actions.cpp to its window. I don't know what every action does, so I would really appreciate if some of you could please take a quick look at it. In the column named Observations I've put question marks where I'm not certain

Re: [Mscore-developer] Keyboard usability and accessibility

2014-06-09 Thread Andrei Tuicu
2014-06-09 19:43 GMT+03:00 Marc Sabatella : > > On 06/09/2014 10:03 AM, Andrei Tuicu wrote: > > Regarding your questions: > >Personally, I wouldn't care if clicking in Inspector (or MuseScore > >Connect) *did* transfer focus there completely. It's really only the > >toolbars where this definitely

Re: [Mscore-developer] Keyboard usability and accessibility

2014-06-09 Thread Marc Sabatella
On 06/09/2014 10:03 AM, Andrei Tuicu wrote: Regarding your questions: >Personally, I wouldn't care if clicking in Inspector (or MuseScore >Connect) *did* transfer focus there completely. It's really only the >toolbars where this definitely should not happen. So that's presumably >another optio

Re: [Mscore-developer] Keyboard usability and accessibility

2014-06-09 Thread Andrei Tuicu
@Maurizio Thank you for your feedback! :) I think Marc has explained more acuratelly than me the problem. @Marc Thank you for your explanations. It is clear that I did not explain myself well enough. :) One thing I did not mention and I think it is important. The solution that I've discribed in my

Re: [Mscore-developer] Keyboard usability and accessibility

2014-06-09 Thread Marc Sabatella
One other general comment: it's all well and good for us to theorize about how it might seem if you made certain UI changes, but in my experience, it's often just as easy and almost always more useful to actually implement it and play with it to get a "feel" for how well it works. I find this

Re: [Mscore-developer] Keyboard usability and accessibility

2014-06-09 Thread Marc Sabatella
On 06/08/2014 09:57 AM, Andrei Tuicu wrote: > 3. (optional) Restrict the user from assigning keys like Return, Tab, > Arrow keys as shortcuts. I'm personally OK with this restriction. At least, I can't think of a reason to care. Would this also extend to Ctrl+Arrow, Shift+Alt+Arrow, etc? I s

Re: [Mscore-developer] Keyboard usability and accessibility

2014-06-09 Thread Marc Sabatella
On 06/09/2014 05:54 AM, Maurizio M. Gavioli wrote: > AndreiTuicu wrote >> If for example I select a button using TAB and press Return, the button >> will not be clicked, instead the system break action will be triggered. If >> I'm editing text in a textbox and press CTRL+A I'm not selecting the who

Re: [Mscore-developer] Keyboard usability and accessibility

2014-06-09 Thread Maurizio M. Gavioli
AndreiTuicu wrote > If for example I select a button using TAB and press Return, the button > will not be clicked, instead the system break action will be triggered. If > I'm editing text in a textbox and press CTRL+A I'm not selecting the whole > text, instead I'm triggering the action that select