Re: WPF Code Creation of input Binding - WPF Discussion Boards

Re: WPF Code Creation of input Binding

9-Jun-11 0:32

I would like to know how to implement the following xaml in code, specifically the input binding to a command.

<Controls:TextBox Text="{Binding Path=SearchText, UpdateSourceTrigger=PropertyChanged}">
    <Controls:TextBox.InputBindings>
        <KeyBinding Key="Return" Command="{Binding Path=SearchCommand}"/>
    </Controls:TextBox.InputBindings>
</Controls:TextBox>

The reason for the question is i am looking to inherit from some of the default windows controls, and have some standard behaviour for my inherited control. I wish for the return and escape keys to execute a commands in my ViewModel which will be the DataContext for the Inherited Control. The return key would trigger a search to be performed, and the escape key would clear the control to its default value, any help would be greatly appreciated.

SledgeHammer019-Jun-11 6:49

SledgeHammer01

9-Jun-11 6:49

Sounds like the perfect use for attached behaviors! Big Grin | :-D

Re: WPF Code Creation of input Binding

Ed Hill _5_9-Jun-11 22:17

Re: WPF Code Creation of input Binding

9-Jun-11 22:17

The following appears to impelemtn what you suggested, to be honest i'm not sure that i understand the need/benifit to use an attached behaviour insted of inheriting from a control.

public static class LookupBehaviour
{
    public static Boolean? GetEscapeToClear(ComboBox comboBox)
    {
        return (Boolean?) comboBox.GetValue(EscapeToClearProperty);
    }
    public static void SetEscapeToClear(ComboBox comboBox, Boolean? value)
    {
        comboBox.SetValue(EscapeToClearProperty, value);
    }

    public static readonly DependencyProperty EscapeToClearProperty = DependencyProperty.Register("EascapeToClear",
                                                                                                  typeof (Boolean?),
                                                                                                  typeof (LookupBehaviour),
                                                                                                  new UIPropertyMetadata(null, OnEscapeToCearChanged));

    private static void OnEscapeToCearChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
    {
        if (!(d is ComboBox)) return;
        var cmb = d as ComboBox;
        if ((e.NewValue is Boolean?) && (e.NewValue as Boolean?).HasValue)
        {
            var escapeBindingCommand = new KeyBinding(ApplicationCommands.NotACommand, new KeyGesture(Key.Escape));
            var escapeBidning = new Binding("EscapeCommand");
            BindingOperations.SetBinding(escapeBindingCommand, InputBinding.CommandProperty, escapeBidning);
            cmb.InputBindings.Add(escapeBindingCommand);
        }
    }
}

One thing that i didn't like was when creating the key binding that you have to specify a tempory command, ApplicationCommands.NotACommand, and then bind over the top of it, if there is any way to avoid that please let me know. Thanks for the origional reply.

SledgeHammer0110-Jun-11 5:05

SledgeHammer01

10-Jun-11 5:05

From your original post, it sounded like you wanted to add the same exact functionality to several different controls. If that was/is the case, then think about it: Its easier to write ONE attached behavior vs a bunch of MyComboBox, a MyButton, a MyCheckBox, etc controls and C&P the code.

The behavior you wrote is hard coded to the ComboBox, but it doesn't have to be hard coded to any specific control type, it can be much more generic. Then you can simply attach it to any control you like. Think of something like a tooltip control. By using attached behaviors, you could attach the tooltip to any control you like.

In addition, attached behaviors allow you to modify a controls' behavior without re-templating an entire parent control just to change an embedded control type. I.e. say you had a data grid and wanted to change the behavior on a ComboBox deep down in the visual tree. You'd have to re-template the entire data grid just to change a <ComboBox /> to a <MyComboBox />.

In regards to your last question, there is no need to create a temporary command and use InputBindings. Just subscribe to the KeyDown message and trap the ESC key.

textbox value

arkiboys8-Jun-11 1:36

arkiboys

8-Jun-11 1:36

