The keyboard: section should be used instead, which should do the right
thing on whatever platform cloud-init is being used on (writes
/etc/default/keyboard on Debian/Ubuntu, uses localectl on RHEL/Fedora,
runs setup-keymap on Alpine).
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038762
[2]: 2030788
But, as a consideration for users wanting to verify their password, add a 2s dwell time before the characters are masked. This timeout is prematurely terminated in the event that you enter another key.
Using onTextEdited meant that the clear() call would happen after the edit had actually happened.
Instead, use the Keys.onPressed handler, which happens earlier in the input chain.
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
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
This used to be attached to the ComboBox for selecting whether you
wanted the customization options to be applied only for this session, or
stored for re-use.
As we've removed that option, we should also remove the label string.
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.
Per a request from the Raspberry Pi Communications team, change
'Advanced Settings' and 'Image customization' to read 'OS
customization'.
This is to avoid amibuguity in the English, where Image_r_ and Image may
be conflated when reading at speed.
Regrettably, this breaks the existing translations. To prevent
confusion, explicitly delete the existing translations - as they're almost
certainly not valid with the reworded meaning.
This reverts commit 2fb58dc01c.
The original commit included an unexpected deletion of _all_
translations in certain languages. This was unintented, and appears to
have been a merging artefact.
This change will be re-submitted as a separate PR.
In addition to replacing Qt5 with Qt6 in CMakeLists.txt
two small changes to the code are needed to make things build
on Qt 6 (which in turn is needed for Apple M1/M2 support).
The cost of this change is that when building on Qt 5, at least
version 5.14 is needed.
Certain older but still used Linux distributions such as
Ubuntu 10.04 LTS still use 5.12, so revert this commit if you
are building on those...
- Reduce platform specific code in ImageWriter class,
and move that to seperate classes.
- Use API calls to get current SSID on Windows and Linux instead
of launching command line utilities.
Instead of using 'pi' as default, try to get the username of
the current user from the OS.
May not always work. (e.g. some Windows users may not have
setup a username themselves, but may be using a default user
created by the PC vendor).
Closes#497
In the "advanced settings" dialog, if "X" instead of
"apply settings" is clicked, it is seen as "cancel" and
no settings are applied.
If there do are saved settings, make sure to ask the
user on pressing "write" if they do want the saved settings
applied, instead of applying no settings.
Implemented as "validator" which will cause that if an user
presses a key that is not allowed, it will not register.
Saves having to add an error message that would need to be
translated to different languages.
Closes#474
