Closed GoogleCodeExporter closed 9 years ago
Hi,
this feature has been implemented to ensure the sorting order you specified in
the movieset view will be stored to the NFO (as described in
http://wiki.xbmc.org/index.php?title=NFO_files/movies#Movie_sets).
Where do you see a problem with this feature?
Kind regards,
Manuel
Original comment by manuel.l...@gmail.com
on 24 Jun 2013 at 8:29
This is a great feature to have as I use it extensively. The problem is that it
is a locked field. This creates problems if you are trying to add titles later
since the ordering occurs when you assign it to a set. Or create a unique set
such as a collection of movies, such as Disney movies. I would like to modify
the sort title.
ie.
Lord of the Rings 1, 2, 3...
Assigned, LOTR1, LOTR2, LOTR3
Now the Hobbit comes out and I want to assign it to the set.
It becomes LOTR4, when I would want it to be listed first.
Original comment by Seawa...@gmail.com
on 24 Jun 2013 at 4:50
You know, that you can change the order of movies inside the movieset? Go to
the movieset panel, edit the movieset and there are UP/DOWN buttons beside the
movie table.
I thought it would be more failsafe, if I lock the sorttitle ;)
Original comment by manuel.l...@gmail.com
on 24 Jun 2013 at 5:34
I tried to get this to work, but this is problematic when using a movieset that
doesnt exist or when it is a big collection, the order is not consistent. I
added all titles to the list in alphabetical order and it will show correctly
in the main screen, but when I look at the ordering in the edit panel, they
arent correctly.
See screenshots for example. Even when i try to change the sort order by
editing using the up/down, they dont display in that order and it makes it hard
to know what is what.
Original comment by Seawa...@gmail.com
on 30 Jun 2013 at 3:07
Attachments:
could you try restarting tmm and have a look if they are sorted right after the
restart?
Original comment by manuel.l...@gmail.com
on 30 Jun 2013 at 4:41
I've just reproduced this issue: looks like a UI display issue. After
restarting the order seems to be right.
Original comment by manuel.l...@gmail.com
on 30 Jun 2013 at 5:00
fixed the (optical) sort order with r694
Original comment by manuel.l...@gmail.com
on 30 Jun 2013 at 6:32
Original issue reported on code.google.com by
Seawa...@gmail.com
on 21 Jun 2013 at 3:55