In my wpf application, there is a listbox a several textboxes.
On clicking an item in the listbox, the textboxes are populated accordingly.
Do you know why the following happens?
select an item in the listbox.
textboxes are populated with other fields for the selected item. Let's say textbox1 has an empty value.
Type "hello" in the textbox.
select another item from the listbox.
Now in the listbox, select the original item you selected. the textbox has the value "hello".
If application is closed and re-opened then obviously the word "hello" is not there.
Do you see why the value is retained eventhough the data is not saved into the database?
Thanks

Pete O'Hanlon8-Jun-11 1:45

8-Jun-11 1:45

It sounds like you have an underlying data item that you are updating in the view model using two way binding. I can't quite decide from your description what your architecture is, but I do think that you aren't raising a change notification when you should be. If you remember, as we've discussed many, many times, WPF uses the INotifyChanged.PropertyChangedEventHandler to manage the update of bound items, so your code must call the PropertyChangedEventHandler at the appropriate point (and you should tell it which property has changed).

Make sure that the class in the DataContext implements INotifyChanged, and then call the event handler as appropriate. Without seeing any of your code, this is pure guesswork and speculation.

Forgive your enemies - it messes with their heads

My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility

arkiboys8-Jun-11 2:04

arkiboys

8-Jun-11 2:04

Yes, I think I understand or may be not...
May be I did not explain properly the issue.
I have read your comment several times but I still do not see the solution.
To re-cap:
listbox is populated by fullnames from the database.
on selection of each fullname the textboxes are populated i.e. txtaddress, etc...
If a value is changed in the textbox and submit is pressed then the data gets saved into the database BUT if the save button is not clicked and only you click on another fullname, then when you go back to the first fullname, then the textbox value you entered (which you did not save) will be present.
Surely, the value of the textbox should be as same as what is in the database, right?
Thanks

Pete O'Hanlon8-Jun-11 2:09

8-Jun-11 2:09

arkiboys wrote:
Surely, the value of the textbox should be as same as what is in the database,
right?

Not if you've updated it with 2 way binding.

Forgive your enemies - it messes with their heads

My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility

arkiboys8-Jun-11 2:26

arkiboys

8-Jun-11 2:26

I think I figured it out because although I have not placed any mode in textbox xaml, by default it is using twoway mode.
Thanks for pointing that out.

Sparkling_ouc8-Jun-11 22:16

Sparkling_ouc

8-Jun-11 22:16

Common property(Not dependency property) will not be bound with the "TwoWay" Mode(Actually, only special dependency property would, when register dependency property there is an option ).If you want bind it "TwoWay",please implement the interface INotifyPropertyChanged in you "Model" Layer.

Pete O'Hanlon8-Jun-11 2:25

8-Jun-11 2:25

You may need to take a look at IEditableObject and IEditableCollectionView. If you'd like to read the blog and download the code sample here[^], you'll get some idea as to how the transaction support in WPF can help you.

Forgive your enemies - it messes with their heads

My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility

Ed Hill _5_9-Jun-11 0:44

9-Jun-11 0:44

To me this sounds like the correct behaviour, by changing the text you have changed the property in your data context, and although you have not commited this to the database you are not refreshing the data from the database when re selecting the item. If you wish for any changed to be undone if you do not press the save button you may wish to consider calling

ObjectContext.Refresh(RefreshMode.StoreWins, WhatToRefresh);

The WhatToRefresh could be ObjectContext.NamesSourceTable, or to be more graceful you could just pass the previously slected item, i would guess that you call this when you change the slected item on the list. If you need a more full solution post a you code and i'll try to edit it for you.

Pete O'Hanlon9-Jun-11 0:48

9-Jun-11 0:48

Why have you posted this to me? The OP doesn't get notified on replies to other people's comments, and I am more than fully aware of how binding works in WPF/SL.

Forgive your enemies - it messes with their heads

My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility

Ed Hill _5_9-Jun-11 0:50

9-Jun-11 0:50

clicked the wrong reply link by mistake i guess, was simply trying to offer a solution to the OP.

Pete O'Hanlon9-Jun-11 1:04

9-Jun-11 1:04

No problems. Simply add a reply to one of his posts and link to the answer you gave there.

Forgive your enemies - it messes with their heads

My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility

Ed Hill _5_9-Jun-11 5:59