Re: [Development] QSettings refactor updates

2014-10-11 Thread Milian Wolff
On Saturday 11 October 2014 11:39:40 Tomaz Canabrava wrote: > Em 11/10/2014 11:35, "Thiago Macieira" escreveu: > > On Saturday 11 October 2014 09:01:52 Tomaz Canabrava wrote: > > > True, I dont need it to make things work, but I need it in case I wanna > > > show them inside a qtreeview. > > > >

Re: [Development] QSettings refactor updates

2014-10-11 Thread Milian Wolff
On Friday 10 October 2014 21:26:11 Tomaz Canabrava wrote: > On Fri, Oct 10, 2014 at 6:35 AM, Milian Wolff wrote: > > On Friday 10 October 2014 06:22:12 Tomaz Canabrava wrote: > > > Em 10/10/2014 06:18, "Oswald Buddenhagen" < > > > > > > oswald.buddenha...@theqtcompany.com> escreveu: > > > > On Fr

Re: [Development] QSettings refactor updates

2014-10-11 Thread Tomaz Canabrava
Em 11/10/2014 11:35, "Thiago Macieira" escreveu: > > On Saturday 11 October 2014 09:01:52 Tomaz Canabrava wrote: > > True, I dont need it to make things work, but I need it in case I wanna > > show them inside a qtreeview. > > > > I can split it into a QConfigTrreModel if you think its the way to

Re: [Development] QSettings refactor updates

2014-10-11 Thread Thiago Macieira
On Saturday 11 October 2014 09:01:52 Tomaz Canabrava wrote: > True, I dont need it to make things work, but I need it in case I wanna > show them inside a qtreeview. > > I can split it into a QConfigTrreModel if you think its the way to go. The > rationale is just to provide a quick way to have a

Re: [Development] QSettings refactor updates

2014-10-11 Thread Tomaz Canabrava
Em 11/10/2014 09:20, "Rafael Roquetto" escreveu: > > On Fri, Oct 10, 2014 at 09:26:11PM -0300, Tomaz Canabrava wrote: > > On Fri, Oct 10, 2014 at 6:35 AM, Milian Wolff wrote: > > > > > > > It's too error prone regarding typos. > > This is easily solved by using constants instead of string litera

Re: [Development] QSettings refactor updates

2014-10-11 Thread Rafael Roquetto
On Fri, Oct 10, 2014 at 09:26:11PM -0300, Tomaz Canabrava wrote: > On Fri, Oct 10, 2014 at 6:35 AM, Milian Wolff wrote: > > > It's too error prone regarding typos. This is easily solved by using constants instead of string literals. const QLatin1String SettingsGroup("blah"); const QLatin1St

Re: [Development] QSettings refactor updates

2014-10-11 Thread Tomaz Canabrava
Em 11/10/2014 05:24, "Thiago Macieira" escreveu: > > On Friday 10 October 2014 21:22:34 Tomaz Canabrava wrote: > > Yes - the QConfig is actually a QAbstractTableModel already. > > Sorry, can you explain this a little more? > > A Model is a standardised way for the Views classes to access a storage

Re: [Development] Building Qt 5 in release mode with debug symbols

2014-10-11 Thread Sean Harmer
On 10/10/2014 10:49, Milian Wolff wrote: > On Friday 10 October 2014 11:39:33 Milian Wolff wrote: >> Hello all, >> >> once more I'm preparing a Qt 5 build for profiling purposes and wonder again >> why there is no way to combine -release and -debug in Qt's configure >> script. The only way to get a

Re: [Development] QSettings refactor updates

2014-10-11 Thread Thiago Macieira
On Friday 10 October 2014 21:27:58 Tomaz Canabrava wrote: > I tougth about having a changed() signal on the QConfig / QConfigGroup > classes, is the QConfigWatcher a better approach? Put it in a separate class. QConfig (Group) should not be a QObject. -- Thiago Macieira - thiago.macieira (AT) in

Re: [Development] QSettings refactor updates

2014-10-11 Thread Thiago Macieira
On Friday 10 October 2014 21:22:34 Tomaz Canabrava wrote: > Yes - the QConfig is actually a QAbstractTableModel already. Sorry, can you explain this a little more? A Model is a standardised way for the Views classes to access a storage that exists elsewhere. You don't need to use QAbstractTableM