I make an project where user can create application for by dropping elements inside itemscontrol, also there is a "group field" control (itemscontrol with a label) which can hold other elements. When I'm trying to drop element inside group field, it drops element both to main and group field item controls. Looks like group field is passing drop event to main items control. How can I solve this problem?My actions
Related
Similar threads:
How can I know when a value is "re-selected" in a ComboBox?
What event handler to use for ComboBox Item Selected (Selected Item not necessarily changed)
I am using Infragistics UltraComobEditor to show some values by filling it's ValueList property with items. The selected item is just like a template and it require to update all elements which are using that template.
To apply it again i need to fire it's SelectionChangeCommitted event, but it does not fire if item is already selected.
I am in the quest to find the drop down list element which was selected before the DropDownClosed event fire. Is there any way to get which element was selected or get the element under the mouse point after the DropDown event?
If I setup a lookup for a field when designing a table (i.e. through the Lookup Wizard) and I set "Allow Multiple Values" to "Yes", a multi-select combobox (i.e. with check-boxes) is displayed in the relevant field in the "Datasheet" view of the table. My question is the following: Is the text-box component of a multi-select combobox control actually of any use? While a single-select combobox lets you type a new value that is not in the list or facilitates the auto-complete feature when typing a value that is included in the list, but the multi-select combo box prevents you from typing anything in its textbox, and that behavior doesn't seem to change via the properties of the combobox control.
The reason I need this feature is because I want to type there something not in the list, in order to trigger the control's NotInList event, so that I can update the corresponding lookup table with the new value I typed.
Thanks
I'm trying to create an effect similar to the one used in the default email client on Windows phone. When a user taps the very left of a single listbox item, checkboxes appear to the left of all listbox items.
I'd like the appearance of the checkboxes to be fluid (ie requiring FluidLayout).
When I set up two states in a VisualStateGroup within the ItemTemplate of my items, I am unable to transition between states, as calling VisualStateManager.GoToState requires a view-object (for that item) which I don't have.
How do I make checkboxes appear fluidly inside of all items of a ListBox?
I have a tree view with checkboxes bounded to a property by name Ischecked in the corresponding view model,and whose content will be loaded on demand.Now when ever user checks the box,in the Ischecked setter property I add the checked treeview item into another Generic List(When a node is unchecked,It is removed from the List).Now I have two buttons namely select and deselect button.So when user checks different nodes and press select I will update the List box in the same usercontrol with the Generic List that I had previously.
How do I uncheck the corresponing treeview Items when user wants to remove few items from List box.Also am I doing the right way?
I have a Silverlight 4 application that uses multiple tabs. On Tab 1 I allow the user to select items from a grid, right click and select a context menu item that sends the items to a different grid on Tab 2. However, if the user has not clicked on Tab 2 yet, the grid I am trying to add items to does not exist yet.
What is the most elegant way to make sure that all objects on the second grid are instantiated even if the user has not selected the tab yet?
Thanks,
-Scott
Assuming you are adding items to data grid of some sort then the way to go is to add your items to an ObservableCollection and then data bind the grid to the collection.
That way you don't have to worry about whether the grid is actually visible or not and it will update itself when it does become visible.
Instead of trying to prepopulate the grid on tab2 with data that does not yet exist, you could use the MVVM pattern.
Tab1 could be view1 of viewModel1. Tab2 could be view2 for viewModel2. When view1 updates viewModel1, ViewModel1 updates ViewModel2, which, in turn, updates view2. Then, you only need to set bindings for the visibility, isEnabled, and ItemsSource properties.