- 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
It is possible to connect to open wifi networks using raspi-config or
the wf-panel-pi GUI. It was also possible in rpi-imager but only with a
workaround - if you entered a dummy PSK it would be ignored if the SSID
was that of an open network. (This also meant a Pi could be tricked
into connecting to an open network on first boot even if a PSK was
configured).
The change in https://github.com/RPi-Distro/raspberrypi-sys-mods/pull/83
has a side effect which means that Pis will no longer connect to an open
network if a PSK is configured.
This commit lets the user enter no PSK to indicate that an open network
should be configured.
Resolves#424
This is a compromised change. Essentially, I'm working around a
poorly-understood failure mode in Qt5, where the disk cache can
occasionally fail to invalidate, resulting in stale compiled units being
used.
This will increase application start times in favour of correctness.
In order to prompt issue reporters to provide more information up front, introduce some issue templates.
This is the start of a wider initiative to add some structure to how we respond to issues.
In order to ensure the 'Recommended' tag shows up for older versions of
the Imager, we should migrate to using V4 for the version where we move
the tag out of the JSON file.
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.
With the move from OS customisation being a popup to being a separate
window, it is no longer closed by the escape key. Add a handler to
restore this behaviour.
- 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
As part of changing the reference string, these translations will
require a rework.
Signed-off-by: Tom Dewey tom.dewey@raspberrypi.com <tom.dewey@raspberrypi.com>
We've now modified the UI in a fairly major way - but no so much that
it's unrecognisable. As a result, bump the version number to the next
minor revision.
- 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
