diff options
author | Adrian Kummerlaender | 2015-08-12 20:24:52 +0200 |
---|---|---|
committer | Adrian Kummerlaender | 2015-08-12 20:24:52 +0200 |
commit | aca84cb4ef24c1b4b9e3d53126081db8b14855e2 (patch) | |
tree | 6433f9095f51f8681e4d6ef47c94f982e50af5b3 /src/list | |
parent | 900d3255441aff62fe54ba7e57d89d472908d65e (diff) | |
download | MetaTerm-aca84cb4ef24c1b4b9e3d53126081db8b14855e2.tar MetaTerm-aca84cb4ef24c1b4b9e3d53126081db8b14855e2.tar.gz MetaTerm-aca84cb4ef24c1b4b9e3d53126081db8b14855e2.tar.bz2 MetaTerm-aca84cb4ef24c1b4b9e3d53126081db8b14855e2.tar.lz MetaTerm-aca84cb4ef24c1b4b9e3d53126081db8b14855e2.tar.xz MetaTerm-aca84cb4ef24c1b4b9e3d53126081db8b14855e2.tar.zst MetaTerm-aca84cb4ef24c1b4b9e3d53126081db8b14855e2.zip |
Change color setting types to `string`
While `color` would obviously be the correct type to store a color value it is serialized as a `QVariant` value which is not easily changeable by the user.
This requirement is satisfied by `string` and as such this type is - at this point in time - a superior replacement of `color`.
Should the QML settings module be changed to serialize color values in a human readable fashion these types should be changed back to their formally correct value.
Diffstat (limited to 'src/list')
0 files changed, 0 insertions, 0 deletions