|
If you are using INotifyPropertyChanged and the view / viewmodel concept, you can bind a property of the view model to the visibility.
For e.g.
Now its just setting this MyBranchProperty to the appropriate value in the view model.
Too much of heaven can bring you underground
Heaven can always turn around
Too much of heaven, our life is all hell bound
Heaven, the kill that makes no sound
|
|
|
|
|
Just a little advice from an old school programmer to another. I've learned that Binding is the only way to go with WPF. You will cause yourself more bugs, errors and headache trying to do it old school. Just step up and take the time to learn how to bind elements and such. Like I said just a friendly bit of advice.
WPF offers so much in the way of customization I sincerely hope Microsoft doesn't scrap it.
|
|
|
|
|
|
Having an issue that is causing me to bang my head. my namespace is not being seen by the designer but still compiles and runs fine. the problem is that I can't view the forms at design time this happened shortly after I moved my files into folders to organize my program better. Yes I did make namespace modifications all throughout my app otherwise it wouldn't run. here is the main window xaml that is causing the error to occur.
<ribbon:RibbonWindow
x:Name="window"
x:Class="MHManager.MainWindow"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="clr-namespace:MHManager"
xmlns:classes="clr-namespace:MHManager.Classes"
xmlns:controls="clr-namespace:MHManager.Controls"
xmlns:shared="http://schemas.actiprosoftware.com/winfx/xaml/shared"
xmlns:ribbon="http://schemas.actiprosoftware.com/winfx/xaml/ribbon"
xmlns:themes="http://schemas.actiprosoftware.com/winfx/xaml/themes"
xmlns:editors="http://schemas.actiprosoftware.com/winfx/xaml/editors"
xmlns:ribboneditors="http://schemas.actiprosoftware.com/winfx/xaml/ribboneditors"
xmlns:s="http://www.stemasoft.com/xaml"
xmlns:i="clr-namespace:System.Windows.Interactivity;assembly=System.Windows.Interactivity"
xmlns:ComponentModel="clr-namespace:System.ComponentModel;assembly=WindowsBase"
xmlns:System="clr-namespace:System;assembly=mscorlib"
ResizeMode="CanResizeWithGrip"
ApplicationName="Manufactured Housing Manager"
Icon="Icons/MHManagericon.ico"
Background="{Binding Background, ElementName=navigationPane}"
Height="632"
Width="930"
Loaded="window_Loaded" Closed="applicationExitCommand_Execute">
these three give the error
xmlns:local="clr-namespace:MHManager"
xmlns:classes="clr-namespace:MHManager.Classes"
xmlns:controls="clr-namespace:MHManager.Controls"
Maybe this will help to figure this out. It only happens when I copy all the files and transfer them to my laptop to work on the project there. So on my desktop everything is fine, but after I open the project on my laptop the Designer displays this message:
An Unhandled Exception has occurred
System.Reflection.TargetInvocationException
Exception has been thrown by the target of an invocation.
at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
System.InvalidOperationException
'[Unknown]' property does not point to a DependencyObject in path '(0).(1)[0].(2)'.
at System.Windows.Media.Animation.Storyboard.VerifyPathIsAnimatable(PropertyPath path)
at System.Windows.Media.Animation.Storyboard.ClockTreeWalkRecursive(Clock currentClock, DependencyObject containingObject, INameScope nameScope, DependencyObject parentObject, String parentObjectName, PropertyPath parentPropertyPath, HandoffBehavior handoffBehavior, HybridDictionary clockMappings, Int64 layer)
at System.Windows.Media.Animation.Storyboard.ClockTreeWalkRecursive(Clock currentClock, DependencyObject containingObject, INameScope nameScope, DependencyObject parentObject, String parentObjectName, PropertyPath parentPropertyPath, HandoffBehavior handoffBehavior, HybridDictionary clockMappings, Int64 layer)
at System.Windows.Media.Animation.Storyboard.BeginCommon(DependencyObject containingObject, INameScope nameScope, HandoffBehavior handoffBehavior, Boolean isControllable, Int64 layer)
at System.Windows.VisualStateGroup.StartNewThenStopOld(FrameworkElement element, Storyboard[] newStoryboards)
at System.Windows.VisualStateManager.GoToStateInternal(FrameworkElement control, FrameworkElement stateGroupsRoot, VisualStateGroup group, VisualState state, Boolean useTransitions)
at System.Windows.VisualStateManager.GoToStateCommon(FrameworkElement control, FrameworkElement stateGroupsRoot, String stateName, Boolean useTransitions)
at System.Windows.VisualStateManager.GoToState(FrameworkElement control, String stateName, Boolean useTransitions)
at System.Windows.Controls.Primitives.Thumb.ChangeVisualState(Boolean useTransitions)
at System.Windows.Controls.Control.UpdateVisualState(Boolean useTransitions)
at System.Windows.Controls.Control.OnPostApplyTemplate()
at System.Windows.FrameworkElement.ApplyTemplate()
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.DockPanel.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Control.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.DockPanel.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Grid.MeasureCell(Int32 cell, Boolean forceInfinityV)
at System.Windows.Controls.Grid.MeasureCellsGroup(Int32 cellsHead, Size referenceSize, Boolean ignoreDesiredSizeU, Boolean forceInfinityV)
at System.Windows.Controls.Grid.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Grid.MeasureCell(Int32 cell, Boolean forceInfinityV)
at System.Windows.Controls.Grid.MeasureCellsGroup(Int32 cellsHead, Size referenceSize, Boolean ignoreDesiredSizeU, Boolean forceInfinityV)
at System.Windows.Controls.Grid.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Border.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.DockPanel.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at MS.Internal.Helper.MeasureElementWithSingleChild(UIElement element, Size constraint)
at System.Windows.Controls.ContentPresenter.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Grid.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Border.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Control.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Documents.AdornerDecorator.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Grid.MeasureCell(Int32 cell, Boolean forceInfinityV)
at System.Windows.Controls.Grid.MeasureCellsGroup(Int32 cellsHead, Size referenceSize, Boolean ignoreDesiredSizeU, Boolean forceInfinityV)
at System.Windows.Controls.Grid.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Border.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Border.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.DockPanel.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Border.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Grid.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Control.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Border.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at MS.Internal.Designer.ZoomableViewPresenter.DesignerBackground.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at Microsoft.Windows.Design.Interaction.DesignerView.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at MS.Internal.Designer.Viewport.MeasureOverride(Size availableSize)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at MS.Internal.Helper.MeasureElementWithSingleChild(UIElement element, Size constraint)
at System.Windows.Controls.ScrollContentPresenter.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Grid.MeasureCell(Int32 cell, Boolean forceInfinityV)
at System.Windows.Controls.Grid.MeasureCellsGroup(Int32 cellsHead, Size referenceSize, Boolean ignoreDesiredSizeU, Boolean forceInfinityV)
at System.Windows.Controls.Grid.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.ScrollViewer.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Grid.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at MS.Internal.Helper.MeasureElementWithSingleChild(UIElement element, Size constraint)
at System.Windows.Controls.ContentPresenter.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Control.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Interop.HwndSource.SetLayoutSize()
at System.Windows.Interop.HwndSource.set_RootVisualInternal(Visual value)
at MS.Internal.DeferredHwndSource.ProcessQueue(Object sender, EventArgs e)
modified on Saturday, August 27, 2011 8:28 AM
|
|
|
|
|
Try using command Rebuild Soulution from Build menu. It will clean cache and build it again. Then try restarting visual studio. If those namespaces are in a diffrent project, then check references.
Edit: You also coud try to delete .suo file that lies in the same folder that has a solution file. That file resets Certan IDE elements, but does not break project/solution. This file has hidden attribute. You need special settings to see it.
modified on Saturday, August 27, 2011 4:57 PM
|
|
|
|
|
Thanks I've tried cleaning and rebuilding the project/solution but I havn't tried deleting the .suo file.
|
|
|
|
|
Ok tried that and a few other things still get the same error and can't display design time window. Also it won't let me compile a release version like this although a debug version is fine.
|
|
|
|
|
|
ok now I can get it to build debug or retail on my desktop but my laptop gives me the error. Mind you it always been the laptop giving the error. Brand new Laptop 4gig ram, has the new AMD APU in it. What throws me is that it will compile and run in debug but not retail and the designer can't display my main form.
Yet, on my desktop it is fine. This is driving me nuts. As for the Library Controls links I reviewed them, I do have some custom controls in my project but have not been giving me any trouble as they are basically overridden controls. Extended RTF editor, Masked Text Box, etc.
|
|
|
|
|
I've tracked down the issue, trying to resolve it now. My issue stems from creating a custom style in Blend for parts of a third party control. I am using NavigationPane from Codeplex and had created styles for the splitterbars and buttons this seemed to work fine on my desktop but when moving it to my laptop it wouldn't display the design-time preview of the form. removing the Style="" comment made it viewable again. I've decided to modify the source code of NavigationPane and added my own style to it's list of Styles. So far this has solved the issue.
This has been resolved Thank you for all the help.
modified 21-Sep-11 18:25pm.
|
|
|
|
|
I'm building a pie chart (from the WPF Toolkit). Here's the code:
public Chart ChartObject;
protected void MakePie(List<RepItem> data, string seriesTitle, string yProperty)
{
DisplayCategories categories = new DisplayCategories();
foreach (RepItem item in data)
{
categories.Add(item.Category);
}
System.Collections.ObjectModel.Collection<ResourceDictionary> palette = MakePalette(categories);
this.ChartObj.Palette = palette;
PieSeries series = new PieSeries()
{
ItemsSource = data,
Title = seriesTitle,
DependentValueBinding = new System.Windows.Data.Binding(yProperty),
IndependentValueBinding = new System.Windows.Data.Binding("Category"),
TransitionDuration = new TimeSpan(0),
};
this.ChartObj.Series.Add(series);
}
I have to build the palette manually because the number of values represented in the pie isn't necessarily the same, and they values are sorted from lowest to highest before creating the series. The end result is that the pie slice color must always be the correct color for the associated category regardless of that category's position in the pie.
In any case, that part works great. However, I decided I wanted custom tooltips, so I created a custom ControlTemplate in the app resources:
<ControlTemplate x:Key="PieDataTemplate" TargetType="wtkchart:PieDataPoint">
<Grid>
<Path x:Name="Slice"
Data="{TemplateBinding Geometry}"
Fill="{TemplateBinding Background}"
Stroke="{TemplateBinding BorderBrush}">
<ToolTipService.ToolTip>
<StackPanel>
<ContentControl Content="{Binding Path=Category}" FontSize="12" />
<ContentControl Content="{TemplateBinding FormattedDependentValue,
Converter={StaticResource TooltipValueFormatter}}"
FontWeight="Bold" FontSize="14" />
<ContentControl Content="{TemplateBinding FormattedRatio}"/>
</StackPanel>
</ToolTipService.ToolTip>
</Path>
</Grid>
</ControlTemplate>
If I uncomment out the code in the c# code, I get the tooltip I want, but all of the pie slices turn orange. If I re-comment the code, the tooltip isn't right, but the colors are. I THINK I want to change the binding on the Fill property in the control template, but I don't know exactly how to bind that with the parent chart's Palette property.
Any help?
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
Would there be any way you would be able to bind the Palette background with the Fill background using relative resources?
Too much of heaven can bring you underground
Heaven can always turn around
Too much of heaven, our life is all hell bound
Heaven, the kill that makes no sound
modified on Friday, August 26, 2011 2:29 PM
|
|
|
|
|
Well, the Palette is a collection of ResourceDictionary objects, each of which contains a single brush component, so there is no palette "background" to bind to.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
Well, I made the decision to switch away from the WPF Toolkit to Visiblox. In less than 1 day, I got all the charts working the way I wanted. I fought with the WPF Toolkit for more than a week, and it was still not right.
Good riddance WPF Toolkit. What a steaming pile...
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
John Simmons / outlaw programmer wrote: Visiblox
Makes sense. Use whatever supports our requirements.
In defense of the toolkit, its not too bad.
I wonder why they have not been upgrading it though.
Too much of heaven can bring you underground
Heaven can always turn around
Too much of heaven, our life is all hell bound
Heaven, the kill that makes no sound
|
|
|
|
|
Abhinav S wrote: In defense of the toolkit, its not too bad.
Until you start to color outside the lines. I've NEVER experienced a time when I didn't need to do something that was beyond the in-the-box capabilities of of a chosen framework/library. The fact that it's near impossible with the Toolkit answers your next question:
Abhinav S wrote: I wonder why they have not been upgrading it though.
Because they know it's crap from a real-world standpoint.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
I used a WPF Toolkit DataGrid.
I'd like to move cell in a column with mouse.
There are a lot of examples about the drag & drop row but nothing for drag & drop of cell.
How can I do to drag & drop cell in a column ?
Thanks.
|
|
|
|
|
Hope the title is OK. Didn't know how to put it any better.
I am looking here for some background information, opinions if you will. I know how to code them.
But I can't get my head around why sometimes things are done one way and sometimes the other.
If you read WPF books (mostly) they teach you to implement RoutedUICommands.
So in short, to have a static class with commands, commandbindings in XAML and some codebehind.
If you read some of the MVVM articles on this site or this article http://msdn.microsoft.com/en-us/magazine/dd419663.aspx[^].
They implement classes with ICommand interface and/or a RelayCommand : ICommand class and put some command handling in the ViewModel
So, when and why, pros and cons, of using one or the other. This is what I hope to hear from you.
|
|
|
|
|
You should always write WPF code the MVVM way. It just produces cleaner, more organized and more efficient code. WPF and MVVM are really a match made in heaven. Once you get your MVVM framework situated, MVVM isn't all that difficult. People who don't want to take a couple of months to learn it and set up a framework are the only ones who make a big deal about how "hard and complicated" it is. If you try write a WPF the non MVVM way, you'll end up with a mess of spaghetti code.
|
|
|
|
|
Very well, I agree that MVVM is a good pattern.
But when not using RoutedUICommand class you loose the bubbling and tunneling, right?
This wil not get me into problems?
|
|
|
|
|
RelayCommand is really kind of required for MVVM. It allows you to define the CanExecute & Execute handlers as part of the RelayCommand object itself. With other types of command implementations, you need to add them to the CommandBindings collection which you don't really have access to in MVVM since the CommandBindingsCollection is part of the window and not the VM. You don't need bubbling and tunneling in VMs. Its mostly handling clicks and such.
|
|
|
|
|
Hm, make good sense to me.
Thx.
|
|
|
|
|
Oh, one other thing I can clear up for you... bubbling and tunneling is really only useful in controls IMO. You may have thought about using them to communicate between a child view and the parent, but that is really not the recommended pattern in MVVM. Most frameworks will include some sort of messenger service that basically lets you send async messages around to anybody who cares to listen for that specific message.
|
|
|
|
|
SledgeHammer01 wrote: If you try write WPF the non MVVM way, you'll end up with a mess of spaghetti code.
FTFY...
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
Seriously? WPF seems way cleaner then MFC or Winforms. Sounds like you need a better MVVM framework .
|
|
|
|
|