CoverFlow support for ICollectionView and ObservableCollection

3 posts, 0 answers
  1. Manuel Felício
    Manuel Felício avatar
    64 posts
    Member since:
    Oct 2009

    Posted 01 Jul 2010 Link to this post

    Hello,

    Did my post about this subject got deleted? Last time I checked I was asking if I could open a support ticket with a trial license and upload a demo app that would reproduce the wierd behavior I'm getting with the CoverFlow control and ICollectionView ItemSources.

    Best regards,

    Manuel Felício.
  2. Nikolay
    Admin
    Nikolay avatar
    3997 posts

    Posted 02 Jul 2010 Link to this post

    Hello Manuel Felício,

    I converted your last post into another type so that you can attach a zip file to it. Please log into your account and go to http://www.telerik.com/account/support-tickets.aspx. There you will see your old ticket, to which you can reply and attach a zip file.

    Regards,
    Nick
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. DevCraft banner
  4. Manuel Felício
    Manuel Felício avatar
    64 posts
    Member since:
    Oct 2009

    Posted 02 Jul 2010 Link to this post

    Hi Nick, I didn't see that before I opened this thread. You may delete this one if you wish. By the way, I'm trying to reproduce the same behavior in a very simple app and so far I haven't been sucessful.. its working very well with PagedCollectionView. In my app, I have my own implementation of ICollectionView. Maybe I'm doing something wrong there..maybe not, but the fact is that RadGridView, SL DataGrid, SL ListBox, SL ItemsControl and beyond all work well with my ICollectionView implementation. I'll try to use that instead of the PagedCollectionView and update the support ticket when its ready.

    Thanks for your support.

    Best regards,

    Manuel Felício.


    Edit: I just updated the support ticket thread and was able to reproduce the issue :)
Back to Top