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

Qt 5.6: Pixmap/Bitmap cursors are not scaled when High DPI scaling is in effect

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P3: Somewhat important
    • 5.6.0
    • 5.6.0 Alpha
    • QPA: Windows
    • None
    • Windows, others?
    • 36bb6d266e08ff4ae3c45d2ad428f7f787746b8a (qtbase/5.6, 24.11.2015, 5.6)

    Attachments

      1. qtbug49511_imv.zip
        3 kB
        Friedemann Kleint
      2. qtbug49511.zip
        3 kB
        Friedemann Kleint

      Issue Links

        relates to

        Task - A task that needs to be done. QTBUG-46615 Implement High DPI scaling v2 (5.6)

        • Not Evaluated - Not yet evaluated/prioritized
        • Closed
        resulted from

        Bug - A problem which impairs or prevents the functions of the product. QTBUG-49434 Windows custom cursor too small on hi-res screen

        • P2: Important - Urgent, should be fixed, but will not stop the release.
        • Closed
        For Gerrit Dashboard: QTBUG-49511
        # Subject Branch Project Status CR V
        141434,2 Windows: Refactor cursor handling. 5.6 qt/qtbase Status: MERGED +2 0
        141435,3 Windows: Create one QPlatformCursor per screen. 5.6 qt/qtbase Status: MERGED +2 0
        141436,3 Windows: Scale pixmap/bitmap cursors when High DPI scaling is active. 5.6 qt/qtbase Status: MERGED +2 0
        141437,3 Windows: Scale cursors from resource pixmaps according to screen. 5.6 qt/qtbase Status: MERGED +2 0
        141438,2 Windows: Fix the size of drag cursors in multi-screen setups. 5.6 qt/qtbase Status: MERGED +2 0
        141444,3 Add a manual test for cursors in multi-screen/High DPI setups. 5.6 qt/qtbase Status: MERGED +2 0

        Activity

          People

            kleint Friedemann Kleint
            kleint Friedemann Kleint
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: