AccountWizard: add option to configure default crypto behaviour for new identity
ClosedPublic

Authored by dvratil on Jul 21 2016, 11:08 AM.

Details

Summary

As we now have per-identity auto-sign and auto-encrypt configuration,
users can now choose if they want to enable them when creating a new
account.

Diff Detail

Lint
Lint Skipped
Unit
Unit Tests Skipped
dvratil updated this revision to Diff 5388.Jul 21 2016, 11:08 AM
dvratil retitled this revision from to AccountWizard: add option to configure default crypto behaviour for new identity.
dvratil updated this object.
dvratil edited the test plan for this revision. (Show Details)
dvratil added a reviewer: KDE PIM.
dvratil set the repository for this revision to R43 KDE PIM.
dvratil added a project: KDE PIM.
dvratil added subscribers: mlaurent, aheinecke.
Restricted Application added a subscriber: kde-pim. · View Herald TranscriptJul 21 2016, 11:08 AM
knauss added a subscriber: knauss.Jul 21 2016, 2:15 PM
knauss added inline comments.
accountwizard/src/personaldatapage.cpp
121 ↗(On Diff #5388)

create a enum for the states

dvratil updated this revision to Diff 5414.Jul 22 2016, 9:26 AM
dvratil removed R43 KDE PIM as the repository for this revision.
dvratil updated this revision to Diff 5417.Jul 22 2016, 9:32 AM
knauss added inline comments.Jul 22 2016, 10:50 AM
accountwizard/src/personaldatapage.cpp
4 ↗(On Diff #5388)

shouldn't we move the enum to the file namespace? So also other methods can use it?

I would suggest to create a method aka:

CryptoState PersonalDataPage::cryptoState() const{
         return static_cast<CryptoState>(ui.cryptoComboBox->currentIndex());
}

@knauss shouldn't we move the enum to the file namespace? So also other methods can use it?

It's only relevant for the internal mapping here, nowhere else, there are no users outside and this is not public API anyway, so I don't see any point in that....

@knauss shouldn't we move the enum to the file namespace? So also other methods can use it?

It's only relevant for the internal mapping here, nowhere else, there are no users outside and this is not public API anyway, so I don't see any point in that....

thats a good point, so let's leave this internal in the function.

This revision was automatically updated to reflect the committed changes.