Very cool, reminds me of 1.4.x days... :) In the current implementation I was looking to see if there was a way to reset the model on the third QHeaderView header click(ascending, decending, unsorted), never found one, not sure if that still applies coming from the SQL model though. I'll have to remember look at that again one of these days.
If the "smart" sorting of null/crap doesn't work in the new setup, let me know and I'll try to port it to SQL. -G On 11/15/08, Albert Santoni <[EMAIL PROTECTED]> wrote: > Just another quick update. Started playing around with QSplitter to > add a view of the "track sources" (eg. library, playlists, blah) to > the UI: > > http://picsharp.com/images/0b3gt1qam2vukhzf3fo.png > > I also discovered a few days ago that the QHeaderView class, which > corresponds to the column headers in our new track table has these > "saveState()" and "restoreState()" functions, which allow us to > serialize it's column positions/sizes and sorting to a QByteArray. > That means it'll hopefully be trivial for me to make all that stuff > auto-save. I think that's been a feature request for ages. :) > > Albert > > On 13-Nov-08, at 4:14 AM, Ben Wheeler wrote: > >> On Mon, Nov 10, 2008 at 11:28:10PM -0800, Albert Santoni wrote: >>> I've been plugging away at the library rewrite for a while now, and >>> I've >>> got parts of the basic library functionality reimplemented. >> >> I'm in awe of the amount of hard and good work you put into the >> "un-sexy" jobs that no-one else wants to do! Kudos, kudos. >> >> >>> My final thought is that the new library is a double-edged sword. >>> I've >>> been motivated to rewrite the code because of the sheer number of >>> library related bugs that have come into the tracker after 1.6.0, >>> most >>> of which are getting increasingly hard to fix because of >>> architectural >>> issues with the old code. The problem is that now I'm not going to >>> fix >>> any of those old bugs in trunk, instead I'm devoting that time to the >>> new code. The new library code definitely won't be ready for 1.6.2, >>> so >>> the library bugs in 1.6.1 will remain. >> >> I think that's fair enough. There comes a point where time spent >> fathoming and fixing bugs becomes wasteful (and even less "sexy" >> than fixing the core of the problem by redeveloping the architecture). >> One of the rules of open source innit: be prepared to "throw one >> away". >> >> Anyway, just wanted to big you up for the work. :) >> >> One of these days I'll actually get on with the very minor >> task of hooking up the DJM-800 for MIDI control... but, happy to say, >> I have very little spare time at the moment because I'm too busy >> DJing :) >> >> Ben >> > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Mixxx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > -- Sent from Gmail for mobile | mobile.google.com __ --- == __/ t.O ==-- http://stacktrace.org/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
