Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-50705

Functionality from QtQuickControls 1: Action



    • Suggestion
    • Status: Closed
    • P3: Somewhat important
    • Resolution: Done
    • 5.6.0 Beta
    • 5.10.0 Alpha
    • Quick: Controls 2
    • None
    • 4aa35f5acabc352894a40310d378e6a97b92f59a


      QtQuickControls 1 had a pretty abstract way to define actions, that was the Action object. That way it was possible to separe decently the definition of actions (with its text, icon, state, keyboard shortcuts and so on) and their final representation (which didn't really matter if the UI was then implemented by some standard component or in a completely custom way by the user)

      While it's still possible to use the Action object from QQC1, I understand that the objective in the long run is to migrate completely to QQC2.
      I think this component was important from a design point of view, even tough would have been even better for it to be available from C++ as well (so that makes it easy making it a bridge between the logic implemented in C++ that could provide a model of actions and the representation written in QML) So I'm not even sure the real place for it would be qtquickcontrols2 or rather qtquick or even qtgui (unfortunately QAction is not usable in situations were the dependency from QWidgets can't be used)


        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.



              Unassigned Unassigned
              mart Marco
              5 Vote for this issue
              6 Start watching this issue



                Gerrit Reviews

                  There are no open Gerrit changes