Dependency Properties can be set from many different places; inline, animations, coercion, triggers, etc. As such a Dependency Property Value Precedence list was created and this dictates which changes override which other changes. Because of this order of precedence, we can’t use a Trigger to update a property that is explicitly set inline in your … Read more
The Columns property is not a dependency property, so you can’t bind it. However, it might be possible to create an attached property that you could bind to a collection in your ViewModel. This attached property would then create the columns for you. UPDATE OK, here’s a basic implementation… Attached properties using System.Collections.Generic; using System.Collections.Specialized; … Read more
I struggled with this problem for a while. What worked was to bind the input to an object instead of a primitive. <!– Partial –> <input type=”checkbox” ng-model=”someObject.someProperty”> Check Me! // Controller $scope.someObject.someProperty = false
Instead of responding to several events at the TableCell and TableColumn level to initiate editing of a cell, and successfully update the cell’s underlying data – instead we provide a custom cell factory and override theupdateItem() method in the cell and ‘bind’ the textProperty of the textField directly to the property inside our data model … Read more
This is happening because DataContext=”{Binding PlacementTarget,… binding would set the button as MenuItems DataContext but that won’t add the ContextMenu to the VisualTree of your window and that’s why ElementName binding’s won’t work. A simple workaround to use ElementName bindings is to add this in your Window/UserControl’s code-behind: NameScope.SetNameScope(contextMenuName, NameScope.GetNameScope(this)); Another solution is to do … Read more
Ahhh got you. Now I understand what you mean. You set the Content to null and so you kill the compelte ListBox but still the ItemsSource binds to List and so ListBox memory is not completely released. That is unfortunately a well known issue and also well documented on MSDN. If you are not binding … Read more
Let’s break down what you’re doing. <Image Source=”{Binding ImageSource}” /> For this to work, the binding source needs to be either an ImageSource, or a string representing a URI to an image file. So let’s take a look at what the ImageSource property actually is. public string ImageSource { get; set; } One problem here … Read more
I got it working after much playing around with the various different approaches. In the view: <%string[] PostFeatures = Request.Form.GetValues(“Features”);%> <% foreach (var Feature in (ViewData[“AllPropertyFeatures”] as IEnumerable<MySolution.Models.PropertyFeature>)) { %> <input type=”checkbox” name=”Features” id=”Feature<%=Feature.PropertyFeatureID.ToString()%>” value=”<%=Feature.PropertyFeatureID%>” <%if(PostFeatures!=null) { if(PostFeatures.Contains(Feature.PropertyFeatureID.ToString())) { Response.Write(“checked=\”checked\””); } } %> /> <label for=”Feature<%=Feature.PropertyFeatureID%>”> <%=Feature.Description%></label> <% } %> In the receiving controller method: … Read more
To complete Will’s answer, here’s a “standard” implementation of the CanExecuteChanged event : public event EventHandler CanExecuteChanged { add { CommandManager.RequerySuggested += value; } remove { CommandManager.RequerySuggested -= value; } } (from Josh Smith’s RelayCommand class) By the way, you should probably consider using RelayCommand or DelegateCommand : you’ll quickly get tired of creating new … Read more
You are encountering the differences between physical scrolling and logical scrolling. As you have discovered, each has its tradeoffs. Physical scrolling Physical scrolling (CanContentScroll=false) just goes by pixels, so: The viewport always represents exactly the same portion of your scroll extent, giving you a smooth scrolling experience, and but The entire contents of the DataGrid … Read more