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

Move functionality that's not widget specific out of QtWidgets

    XMLWordPrintable

    Details

    • Type: User Story
    • Status: Closed
    • Priority: P1: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 6.0 (Next Major Release)
    • Component/s: Other
    • Labels:
      None

      Description

      The QtWidgets module includes several components that are not widget specific, and that should be moved out into a separate module, into QtGUI, or into QtCore.

      Recommendations:

      • Run a Qt Creator's clang checks on the code base first to identify (fix in Qt 5)
        • Static invocations: Fix qApp->sendEvent() and similar to QCoreApplication::sendEvent() (reduce dependencies on QApplication)
        • Use member initialization in private classes to reduce constructor #ifdefery
        • Check the autotest of the class and port to Qt 5 signal slot connections and ideally also fix nullptr to get rid of things like (Class *)0.
      • On no account introduce workarounds forward-declaring QtWidget classes from QtGui . This creates huge problems for Qt for Python.
      • Test source compatibility by compiling Qt Designer

      In conjunction with the QAction removal: it might make sense to move QShortcut out (that is, extract a QAbstractShortcut into QtGui) - depending on whether that makes sense for Quick controls (Friedemann, 6/19).

        Attachments

          Issue Links

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

            Activity

              People

              Assignee:
              vhilshei Volker Hilsheimer
              Reporter:
              vhilshei Volker Hilsheimer
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: