Closed GoogleCodeExporter closed 9 years ago
So basically this would load the images in the facade asynchronously and at a
higher
resolution. Higher resolution coming into play for things like filmstrip view
or large
thumbnail view.
I think this is a good idea, but I also think this will be non-trivial.
Although we
might be able to base some of the logic off of TV-Series code.
Original comment by conrad.john
on 4 Dec 2009 at 4:51
hi, i will love to see this issue get higher priority , the quality of the
cover in filmstrip is rally worse , and you can see it if you comper my tv
seires plugin filmstrip view with moving pictures filmstrip view ,
thanks,
Original comment by ysm...@gmail.com
on 15 Oct 2010 at 3:43
Original comment by conrad.john
on 31 Jan 2011 at 1:22
Some discussion here: http://bit.ly/l0udvM
Going to reschedule this for 1.3 as this causes some problems with high
resolution skins that prominently display artwork using something like
CoverFlow.
Original comment by conrad.john
on 29 Jun 2011 at 3:00
Attached is a patch that allows the user to set the width of the thumbnails in
advanced settings (located under Tweaks).
You have to delete the cover thumbs (ProgramData\Team
MediaPortal\MediaPortal\thumbs\MovingPictures\Covers\Thumbs) when changing this
value. New thumbs will be created on plugin start.
Original comment by ncohrt@googlemail.com
on 1 Jul 2011 at 8:26
Attachments:
Thanks ncohrt! Going to pull this up to 1.1.5 since this looks like a fairly
stable solution.
Original comment by conrad.john
on 1 Jul 2011 at 2:07
Attached is a fixed version of the patch above. I forgot one file...sorry
Original comment by ncohrt@googlemail.com
on 3 Jul 2011 at 10:09
Attachments:
Applied your patch (with a tiny bit of cleanup) in r1320. Thanks a ton nchort!
I have opened Issue #1038 for a possible user interface on the main config
panel to make this more accessible to the common user. Please direct
conversation regarding user interaction over there.
Original comment by conrad.john
on 30 Jul 2011 at 3:58
Original issue reported on code.google.com by
damien.haynes@gmail.com
on 4 Dec 2009 at 6:04