diff options
| author | Andre Heinecke <[email protected]> | 2017-05-10 08:22:23 +0000 |
|---|---|---|
| committer | Andre Heinecke <[email protected]> | 2017-05-10 08:22:23 +0000 |
| commit | cc2ef3d07c0d261bb9e8e8c0f2706e1a08e4ec53 (patch) | |
| tree | ce5c04a5e43642a2726330de024627849580d4ca /lang/qt/src/qgpgmenewcryptoconfig.cpp | |
| parent | qt, tests: Don't use internal API (diff) | |
| download | gpgme-cc2ef3d07c0d261bb9e8e8c0f2706e1a08e4ec53.tar.gz gpgme-cc2ef3d07c0d261bb9e8e8c0f2706e1a08e4ec53.zip | |
qt: Undeprecate API that I find useful
* lang/qt/src/decryptjob.h,
lang/qt/src/decryptverifyjob.h,
lang/qt/src/signencryptjob.h,
lang/qt/src/verifydetachedjob.h,
lang/qt/src/verifyopaquejob.h: Undeprecate ByteArray based API.
--
While an IODevice may be more performant the ByteArray API is
a very easy way to get started with QGpgME as it allows you
basically to encrypt / decrypt any QString.
This also fixes a ton of deprecation warnings in KDE where this
API is used all over the place.
Diffstat (limited to 'lang/qt/src/qgpgmenewcryptoconfig.cpp')
0 files changed, 0 insertions, 0 deletions