[Ezekiel000]

That would be the ideal solution but the way things are at the moment it seems that the order items are displayed is tied to the way the library database is stored as this change doesn't actually come into effect until you rebuild your library. So some reworking of the way ngale reads or writes the database would need to be done before it could be an option that could be toggled.

Also if you have a library database built with this change in place and then switch to a vanilla ngale the order of all current items in the library will stay the same but new items added will be added in the vanilla ngale order.

Hmm, I'm not sure if I explained that clearly. Let me know if it sound like gibberish to you.

[johnmurrayvi]

I looked at this a few nights ago and was wondering how this issue could be solved...
Getting the sort option in there would be pretty easy, and a pref could easily control that. I wonder if the pref could make the app restart, triggering some function which dumps the database to a temp file, makes the change, then uses the temp file?

Just a shot in the dark, SQL is fairly new to me..

[ilikenwf]

We could maybe find a way to do it without doing a whole lot. Maybe a view that pivots things the way we need them.

[rsjtdrjgfuzkfg]

(07-11-2013, 03:03 AM)johnmurrayvi Wrote: I looked at this a few nights ago and was wondering how this issue could be solved...
Getting the sort option in there would be pretty easy, and a pref could easily control that. I wonder if the pref could make the app restart, triggering some function which dumps the database to a temp file, makes the change, then uses the temp file?

Just a shot in the dark, SQL is fairly new to me..

I'm for creating indices for both orders, and then simply making the queries customizeable. If we're using plain SQL that should work.