When no more directory entries are available in the existing
cluster(s) of a directory on FAT32, we allocate an
extra cluster.
Make sure to zero out that new cluster, as disk checking utilities
may not stop reading when reaching an end of directory marker but
read the rest of cluster as well.
So there must not be any garbage data from a previously deleted file
in the sector there.
Also add checks to prevent getting in an endless loop on
encoutering circular "next cluster" references.
- No longer relies on operating system for mounting FAT partition
when applying 'advanced settings'
- change '__attribute__ ((packed))' to '#pragma pack()' as the
mingw version we are using for Windows has a bug with the former
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
Only supported when NetworkManager is used on the Linux distro
as wpa_supplicant itself does not support reading PSKs through
DBus, only setting them.
Closes#457
- Fix advanced settings not working if users has wifi settings saved
with previous version of Imager, and user selected "use always"
Ref #343
- Also fix problem where "SSH enabled" is not saved on Mac OS X due
to the check assuming QSettings stores settings as strings, while
with the plist stuff on Mac OS X it is stored as boolean.
Fixes "Can't assign to existing role 'subitems' of different type"
or hang (depending on Qt version) on using nested subitems.
Keep nested subitems flattenend as json string in memory while not
being used, to simplify dealing with ListElement expectation that
all elements have the same data type, as well as QML/Ecmascript's
memory management.
ON LINUX PLATFORM ONLY
Allow NVMe destination drives as long as they are not mounted
except under /media
This does increase the risk of someone accidently selecting an
internal NVMe drive that is not mounted under the current OS
(Linux) but do is being used by the other operating system
(e.g. Windows) on dual boot systems.
But is deemed to be an acceptable risk.
Ref #158
