Hi Carl, In silverlight (I presume it's the same in WPF) I try to template an existing control, rather than make my own user control from scratch, so i get all those lovely states wired up to events by default. Usually i template a button. Sometimes a checkbox.
If I need to add other elements that buttons don't have (e.g an icon that is separate to the button label) I wrap the button in a custom control and expose other properties. Then I might need to wire up some of the button's events to visual states in my control using the GotoStateAction behavior. That's how I do it anyway... Dunno if thus helps Shane Shane Morris | Automatic Studio | [email protected] | +61 438 818 888 On 12/10/2011, at 12:18 PM, "[email protected]" <[email protected]> wrote: > > Hi all, > > Has anyone used States on WPF controls in anger? I can’t find any info on > how to use them effectively. > > In my brief foray into them, I added a Button to a window, edited its > template, switched to the States tab in Blend and it’s got some recommended > states prepopulated. Modifying the template and recording into those > states gives the effect I want. So far so good. > > If I go to the states pane on a custom built control it has recommended > states, but not the ones I want (the common states, like mouse over etc). > I try copying the state manager section from the previously styled button, > but these states are missing the magic that binds(?) them up correctly and > don’t work as expected. > > There’s a bit of magic here I don’t quite understand. Can I manually hook > up the common states? Where does the magic happen? > > And finally, is it worth the effort? I’m worried I’ll remove my working > triggers to use states, and get to a point where the states fail and I’ll > have to roll back to using triggers. Any advice? > > Cheers, > Carl. > > Carl Scarlett > Senior .NET/WPF Developer, UX Designer | Genesis > IT & Change Management | Bankwest > A: Level 5, 199 Hay Street | Perth | Western Australia | 6004 > P: (08) 9449 8451 > M: 0408 913 870 > E: [email protected] > > (Embedded image moved to file: pic13385.jpg) > > _______________________________________________________________________________ > Unencrypted electronic mail is not secure and may not be authentic. > If you have any doubts as to the contents please telephone to confirm. > > This electronic transmission including any attachments is intended only > for those to whom it is addressed. It may contain copyright material or > information that is confidential, privileged or exempt from disclosure by law. > Any claim to privilege is not waived or lost by reason of mistaken > transmission > of this information. If you are not the intended recipient you must not > distribute or copy this transmission and should please notify the sender. > Your costs for doing this will be reimbursed by the sender. > > We do not accept liability in connection with computer virus, data corruption, > delay, interruption, unauthorised access or unauthorised amendment. > _______________________________________________________________________________ > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > <pic13385.jpg> > _______________________________________________ > ozwpf mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf _______________________________________________ ozwpf mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
