Re: [SailfishDevel] QSqlTableModel and running several remorses

2016-01-18 Thread jollailija
François K. kirjoitti ma tammikuuta 18 12:35:14 2016 GMT+0200: > > PS: I haven't investigated the proxy approach yet. I'll probably give it a > try in the next few days. > You can see my proxy list implementation from https://github.com/jollailija/nettiradio (fav manager + fav dialog). It's a b

Re: [SailfishDevel] QSqlTableModel and running several remorses

2016-01-18 Thread François K .
Hi, Allright, I've done some further testing and I also read some parts of the QSqlTableModel source code to understand what's going on. I've finally managed to get something working. For people that might be interested in it, I figured out that : - You have to emit the `beginRemoveRows` and

Re: [SailfishDevel] QSqlTableModel and running several remorses

2015-12-30 Thread Peter Kovacs
Hi Francoise, Yeah, sorry about that. I'm not used to working in team and I also avoid variable names that can look like keywords (i.e. "list"). I also always use "r" for the variable that is returned. I see. I use Longer Names to avoid the keywords stuff, like remorseList. IDE will always off

Re: [SailfishDevel] QSqlTableModel and running several remorses

2015-12-30 Thread jollailija
François K. kirjoitti ke joulukuuta 30 00:07:29 2015 GMT+0200: > How would you make such a thing ? Use the destructor of the proxy to update > the database ? The remorse would just delete the item from the QML list model, and then you could have a update timer (to prevent updating the whole lis

Re: [SailfishDevel] QSqlTableModel and running several remorses

2015-12-29 Thread François K .
Hi, Thanks for your input :) > Hi, I am a SQL noob, but here's my piece of advice: > Use a QML list model as a "proxy" and then replace the database with > the QML list model's data at some point, like after the user exits > some sort of list edit mode. It might not be the most efficient way > bu

Re: [SailfishDevel] QSqlTableModel and running several remorses

2015-12-29 Thread François K .
Hi Peter, hi guys, First, thanks for your answer and ideas :) > I find your code a bit hard to read. It would be nice if you use full > names like list instead of l. I know it is annoying, but makes live > easier in the long run. Yeah, sorry about that. I'm not used to working in team and I also

Re: [SailfishDevel] QSqlTableModel and running several remorses

2015-12-28 Thread Peter Kovacs
Hello Francoise, I find your code a bit hard to read. It would be nice if you use full names like list instead of l. I know it is annoying, but makes live easier in the long run. Why do you have more then one Remorse? This is not clear to me. Maybe you can explain? Where do you close your d

Re: [SailfishDevel] QSqlTableModel and running several remorses

2015-12-28 Thread jollailija
Hi, I am a SQL noob, but here's my piece of advice: Use a QML list model as a "proxy" and then replace the database with the QML list model's data at some point, like after the user exits some sort of list edit mode. It might not be the most efficient way but it works and is really easy, you jus

Re: [SailfishDevel] QSqlTableModel and running several remorses

2015-12-28 Thread François K .
Hello, I sent the following email a few weeks ago but got no answer. The github statistics also show that only one person downloaded the "dummy" project I wrote to demonstrate my issue... :( With the recent announcements and the Jolla boat sailing on, I'd like to get this solved. I'm even will