From: Mike J. <mrj...@mi...> - 2008-01-11 15:13:49
|
heya, On Fri, 2008-01-11 at 08:53 +0100, Petr Vanek wrote: > You can theoretically use item based widgets at all. But it is heavy-footed > for coding. > Move to MVC widgets is a good choice. it's cleaner, that's for sure. at the time i just wanted to get the thing ported and it became very clear that using qtreewidget wasn't going to do everything we wanted... > BTW is there any reason why is toQValue used over new Qt4 QValue at all? lol, i'm glad you noticed that. it originally was a list of QVariants. two reasons really, one was that i can put custom types in toqvalue. it gives me a little more flexibility so i can keep what originally came from the database separate from what's displayed. and i don't have to convert it to something qt understands before i need to. then i also had a lot of problems figuring out the type stored in qvariant. toqvalue has nice methods isInt, isDouble that only return true if that was the original type stored. qvariant only provides canConvert<double>(), which returns true for just about everthing i tried. it took me a while to figure out why my sorts were all out of whack on a timestamp column, it was because the value was getting converted to a double then sorted on. (query class returns that as a string.) > heh, congrats. And I wish you perfect emplouyer and good job without army > drill ;) lol, thanks. i just heard though that there was a screwup in hr so i'll be starting on the 22nd. oh, well... more time to hack on tora, right? :-) |