This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
We've started using the Coverflow control to browse business cards in out application. It works nicely except that performance is poor with large collections. Snoop confirms that the control does not do virtualization. We can solve this problem by managing an intermediate collection, but it seems like this logic really ought to be in the control. I see virtualization of this control was mentioned in the forum a few years back, so I was wondering if their might be any change coming. Thanks Peter |
|
|
|
|
Hi Peter, A few years ago I had experimented with building a whole new implementation of the Coverflow control with virtualization, custom paths, more flexible animation and proper 3D (rather than skewing) which works with reflections too. This is probably what was being refered to in the forum posts you found. It was close to being done, but I was never given the time to put it into WPF Elements. It being a total rewrite and so quite a large breaking change also makes it difficult. Not to mention it is one of our free controls (has no licensing so anyone can use it), so had very low priority. I have gotten permission to give away the source code of the improved experimental version of the Coverflow which I hope you will find useful. But there are some catches: I'm not totally sure how complete or bug free it is. The API is quite different to the WPF Elements one - each animatable attribute is controlled by specifying a function. There is no documentation, and it won't get the same level of support/maintenance as it is not part of the WPF Elements product (e.g. no nightly builds). As you'll have all the source code and some example demos, these probably won't be much hindrance. You can also update it however you like. All that said, this is the only way you're going to get a virtualized Coverflow (from us at least), and you should find it is much better than the WPF Elements one overall. Note that this code is not in it's own library, but just slapped together in a demo app. You'll need to pull out the Coverflow code bits to get it working in your app - ideally wrap it up in a library. The app itself should be useful to view the performance and learn how to customize it. It may take a bit of trial and error to get it looking like what you currently have, or maybe you'll be able to make it look better. As for the demo, I had to remove most of the album covers to reduce the size, so add move images to the AlbumCovers folder if you want to see a better demo (the one on page 3). Also, the Pokédex demo on page 1 looks better when the window is resized :) Let me know if it's useful for your app, and if you have any questions getting started. -Jason Fauchelle |
|
|
|
|
Hi Jason, Thanks for providing us with source code for the new version. We will definitely take a look at it. I understand that as a developer you can't do everything you'd like to do and you have to prioritize. Peter |
|
|
|
