now QSettings will behave much like opening a file via open() and the like,
see the QFile hijack test case
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
I am not interested in custom types feature at all - QMainWindow for
example saves its state via QDataStream. ofcourse it involves conversion
but that is the case with QVariant aswell. there is also the qreal type
thing - it may be float, it may double. streaming QRectF has to be done
in such a way to account for both cases but here is the catch - if
conversion fails there has to be fallback which QSettings::value() kinda
covers for types that are not composed of several more types.
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
this is mostly automated change set, a lot to be done later on
especially about the definitions in core component. the goal is
to make most of the options of the core component available so
that they can be utilized in other components and tools without
restrictions as shown by some of the changes done to the GUI
component in this commit
Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
