1. 04 Apr, 2018 - 2 commits
  2. 26 Mar, 2018 - 2 commits
  3. 23 Mar, 2018 - 4 commits
  4. 22 Mar, 2018 - 1 commit
    • Mitch Curtis's avatar
      Fix Shortcuts in Popups with window context not being activated · 1f118ce8
      Mitch Curtis authored
      
      Before this patch, this code wouldn't work:
      
          Popup {
              id: popup
      
              Shortcut {
                  sequence: "Tab"
                  onActivated: popup.visible = !popup.visible
              }
          }
      
      Even though Popup is aware of its Window, the Shortcut object is
      parented to Popup::contentItem, which does not have a Window associated
      with it while the Popup is hidden.
      
      The fix is to check if the item has a window in
      QQuickShortcutContext::matcher(), so that that check fails and the
      QQuickPopup itself is used to access the window.
      
      Change-Id: Ia1c5d75ad6b82fb4c8b7664b6d418d84428b1ddf
      Reviewed-by: default avatarJ-P Nurmi <jpnurmi@qt.io>
      1f118ce8
  5. 21 Mar, 2018 - 5 commits
  6. 16 Mar, 2018 - 1 commit
  7. 13 Mar, 2018 - 1 commit
  8. 12 Mar, 2018 - 3 commits
    • Simon Hausmann's avatar
      Fix doubly connected signals in SignalSequenceSpy · 5c2b1bee
      Simon Hausmann authored
      
      We call __setup() from two different onFooChanged signal handlers. If we
      access the second property from within that method, we may end up being
      the first one to read that property and consequently require an
      initialization of the binding to that property first, which will write
      the value (before returning) and trigger the signal handler, recursively
      calling __setup() and thus calling connect() twice for each signal the
      spy wants to connect to.
      
      This used to be fine as we ended up with a _third_ evaluation that
      called __setup() and thus cleared the connections first, but after
      commit f514451cc2e3610e160b5dc8ccd1e390730ecc67 in declarative we avoid
      unnecessary binding evaluations if possible and therefore uncovered this
      bug.
      
      Task-number: QTBUG-66995
      Change-Id: I83ef9c80978a88c1490174d3cdb21b149733a78f
      Reviewed-by: default avatarJ-P Nurmi <jpnurmi@qt.io>
      5c2b1bee
    • J-P Nurmi's avatar
      ComboBox: fix key search in the popup · 79964673
      J-P Nurmi authored
      
      ComboBox does not change its current index, but highlighted index,
      when navigating in the popup. If the popup is accepted, the currently
      highlighted index is applied as the new current index. However, if the
      popup is rejected, the old current index is kept intact. This is why
      there is a separation between current and highlighted index. The newly
      added key search functionality (added together with ComboBox::editable)
      was missing a check whether the popup is visible. It was unconditionally
      changing the current index, which lead to a wrong behavior when the
      popup was open.
      
      Task-number: QTBUG-61348
      Change-Id: Ic0295db609495ccefbccb7c425a817926786014e
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@qt.io>
      79964673
    • J-P Nurmi's avatar
      Sliders and Dials: keep mouse grab on press · ec9aa9f1
      J-P Nurmi authored
      
      Since Qt 5.9, Sliders and Dials react immediately on mouse press. Thus,
      the old logic to keep mouse grab if the drag threshold was exceeded no
      longer makes sense with mouse. Don't allow e.g. Drawer to steal mouse
      press if a Slider or Dial is already being dragged.
      
      Task-number: QTBUG-66637
      Change-Id: I76f7ab59180c1f3fb66db8412d7cccfbd373aee3
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@qt.io>
      ec9aa9f1
  9. 09 Mar, 2018 - 1 commit
  10. 08 Mar, 2018 - 1 commit
  11. 07 Mar, 2018 - 1 commit
  12. 06 Mar, 2018 - 2 commits
  13. 01 Mar, 2018 - 6 commits
    • J-P Nurmi's avatar
      Platform: fix checkable MenuItem · b4db69ee
      J-P Nurmi authored
      
      Update the internal checked state before emitting triggered()
      
      Task-number: QTBUG-66386
      Change-Id: If120955681b2011bf88126a1ca6032f0af482824
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@qt.io>
      b4db69ee
    • J-P Nurmi's avatar
      Fix QQuickTheme::font() and palette() · 01b0e231
      J-P Nurmi authored
      
      Respect fonts and palettes from :/qtquickcontrols2.conf, but don't
      blatantly override the platform fonts and palettes with null values
      if the fonts and palettes are not set in :/qtquickcontrols2.conf.
      
      Even though fonts and palettes have technically same problem, testing
      the system palette is hard with 5.11 since QQuickDefaultTheme is a
      platform proxy theme and provides a custom system palette. It should
      be possible to have tst_palette::systemPalette() in dev, though, where
      we have removed the inheritance between QQuickTheme and QPlatformTheme.
      
      Task-number: QTBUG-66430
      Change-Id: I6dfe678ccdc7e3990320c120612cfcc68723264d
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@qt.io>
      01b0e231
    • Mitch Curtis's avatar
      Doc: add an "Item Ownership" section toStackView's documentation · 3995d587
      Mitch Curtis authored
      
      It's important that users know the circumstances under which the items
      managed by StackView will be destroyed.
      
      Task-number: QTBUG-66658
      Change-Id: I26e287b3dfed44e441125080443bdae4ee1814b7
      Reviewed-by: default avatarJ-P Nurmi <jpnurmi@qt.io>
      3995d587
    • J-P Nurmi's avatar
      Material: round ripple translation to avoid artifacts · 1dbb132f
      J-P Nurmi authored
      3b36c4e4
      
       rounded translation of the ripple background node. Do the same
      for the ripple wave node.
      
      Task-number: QTBUG-58646
      Change-Id: I455249603e5845a8790dcb374564744de4b880e2
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@qt.io>
      1dbb132f
    • J-P Nurmi's avatar
      Material: calculate BusyIndicator's line width · 70ad96e6
      J-P Nurmi authored
      
      A BusyIndicator with its default implicit size (48px) gets the same
      line-width (4px) as before: 48px / 12 = 4px. The line-width is still
      not adjustable as requested in QTBUG-64872, but tiny and huge busy
      indicators look now much better.
      
      Task-number: QTBUG-64872
      Change-Id: If21feaf1f898b337eae879a961d37b54b217ed87
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@qt.io>
      70ad96e6
    • J-P Nurmi's avatar
      Fusion: fix BusyIndicator · cbf9d807
      J-P Nurmi authored
      
      When running is set to true, QQuickFusionBusyIndicator, which is a
      QQuickPaintedItem sub-class, must trigger an update.
      
      Task-number: QTBUG-66752
      Change-Id: I848a0008d7c8bd3f26f5daf54881c80cc6ba557e
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@qt.io>
      cbf9d807
  14. 26 Feb, 2018 - 3 commits
  15. 22 Feb, 2018 - 1 commit
    • J-P Nurmi's avatar
      DialogButtonBox: workaround implicit size calculation with one button · f1f884d3
      J-P Nurmi authored
      
      When there's only one button in the dialog button box, the Default and
      Universal styles resize the button to cover half of the button box.
      This works in typical scenarios when the dialog button box is assigned
      as a footer of a dialog, and thus, gets resized together with the
      dialog. However, if the dialog button box is placed into a layout, or
      otherwise not given an explicit size, the implicit size calculation
      loops until it reaches zero.
      
       1) button box gets the implicit size of the content (one button)
       2) button box resizes the button to cover half of the box width
       3) button box re-calculates its implicit size => step 1
      
      Avoid the problem by providing a reasonable hard-coded implicit size
      for this special case.
      
      Notice that this is just a temporary workaround to avoid the problem.
      This can be fixed properly in dev by providing separate contentWidth
      and contentHeight properties that cleanly propagate the content size
      to QML.
      
      Task-number: QTBUG-59719
      Change-Id: I552e0824ae6bff26b570c699252a3e4f09bd3397
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@qt.io>
      v5.11.0-beta1
      f1f884d3
  16. 20 Feb, 2018 - 6 commits