The default colour for Rectangle is white. So this Rectangle, not defining a colour, became white. Instead we should use an Item, which cannot have a background colour and thus becomes transparent, making the background colour the same as the button below, which was intended. It's also slightly faster to render.
Contributes to issue CURA-6033.
Change some margins for the corresponding absolute values instead of adding formulas.
Contributes to CURA-5876.
Co-Authored-By: diegopradogesto <d.pradogesto@ultimaker.com>
The current behavior now is to open the configuration panel in the previous state, in case it was manually selected. That means that after selecting a printer, the manual state is reset so it will open the auto configuration if it is a connected printer. It will open the custom state in case it's not connected or the printer has no connection.
Contributes to CURA-5876.
But if the printer does have other configurations to change, do show a placeholder text to indicate that the configuration can be selected here.
This also simplifies a bit of code where it would need to call an updateEnabled() function, since it turns out that these properties in Cura.MachineManager have proper signals (contrary to what was previously used, the metadata entry stuff).
Contributes to issue UCRA-5876.
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.
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.
