Skip to content

Conversation

keithel-qt
Copy link
Contributor

Removal of 'SwiftNav' Qt Quick Control style

Because QTBUG-108518 will not be resolved in time for 6.5, we must remove the use of custom Qt Quick Control Styles that require fallback to another style, as the fallback style's theme does not properly initialize. (See bug).

This removes the SwiftNav style Qt Quick Controls.

Some additional things done here:

  • Remove use of SwiftButton where the customization done in SwiftButton was not used, and Material button is more appropriate to use with the same look and feel.
  • Remove use of SwiftComboBox where the customization done in SwiftComboBox was not used, and Material ComboBox is more appropriate to use with the same look and feel.
  • Remove access to change orientation of TabBar, as this was never used. It was originally added, as the original implementation of the SideNavBar was originally implemented with an altered Vertical TabBar, however when I refactored it, I found that TabBar was not the right tool for the job, and abandoned the TabBar based SideNavBar implementation. This was a vestige of that logic.
  • Use swiftWhite constant instead of literal "white".
  • Tweaks to the SwiftTabButtons on the TabInfoBar to make it display correctly.
  • Fix "Binding on indicator is not deferred" (one instance of these "not deferred" warnings)

Fixes:
    "Binding on indicator is not deferred as requested by the
     DeferredPropertyNames class info because it constitutes a group
     property."

This fixes one instance of the Binding not deferred warning.
It also shows better form - where you should not infer the
implementation of a QML Item from another QML file that uses it. Alter
internals using toplevel properties instead.
Because QTBUG-108518 will not be resolved in time for 6.5, we must
remove the use of custom Qt Quick Control Styles that require fallback
to another style, as the fallback style's theme does not properly
initialize. (See bug).

This removes SwiftNav style controls for all but TabBar and TabButton.

Some additional things done here:
* Remove use of SwiftButton where the customization done in SwiftButton
was not used, and Material button is more appropriate to use with the
same look and feel.
* Remove use of SwiftComboBox where the customization done in
SwiftComboBox was not used, and Material ComboBox is more appropriate to
use with the same look and feel.
Because QTBUG-108518 will not be resolved in time for 6.5, we must
remove the use of custom Qt Quick Control Styles that require fallback
to another style, as the fallback style's theme does not properly
initialize. (See bug).

This removes the SwiftNav style Qt Quick Controls.

Some additional things done here:
    * Remove use of SwiftButton where the customization done in
      SwiftButton was not used, and Material button is more appropriate
      to use with the same look and feel.
    * Remove use of SwiftComboBox where the customization done in
      SwiftComboBox was not used, and Material ComboBox is more
      appropriate to use with the same look and feel.
    * Remove access to change orientation of TabBar, as this was never
      used. It was originally added, as the original implementation of
      the SideNavBar was originally implemented with an altered Vertical
      TabBar, however when I refactored it, I found that TabBar was not
      the right tool for the job, and abandoned the TabBar based
      SideNavBar implementation. This was a vestige of that logic.
    * Use swiftWhite constant instead of literal "white".
    * Tweaks to the SwiftTabButtons on the TabInfoBar to make it
      display correctly.
@swiftnav-travis
Copy link

Frontend and Release Workflow Started here

Copy link
Contributor

@adrian-kong adrian-kong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@keithel-qt keithel-qt merged commit 276b791 into main Dec 7, 2022
@keithel-qt keithel-qt deleted the keithel-qt/swift-button-style-issue-711 branch December 7, 2022 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants