I needed to find a new solution, that was general enough to cover if not all, at least most of the usecases. The bigger picture: All shortcuts are global and any key or key sequence that is assigned as shortcut will be sent to the QAction object, instead of the widget that has focus. Remainder: The problem with the Return key was that the shortcut was global and other objects did not receive an event when it was pressed, because Qt was sending the event to the QAction object that had the key assigned to instead of seding it to the widget that had focus at that moment. I’ve removed that Enter key from being a shortcut, but that doesn’t stop any user to add it again. – secondly, there was no way of knowing what shortcuts would every user add/change. Shortcuts are now configurable through the preferences dialog, using the shortcuts tab, or using directly the shortcuts.xml file – first of all this would meant that a lot of shortcuts would have been hardcoded. It was clear that I could not treat every shortcut that creates conflicts like a KeyPressEvent for two main reasons: There is the same problem with the arrow keys and some other shortcuts used for editing and selecting text (like Ctrl+A, Shift+RightArrow, etc). At the end of this conversation, we both understood that the Return key problem was just a piece of the bigger picture. Everything looked good at this point, I was preparing to make my first Pull Request and just when I was thinking about it, I started talking to Marc Sabatella, telling him what I’ve did, what works and what are my concernes. These are: MuseScore Connect, Palette, Piano and Inspector. I’ve managed to remove from the tabbing order every subwindow of the main window that doesn’t have yet support for accessibility. I’ve mostly worked on tabbing through the main window. This week was a bit unusual, so I can’t structure this blog post in the way that I did before.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |