Quote from: Aethereal on Today at 08:59:30 AM

The creation process still throws a warning about "No crontrol passphrase" for the global protection but now the single wallet created is correctly encrypted with the set password.

Updated the verbose to be more specific about what's happening.

Quote

a- previously created wallet now are listed as not encrypted and the new ones are listed as encrypted in the Available Wallets grid

The private keys are encrypted nonetheless. You're running into a GUI quirk. It parses the used address data to determine encryption state and a fresh wallet that never went online has no provable used addresses, so there is nothing to parse, hence the issue on fresh wallets. Get one address from the wallet, reload Armory and it should show as encrypted. I have to use a better heuristic for this...

As for the new wallets you made showing as encrypted, I've had the creation process put the first address in use to avoid the quirk. Again, I have to think of something better.

Quote

b- when asked to make a paper backup during the creation phase, I'm asked again (for a fouth time) the password to unlock it

Will fix.

Quote

he wizard window is enlarged to accomodate the card pictures

This is really wonky atm, made somehow even worse on Hyprland. Probably something to do with qtpy and/or qt5/6, I'll get to it eventually.

Quote

When creating a new wallet, hitting the "print" button during the "print single sheer paper backup" phase throws an error

Ah, I completely ignored that, we'll see what I can do.

Quote

Since the wallet property window buttons aren't yet working, I couldn't test if the error is specific to the creation flow or is present also on on-demand wallet backup.

Next commit will add unlock testing, should be within the hour of writing this.