Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It sounds like you're looking for a "codeless" MVVMish way of handling the KeyUp/KeyPress/KeyDown event.</p> <p><strong>Option #1: Prism.</strong><br> You've mentioned it only <strong>ships</strong> with the Click command. However, you can add your own attached DPs to enable commands for whatever event you'd like (like KeyUp/KeyDown/KeyPress). </p> <p>If you're looking for a sample on that Corey has a good one for ToggleButton.Checked/Unchecked events.<br> <a href="http://www.85turns.com/2009/06/24/togglebutton-command-for-prism/" rel="noreferrer">http://www.85turns.com/2009/06/24/togglebutton-command-for-prism/</a> </p> <pre><code>&lt;ToggleButton x:Name="ToggleButton1" customCommands:Checked.Command="{Binding CheckedCommand}" customCommands:UnChecked.Command="{Binding UnCheckedCommand}" Margin="8,8,0,8" Content="Check me" /&gt; </code></pre> <p>Also, Erik Mork has an excellent video that gives you a good overview on commands and how to create a custom command Attached DP. <a href="http://development-guides.silverbaylabs.org/Video/Prism-Commands" rel="noreferrer">http://development-guides.silverbaylabs.org/Video/Prism-Commands</a></p> <p><strong>Option #2: Blend Triggers</strong><br> The Expression Blend SDK ships with Triggers and Behaviours that are spot on to what you're try to do.<br> <a href="http://expressionblend.codeplex.com/" rel="noreferrer">Blend Examples</a> codeplex project ships with a EventTrigger you could use: </p> <pre><code>&lt;i:EventTrigger EventName="Click"&gt; &lt;si:InvokeDataCommand Command="{Binding ShoppingCart.CheckOutCommand}"/&gt; &lt;/i:EventTrigger&gt; </code></pre> <p>Or, you could create your own custom Trigger for Key stroke events and do there whatever you'd like. Here's a sample:<br> <a href="http://azurecoding.net/blogs/brownie/archive/2009/04/06/blend-behaviors-ftw.aspx" rel="noreferrer">http://azurecoding.net/blogs/brownie/archive/2009/04/06/blend-behaviors-ftw.aspx</a> </p>
    singulars
    1. This table or related slice is empty.
    1. POHotkey commands for Silverlight in MVVM?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJustinAngel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHotkey commands for Silverlight in MVVM?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI second Justin's response. I have created a KeyDown/KeyUp command attachment using Option #2 and I handle PageUp/PageDown and other hot keys in my SL app. It works really well. I pass the key code in through the command parameter, so my command can handle the key codes proprly. It is a good idea to create a mass of these attached commands. They are simple to write, and easy to use anywhere you need them.
      singulars
      1. PO
      1. USBrian Genisio
    2. COAs for Option #1: The Prism model works well for events that need no additional information, but breaks down if you want to have variations of that same event, like different keys on KeyDown. Its implementation relies on only one attached property per element, but for handling hotkeys you will want multiple attached properties on the same element. The attached property behavior implementation does not allow this. Option #2/Brian: Ideally wouldn't you want the hotkeys to be specified in the view, rather than in the command implementation?
      singulars
      1. PO
      1. USRandomEngy
    3. COI really like that blend behavior sample. That's one smart guy there ;)
      singulars
      1. PO
      1. USMichael Brown
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload