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 selects
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 whole
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
@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
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
Igevorse,
I enjoyed reading your latest blog post: Realtime midi input: to be or
not to be?
http://igevorse.lited.net/p7.html
I tried to comment on the blog but I'm not sure it went through. Here's
a copy of what I wrote. My point isn't to say it is impossible, but to
say that it is more