This was causing obvious confusion for users - misclicking outside of
the pop-up caused a dismissal where the consequences were not at all
clear.
So let's drop that behaviour entirely. You exit the dialog through
explicit button or key presses only.
- Simple implementation of OS list fetching in backend
- Replace frontend OS list fetching by calls to backend
- OS list updates are brought in asynchronously, avoiding excessive UI
blockage.
- "Erase" and "Custom" OS list options are always present, even in a
no-internet scenario
Based-On: cillian64/rpi-imager/oslist_backend
We're going to take advantage of the
convention of always putting the recommended OS first in the list, and
append "(Recommended)" to it's description.
This moves the recommendation out of the JSON, and makes the
recommendation durable to filtering.
When filtering the OS list, if all items in a category/sublist are
filtered out then don't show the category/sublist.
Also, clear the selected OS when the HW device is changed, otherwise you
can get weird effects like having an incompatible (hw, os) pair selected
or the highlighted OS moving when the items in the OS list change.
- All of our red buttons were ImButton with the colours overridden at the
use site. Instead make an ImButtonRed which defines these colours in
one place.
- Previously the red buttons had focus indicated by the text colour
changing from white to blue. This was quite hard to see, instead
change the button colour to blue (as is done for the white buttons).
A darker shade of blue is used so that there is still good contrast
with the white text.
- Update the reds (buttons and main screen background) with the
branding-approved red: the official colour palette says Pi Red is
#cd2355
- Make write confirmation popup modal
- Force focus on the write confirmation popup when it opens
- Force focus on the error popup when it opens
- When the hw select popup opens, force focus on the ListView instead of
on the currentItem, because the latter doesn't work when the list is
empty.
- On embedded, when the settings popup closes, force focus back to the
usecustomisation dialog
Previously, if you clicked "edit settings" in the "use customisation"
msgbox then the flow got a bit confusing, when you saved settings the
"use customisation" msgbox would have disappeared and you had to click
"next" and go back through again. Instead, keep the "use customisation"
msgbox open when editing settings so when you save settings you are back
where you left it.
Also:
- Make "use customisation" modal so you can't click other things while
it's open
- Separate windows in QtQuick can't be modal so we can't stop the user
interacting with the main window while "edit settings" is open. This
could get confusing, so if they close the "use customisation" modal in
the main window then close the settings window.
- Fix a bug where saved settings weren't recognised on startup, only
after being saved during the session
In the new flow, it doesn't make sense to _not_ save the OS
customization parameters, so remove the ComboBox.
Additionally, our data model was failing to notify the UI of changes to
the saved settings state. Due to time constraints, I'm not able to
resolve the binding in the 'correct' manner, but I can introduce a
makeshift status signalling mechanism to prevent UI inconsistency.
Previously it was not possible to select a HW device without a mouse
because the focus change to the HW list was not working. This is
because an extra nested ListView had been left in. Remove the extra
ListView and set the focus target correctly.
Seems like there's a weird Qt bug in the ProgressBar widget where giving
it padding means the white progress indicator doesn't actually start at
the left edge of the bar or extend to the right edge of the bar. So
just remove the padding from ProgressBar because it's not doing much.
- Update back to colour logo
- Change logo alignment and positioning to make it generally
left-aligned, have some nice padding above and below it, and to not
occupy the full window width.
This patch carries a translation risk, as we change the default
progression button.
Remove the customisation button all together, and make the customisation
options something we offer as part of flashing an image that
has that capability.
While this adds an additional click to the flash sequence, it should
provide a steer to people who are flashing customisable images to make
use of this capability, potentially avoiding an additional pass through the
Imager.
This change adjusts the layout for the progress bar, write button and
cancellation buttons such that they are all placed on the same layout
'row', with the progress bar stacked as before, and the
write/cancel/cancel buttons stacked as a column.
This is not ideal, but probably as sensible as we can get inside this
layout paradigm.
1) Resize the window back to 680dip default widths. We don't need the
extra space now.
2) Reduce Row spacing within the grid layout. We need all the space we
can get.
3) Assign layouts to explicit cells, at least for selection options and
write. This layout isn't really scaling to the amount of data we want
to provide, but we'll make do for now.
4) Mark selection buttons as accessibility ignored when the hwpopup is
active.
