I suggest you ...

Implement Triggers

It would be really nice if I didn't have to implement an event handler if all I wanted to do was change the visibility of an element.

636 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jack BondJack Bond shared this idea  ·   ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • JacoJaco commented  · 

        I voted for beter interopability between WPF and Silverlight for this feature, but I will vote again. We actually use both silverlight and WPF in our product, and there is a lot of custom controls that we could EASILY share they could add triggers (they were originially created in WPF).

      • geen_olgeen_ol commented  · 

        Why you cannot use view states within VisualStateManager? imho this way is more usable than triggers in WPF

      • dovepandadovepanda commented  · 

        And also DataTrigger and MultiTrigger would be real nice

      • Stefan OlsonStefan Olson commented  · 

        What's even more important than this to me, is the fact that it allows you to share code more easily between WPF and Silverlight.

      Feedback and Knowledge Base