|
Hi, All!
I'm having another major trouble. I have developed a control, that has some properties, but once I set binding to these properties, a strange error occures during the build. Visual Studio highlights an irrelevant string from the xaml code with green color.
here is a code sample which throws that error:
<a:SearchControl x:Name="SearchResult" SearchCriteria="{Binding ElementName=SearchCriteria, Path=Criteria}"/>
Note 2 things:
1) Code below builds fine
<a:SearchControl x:Name="SearchResult"/>
2) In an output window of VS, it is stated, that System.Unimplemented exception occurred in PresentationFramework.dll. Usually, such exception means, that requested method is not implemented, which is kinda odd, because this property is indeed implemented.
|
|
|
|
|
hello
I'm using sample from WPF Modal Dialog[^] to popup my WPF Modal dialog, problem is, the modal dialog is not movable, how may I correct this?
Here's code to embed the popup
<br />
<Popup<br />
Name="MyMessageModal" <br />
Placement="Top"<br />
PlacementTarget="{Binding ElementName=SomeFormElement}"<br />
Width="100px" <br />
Height="100px" <br />
IsOpen="False"<br />
StaysOpen="true" <br />
AllowsTransparency="True"<br />
Visibility="Collapsed"<br />
><br />
<StackPanel><br />
<myctrl:MyMessageDialog x:Name="SomeEmbedMsgCtrl" ></myctrl:MyMessageDialog><br />
</StackPanel><br />
</Popup><br />
And to actually show it,
<br />
MyMessageModal.IsOpen=true;<br />
MyMessageModal.Visibility = Visibility.Visible;<br />
Thanks
dev
|
|
|
|
|
You could write your own code on the mouse up, mouse down and mouse move event of the popup.
Perform lienar transforms as the user drags the mouse holding the top part of the popup.
|
|
|
|
|
Great thansk I got it working!
dev
|
|
|
|
|
I'm using VS2010 and SL4. I have the following XAML, and I'm trying to implement visual state management, but it appears I don't understand how it works.
<Border CornerRadius="8" BorderBrush="Black" BorderThickness="1" Background="SlateBlue"
Height="35" HorizontalAlignment="Stretch" VerticalAlignment="Top">
<ItemsControl x:Name="myItems" >
<ItemsControl.ItemsPanel>
<ItemsPanelTemplate>
<StackPanel Orientation="Horizontal" Background="Transparent"/>
</ItemsPanelTemplate>
</ItemsControl.ItemsPanel>
<ItemsControl.ItemTemplate>
<DataTemplate>
<Grid>
<VisualStateManager.VisualStateGroups>
<VisualStateGroup x:Name="States">
<VisualState x:Name="MouseOver">
<Storyboard >
<ColorAnimation Storyboard.TargetName="itemBorder"
Duration="0:0:1" To="Yellow"
Storyboard.TargetProperty="(Border.Background).(SolidColorBrush.Color)"/>
<ColorAnimation Storyboard.TargetName="itemContent"
Duration="0:0:1" To="Black"
Storyboard.TargetProperty="(TextBlock.Foreground).(SolidColorBrush.Color)"/>
</Storyboard>
</VisualState>
<VisualState x:Name="Normal">
<Storyboard >
<ColorAnimation Storyboard.TargetName="itemBorder" Duration="0:0:1"
Storyboard.TargetProperty="(Border.Background).(SolidColorBrush.Color)"/>
<ColorAnimation Storyboard.TargetName="itemContent" Duration="0:0:1"
Storyboard.TargetProperty="(TextBlock.Foreground).(SolidColorBrush.Color)"/>
</Storyboard>
</VisualState>
</VisualStateGroup>
</VisualStateManager.VisualStateGroups>
<Border x:Name="itemBorder" Background="Transparent" Margin="5,0,0,0">
<Border.RenderTransform>
<CompositeTransform/>
</Border.RenderTransform>
<TextBlock x:Name="itemContent" Text="{Binding}"
FontSize="13" Padding="0" Margin="5,0,0,0"
HorizontalAlignment="Left"
VerticalAlignment="Center"
Foreground="White" />
</Border>
</Grid>
</DataTemplate>
</ItemsControl.ItemTemplate>
<ItemsControl.Items>
<core:String>Item 1</core:String>
<core:String>Item 2</core:String>
<core:String>Item 3</core:String>
<core:String>Item 4</core:String>
</ItemsControl.Items>
</ItemsControl>
</Border>
.45 ACP - because shooting twice is just silly
-----
"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
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
In this code, AFAIK, when you move your mouse over the ItemsControl, the background of the itemBorder (Border) changes to Yellow and itemContent (TextBox) foreground changes to Black. Both color change again when the state moves back to normal.
|
|
|
|
|
That's what I *want* to happen, but it's not happening.
.45 ACP - because shooting twice is just silly
-----
"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
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
After some searching I found this[^] - apparently the datatemplate does not support the VisualStateManager. There is a workaround as given on this website.
Best of luck!
|
|
|
|
|
I have a grid defined as
<Grid x:Name="CoordWPanel" Height="38" Margin="10,0,70,10" VerticalAlignment="Bottom"
Background="#77000000" HorizontalAlignment="Left">
I want the background shade to cover the the bottom of the screen (less the margin area). But it always stops at the last control placed in the grid. The shading only goes halfway across the screen because that's how far the controls in the grid go. How can I get the grid to fill out the rest of the area in the margins?
Thanks.
Brent
|
|
|
|
|
Nevermind - HorizontalAlignment="Stretch" Duh
Brent
|
|
|
|
|
I was typing my reply when you sent yours. My apologies.
Brad
Deja Moo - When you feel like you've heard the same bull before.
|
|
|
|
|
No big deal, I just had one of those bonehead moments when I realize it must be time to go home.
Brent
|
|
|
|
|
You don't have a width specified so the Grid will shrink to be as small as possible, i.e. just wide enough to hold your controls. And it will pin itself into the bottom left corner. Your right/top margins will only be used if the controls are big enough to fill the width/height of your window.
Change HorizontalAlignment="Left" to HorizontalAlignment="Stretch" (or delete the assignment all together, stretch is the default). The grid will take up as much room as possible leaving the margins specified on each side.
Depending on how you want your controls contained to look, you might want to put a StackPanel in the Grid to hold the controls or switch the Grid to a DockPanel and dock your controls to the bottom.
Brad
Deja Moo - When you feel like you've heard the same bull before.
|
|
|
|
|
I have a settings page that I want to hide certain settings unless it has been unlocked by a password by someone authorized to make the changes.
Right now what I have:
Visibility="{Binding RelativeSource={RelativeSource AncestorType={x:Type Window}}, Path=Unlocked, Converter={StaticResource ResourceKey=BooleanVisibility}}"
Which works fine. However, it seems extremely time consuming to type that in for every control, even doing copy and paste.
I tried:
<UserControl.Resources>
<BooleanToVisibilityConverter x:Key="BooleanVisibility" />
<Binding x:Key="LockedProperty" RelativeSource="{RelativeSource AncestorType={x:Type Window}}" Path="Unlocked" Converter="{StaticResource ResourceKey=BooleanVisibility}" />
</UserControl.Resources></pre
And the Visibility of the control set to:
<pre>Visibility="{StaticResource ResourceKey=LockedProperty}"
Which complains that "A 'Binding' cannot be set on the 'Value' property of type 'DictionaryEntry'. A 'Binding' can only be set on a DependencyProperty of a DependencyObject." Which makes sense now that I'm reading it again. It thinks I'm trying to bind UserControl.Resources.
Is there any way to make a binding template or resource that would let me make the binding call a lot simpler?
Brad
Deja Moo - When you feel like you've heard the same bull before.
|
|
|
|
|
See RelativeSource actually tries to find the window element just by traversing through the entire visual tree. So I recommend to use ElementName rather than an Ancestor.
Use x:Name for the Window and use
Visibility = {Binding ElementName=win, Path=Unlocked, Converter={StaticResource BooleanVisibility}}
Actually this will make the binding to avoid traversing through the Visual Tree.
Abhishek Sur
Don't forget to click "Good Answer" if you like this Solution.
Visit My Website-->www.abhisheksur.com
|
|
|
|
|
I am tring to bind a xaml element property to a property defined in the class.
I've tried the following:
public class FMChartMS
{
private double setting = 275;
public double MyProperty { get { return setting; } }
}
<my:FMChartMS x:Name="ChartPage">
<Grid Height="{Binding MyProperty, ElementName=ChartPage}" />
It crashes the app. What am I missing?
.45 ACP - because shooting twice is just silly
-----
"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
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
You need to make a DependencyProperty for MyProperty.
public static readonly DependencyProperty MyPropertyProperty =
DependencyProperty.Register("MyProperty", typeof(double), typeof(FMChartMS), new PropertyMetadata(false));
public double MyProperty
{
get { return (double)this.GetValue(MyPropertyProperty); }
set { this.SetValue(MyProperty Property, value); }
}
I'm using the standard notation for naming dependency properties, PropertyNameProperty. That's why it's called MyPropertyProperty when using your example. In my project I have a property called Unlock with the dependency property called UnlockProperty. I like to declare the DependencyProperty first so IntelliSense will help fill in the blanks.
Brad
Deja Moo - When you feel like you've heard the same bull before.
|
|
|
|
|
That didn't work.
.45 ACP - because shooting twice is just silly
-----
"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
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
Sorry, there was a copy/paste error.
DependencyProperty.Register("MyProperty", typeof(double), typeof(FMChartMS), new PropertyMetadata(false));
should be
DependencyProperty.Register("MyProperty", typeof(double), typeof(FMChartMS), new PropertyMetadata(0d));
The "0d" is the initial value of the property. You can set it to whatever you want.
Warning: The "d" is very important. For some reason the PropertyMetadata constructor does not implicitly convert values passed into, so even though you can use double var = 0; in code, new PropertyMetadata(0) will cause your program to fail just the same as it is now with being passed a boolean. It has to be passed a value of the same type being declared.
Brad
Deja Moo - When you feel like you've heard the same bull before.
|
|
|
|
|
How do we change theme for a silverlight application at run-time. Suppose I have "Theme1.xaml", "Theme2.xaml" and "Theme3.xaml" as themes inside 'Themes' folder, and I wish to apply them on button-click or combobox-selection.
In WPF, I used to get the required result with following code -
ResourceDictionary skin = new ResourceDictionary();
skin.Source = new Uri(@"Themes/" + themeName + ".xaml", UriKind.Relative);
Application.Current.Resources.MergedDictionaries.Clear();
Application.Current.Resources.MergedDictionaries.Add(skin);
But for Silverlight, I'm not sure how to do it. Any idea? Please do not provide link with 'Telerik' content. I have seen it already.
|
|
|
|
|
Hi Experts,
I am unable to locate a property similar to WindowsForm "DropDownWidth" Property for the Combo Box in WPF. Is there a work around to achieve this functionality?
Please help!
Thanks in advance.
Regards,
Samar
P.S.: Just FYI for those who are not aware, "DropDownWidth" Property changes the width of the drop down area. The area when the Combo Box is clicked to show its master contents.
modified on Friday, July 30, 2010 2:40 AM
|
|
|
|
|
Dear friends,
I am new to WPF and I have to design pages, and I do not know how to design pages that fits for many screen size
Is it possible to design screen that fits in all the screen size? Then how?
If not all the screen size I need to fix it for 4/3 screen resolution like
800 600
1024 768
1280 960
1600 1200
1792 1344
Any idea? Link?
Thanks
|
|
|
|
|
The layout system in UI is designed to be resolution independent. Rather than positioning things absolutely, you can lay things out in any one of a number of panels (such as a Grid), and use margins and padding to achieve whatever effects you want.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
Thanks for reply,
My problem like these ..
i have button and i specified size for the button in One screen size... when i change to other screen size ..the button size same
i tried to by removing button size and just to specify the margin ...if i set margin the (then the margin space remains same)
i do not know what to do?
thanks
|
|
|
|
|
I have a list of data item objects (ObservableCollection<MyDataItem>) bound to a line series, and I need to change the symbol's visibility based on the value of a boolean property (ShowSymbol)in a given data item object. In other words, for a given LineSeries, each datapoint could potentially be represented by a different/unique symbol.
I've written a converter (VisConverter) that is supposed to set the visibility of the symbol based on the value of the ShowSymbol property, and I've added the converter to the UserControl.Resources, but I'm not sure how I specify the property in the xaml.
Can anyone help?
SOLUTION ===================
Visibility="{Binding ShowSymbol, Converter={StaticResource VisConverter}}"
.45 ACP - because shooting twice is just silly
-----
"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
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
modified on Wednesday, July 28, 2010 3:54 PM
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
