Custom template broken with latest SP

3 posts, 0 answers
  1. hwsoderlund
    hwsoderlund avatar
    419 posts
    Member since:
    Aug 2006

    Posted 19 Aug 2010 Link to this post

    Hi, we had made a custom style/template for the RadTreeListView component, and after we upgraded to the latest SP, the expander button lost its pretty face and was replaced by some new default style. Please take a look at the attached screen shots. They show the expander button before and after the update. I am not a designer myself, and the guy who did the design is not assigned to the project anymore. Can you help me out here?

    Best regards,
    /Henrik
  2. Kalin Milanov
    Admin
    Kalin Milanov avatar
    447 posts

    Posted 23 Aug 2010 Link to this post

    Hello hwsoderlund,

    Indeed we did introduce a minor change in the toggle button and this might have affected your project. That being said, I would gladly provide you with the assistance you need if you could send me a sample illustrating your issue so I can apply the changes needed to get your pretty expander back. 

    Greetings,
    Kalin Milanov
    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. hwsoderlund
    hwsoderlund avatar
    419 posts
    Member since:
    Aug 2006

    Posted 23 Aug 2010 Link to this post

    Thank you, but I managed to solve it myself. And I learned a few things about Blend on the way, so no harm done. :)

    I have to say though, that when building custom styles for 3rd party controls (and some of us do that a lot) it becomes a problem when the templates/styles change from one version to another. Of course I understand that it is not possible to always be backwards compatible, but maybe you could include significant template changes in the list of breaking changes? For me as a developer a situation like this is no big deal, especially since the functionality worked perfectly even with the updated button. But it is exactly the kind of problem that can send a troublesome client through the roof. Many of our clients would view it as a breaking change if the big, shiny button that they wanted so much (and sometimes even paid extra for) was suddenly replaced by a small grey plus/minus sign. So to conclude this little rant, if you could think of a way to let us know beforehand which templates have changed enough that they might break things, that would be great.

    Best regards,
    /Henrik
Back to Top