On Monday April 11 2016 09:44:26 Martin Sandsmark wrote:
Morning,
It seems I was a bit confused. I posted this question because I had to
introduce a new patch to force the use of IniFormat, but that was not in Sonnet
itself but for some new setting in KTextWidgets :-/
Same question/principle a
Hi!
On Sun, Apr 10, 2016 at 07:33:38PM +0200, David Faure wrote:
> Hmm we already care for backwards compatibility on Windows and OSX ?
Well, we shouldn't? Sonnet is at least used by Quassel on Windows AFAIK, and
probably (hopefully) others. But if you don't think it is something that we
need to
Hi!
On Sun, Apr 10, 2016 at 11:23:58AM +0200, David Faure wrote:
> On Friday 01 April 2016 15:03:10 René J. V. Bertin wrote:
> > Wasn't it decided a while ago (5.16.0 or so) that frameworks would use
> > QSettings::IniFormat and not QSettings::NativeFormat unless they had a very
> > good
> > re
On Sunday 10 April 2016 18:50:00 Martin Sandsmark wrote:
> Hi!
>
> On Sun, Apr 10, 2016 at 11:23:58AM +0200, David Faure wrote:
> > On Friday 01 April 2016 15:03:10 René J. V. Bertin wrote:
> > > Wasn't it decided a while ago (5.16.0 or so) that frameworks would use
> > > QSettings::IniFormat and
On Friday 01 April 2016 15:03:10 René J. V. Bertin wrote:
> Hi,
>
> Wasn't it decided a while ago (5.16.0 or so) that frameworks would use
> QSettings::IniFormat and not QSettings::NativeFormat unless they had a very
> good
> reason, in order to have the same file format across platforms and av
Hi,
Wasn't it decided a while ago (5.16.0 or so) that frameworks would use
QSettings::IniFormat and not QSettings::NativeFormat unless they had a very
good
reason, in order to have the same file format across platforms and avoid
storing
things in the registry under MS Windows?
R.
__
