Since the children don't adjust their height based on if they are visible (which would cause a binding loop) we just need to adjust the height of the total menu based on which children are visible. Easy enough.
Contributes to issue CURA-5876.
It won't show the drop-down icon then, won't do hovers and won't allow you to click on it. This will not remove the contents of the ExpandableComponent menu bar item though, so that has to be done in ConfigurationMenu.qml.
Contributes to issue CURA-5876.
We need to make this a reusable component at some point, I think. This is the first time we're using the QtQuick2 version of ScrollView.
Contributes to issue CURA-5876.
This fixes a mysterious segfault. We still don't know why the segfault occurred though. All we know is that QML logs something about a binding loop on currentIndex, and Qt logs something about removing range [-1 through 0] from VisualItemModel. When the tab bar is then made visible, Cura crashes. It is a nondeterministic crash. After this change, we are not seeing it any more (but with any nondeterministic bug, it's hard to verify that it was actually fixed).
Contributes to issue CURA-5876.
* ui_rework_4_0:
Ensure that reset always correctly gets set to basic
Remove semi-colon
Simplify preview icon logic
Always return a string for preview icon
Update USBPrinting version to 1.0.1
Fix module importing in USBPrinting
When toggling auto-slice, force a re-slice
Fix multi-argument i18n string
Improve printer status handling
Make "finishes at" single translatable string
Improve exposed progress prop
Simplify logic slightly
Handle idle, unavailable, and unreachable states
Improve printer status and progress bar
Improve date rendering
Add some typings
Move isActive and timeRemaining logic from QML to Python
Apparently the default for this depends on some system setting. In Nallath's computer that system setting makes it false by default for some reason.
Contributes to issue CURA-5876.
This actually changes the secondary colour to be darker for the dark theme, to be more in line with the general theme then.
Contributes to issue CURA-5876.
The old code that simply resetted the preferences was still active, but this could cause a race condition
in some situations. In those cases it would first set it to basic and then clear the preferences (thus
resulting in no settings being visible)
CURA-5981
