RoutedUICommand tricks & tips

  • Thread starter Thread starter hbrower
  • Start date Start date
H

hbrower

RoutedUICommands are quite cool. However, I'm struggling with a few issues.
1) the command stops at the first ui element that handles it. Can I
actually override that behavior and proprogate it to all elements that want
to hear about the command.
2) Can I get data about where it happened? For example, if I had a grid
with an 'insert row' command, I need to know where to insert a new row.
Though I haven't seen anything that provides that context. Is there a way to
walk the current focus chain up and down the ui stack? Or is there something
easier?
 
Nothing stops you from 'multi-casting' commands. The command args contain
the data, you can examine those depending on how you have wired up your
commands.

--

Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book, 2nd Edition
Exclusively on www.lulu.com/owc $19.99
 
Back
Top