public static readonly DependencyProperty TopMarginProperty =
DependencyProperty.RegisterAttached("TopMargin", typeof(int), typeof(FrameworkElement),
new FrameworkPropertyMetadata(false, FrameworkPropertyMetadataOptions.AffectsRender));
public static void SetTopMargin(FrameworkElement element, int value)
{
// set top margin in element.Margin
}
public static int GetTopMargin(FrameworkElement element)
{
// get top margin from element.Margin
}
如果将此与行为结合起来,您可以在 TopMargin 属性上收到更改通知。
The key is to realize that setting it in code like this:
sp2.Margin = new System.Windows.Thickness{ Left = 5 };
is equivalent to:
sp2.Margin = new System.Windows.Thickness{ Left = 5, Top = 0, Right = 0, Bottom = 0 };
You can't set just a single value in a Thickness instance through either code or XAML. If you don't set some of the values, they will be implicitly zero. Therefore, you can just do this to convert the accepted code sample in your other question to a XAML equivalent:
A better option than a custom control would be to write an attached property and change the Thickness using the code above in the dependency property setter. The below code would be usable across ALL controls which have a Margin.
public static readonly DependencyProperty TopMarginProperty =
DependencyProperty.RegisterAttached("TopMargin", typeof(int), typeof(FrameworkElement),
new FrameworkPropertyMetadata(false, FrameworkPropertyMetadataOptions.AffectsRender));
public static void SetTopMargin(FrameworkElement element, int value)
{
// set top margin in element.Margin
}
public static int GetTopMargin(FrameworkElement element)
{
// get top margin from element.Margin
}
If you couple this with a Behavior, you can get notification changes on the TopMargin property.
I am WPF/XAML, thy UI framework, and you will use me when coding apps for Windows - eventually.
Thou shalt have no other technologies - I will not be cross-platform but I'll try to with Silverlight UWP, because Hololens is going to be huge some day. "Xamarin.Forms"? Never heard of it!
Thou shalt inevitably take the name of the Lord in vain, repeatedly, when using WPF/XAML.
Remember the sabbath day: every 7 days... or hours or minutes of coding I will make you take a break to go to StackOverflow and 2000things.
Honor thy father and mother: Windows Forms.
Should thou shalt adopt MVVM, thou shalt also implement INPC and INCC, but rejoice! Thou hast a choice: you can use it or you can use it with anger.
Thou shalt not commit adultery interop with other apps and frameworks.
Thou shalt not covet thy neighbour's UI framework.
Thou shalt not be able to set a position of an element dynamically using binding of an either attached property or margin without writing few lines of code-behind.
Thou shalt never have a simple bool Visibility property in XAML. I am WPF/XAML.
Tested in UWP but this should work for any XAML-based framework. The nice thing is they won't override the other values on the Margin, so you can combine them as well.
You can't define just the Top margin with a binding, because Margin is of type Thickness which isn't a dependency object. However you could use a MultiValueConverter that would take 4 margin values to make 1 Thickness objects
Converter :
public class ThicknessMultiConverter : IMultiValueConverter
{
#region IMultiValueConverter Members
public object Convert(object[] values, Type targetType, object parameter, System.Globalization.CultureInfo culture)
{
double left = System.Convert.ToDouble(values[0]);
double top = System.Convert.ToDouble(values[1]);
double right = System.Convert.ToDouble(values[2]);
double bottom = System.Convert.ToDouble(values[3]);
return new Thickness(left, top, right, bottom);
}
public object[] ConvertBack(object value, Type[] targetTypes, object parameter, System.Globalization.CultureInfo culture)
{
Thickness thickness = (Thickness)value;
return new object[]
{
thickness.Left,
thickness.Top,
thickness.Right,
thickness.Bottom
};
}
#endregion
}
<Window.Resources>
<!-- Define the default amount of space -->
<system:Double x:Key="Space">10.0</system:Double>
<!-- Border space around a control -->
<Thickness
x:Key="BorderSpace"
Left="{StaticResource Space}"
Top="{StaticResource Space}"
Right="{StaticResource Space}"
Bottom="{StaticResource Space}"
/>
<!-- Space between controls that are positioned vertically -->
<Thickness
x:Key="TopSpace"
Top="{StaticResource Space}"
/>
</Window.Resources>
Here's a simple way of doing this without writing converters or hard-coding margin values. First, define the following in your Window (or other control) resources:
<Window.Resources>
<!-- Define the default amount of space -->
<system:Double x:Key="Space">10.0</system:Double>
<!-- Border space around a control -->
<Thickness
x:Key="BorderSpace"
Left="{StaticResource Space}"
Top="{StaticResource Space}"
Right="{StaticResource Space}"
Bottom="{StaticResource Space}"
/>
<!-- Space between controls that are positioned vertically -->
<Thickness
x:Key="TopSpace"
Top="{StaticResource Space}"
/>
</Window.Resources>
Note that system is defined as xmlns:system="clr-namespace:System;assembly=mscorlib".
public class ThicknessSingleValueConverter : IValueConverter
{
override Convert(...)
{
return new Thickness(0, (double)object, 0, 0);
}
//etc...
Use a converter, the sample code below will convert the double you are binding to to a thickness. It will set the "Top" of the thickness to the bound field. You could optionally use a ConverterParameter to determine if you are binding to left, top, right, or bottom.
public class ItemViewModel
{
public Thickness Margin { get; private set }
public ItemViewModel(ModelClass model)
{
/// You can calculate needed margin here,
/// probably depending on some value from the Model
this.Margin = new Thickness(0,model.TopMargin,0,0);
}
}
然后 XAML 就很简单了:
<StackPanel Margin="{Binding Margin}">
Maybe I am "late to the party", but didn't like any of provided solutions, and it seems to me that simplest and cleanest solution is define Thickness property in ViewModel (or anything that you are binding) and then Bind that property. Something like this:
public class ItemViewModel
{
public Thickness Margin { get; private set }
public ItemViewModel(ModelClass model)
{
/// You can calculate needed margin here,
/// probably depending on some value from the Model
this.Margin = new Thickness(0,model.TopMargin,0,0);
}
}
What would be nice is to be able to do this by specifying something like the code example below.
<StackPanel Margin=",10,,">
Unfortunately this capability doesn't seem to exist by default in WPF and it's a shame because it requires developers to hard code known default values in a way that later makes it more difficult to skin or theme an application.
The best solution that I can think of at this point is using a converter, but the amount of extra code you have to produce to introduce this is not ideal.
发布评论
评论(12)
这不是您要找的吗?
第一个值是左边距,然后是顶部,然后是右边,最后但并非最不重要的底部。
我不确定你是否想将它绑定到某些东西,但如果不是,那就可以了。
Isn't this what you're looking for?
The first value is Left margin, then Top, then Right, and last but not least Bottom.
I'm not sure if you want to bind it to something, but if not, that'll work.
关键是要认识到,在如下代码中设置它:
相当于:
您不能通过任一代码在
Thickness
实例中仅设置单个值或 XAML。如果您不设置某些值,它们将隐式为零。因此,您可以执行此操作,将其他问题中接受的代码示例转换为 XAML 等效项:其中
MyConverter
仅返回仅设置Top 的
并将所有其他值保留为零。Thickness
当然,您可以编写自己的控件,将这些单独的值公开为依赖属性,以使您的代码更加简洁:
比自定义控件更好的选择是编写附加属性并更改在依赖属性设置器中使用上面的代码来设置厚度。下面的代码可在所有具有边距的控件中使用。
如果将此与行为结合起来,您可以在 TopMargin 属性上收到更改通知。
The key is to realize that setting it in code like this:
is equivalent to:
You can't set just a single value in a
Thickness
instance through either code or XAML. If you don't set some of the values, they will be implicitly zero. Therefore, you can just do this to convert the accepted code sample in your other question to a XAML equivalent:where
MyConverter
just returns aThickness
that sets only theTop
and leaves all other values as zero.Of course, you could write your own control that does expose these individual values as dependency properties to make your code a little cleaner:
A better option than a custom control would be to write an attached property and change the Thickness using the code above in the dependency property setter. The below code would be usable across ALL controls which have a Margin.
If you couple this with a Behavior, you can get notification changes on the TopMargin property.
这属于 WPF/XAML 戒律:
SilverlightUWP,因为 Hololens 有一天会变得巨大。 “Xamarin.Forms”?从来没有听说过!犯奸淫。bool
Visibility 属性。我是 WPF/XAML。你的罪被列在#9。
This belongs to the WPF/XAML commandments:
SilverlightUWP, because Hololens is going to be huge some day. "Xamarin.Forms"? Never heard of it!commit adulteryinterop with other apps and frameworks.bool
Visibility property in XAML. I am WPF/XAML.Your sin is listed at #9.
刚刚编写了一些附加属性,这些属性应该可以轻松地从绑定或静态资源设置单独的 Margin 值:
用法:
在 UWP 中测试,但这应该适用于任何基于 XAML 的框架。好处是它们不会覆盖边距上的其他值,因此您也可以将它们组合起来。
Just wrote some attached properties that should make it easy to set an individual Margin value from a binding or static resource:
Usage:
Tested in UWP but this should work for any XAML-based framework. The nice thing is they won't override the other values on the Margin, so you can combine them as well.
您不能仅使用绑定定义上边距,因为
Margin
的类型为Thickness
,它不是依赖项对象。但是,您可以使用MultiValueConverter
,它需要 4 个边距值来生成 1 个 Thickness 对象Converter :
XAML :
You can't define just the Top margin with a binding, because
Margin
is of typeThickness
which isn't a dependency object. However you could use aMultiValueConverter
that would take 4 margin values to make 1 Thickness objectsConverter :
XAML :
我想你可以使用属性语法,来自 MSDN< /a>:
比你不需要任何转换器
但顶部不是 DependancyProperty - 回到转换器
I thought You could use the property syntax, from MSDN:
Than you won't need any converter
But the Top is not DependancyProperty - back to converter
这是一种简单的方法,无需编写转换器或硬编码边距值即可实现此目的。首先,在 Window(或其他控件)资源中定义以下内容:
请注意,
system
定义为xmlns:system="clr-namespace:System; assembly=mscorlib"
。现在,您可以按如下方式使用这些资源:
现在,如果您想更改控件之间的默认间距,只需在一处更改即可。
Here's a simple way of doing this without writing converters or hard-coding margin values. First, define the following in your Window (or other control) resources:
Note that
system
is defined asxmlns:system="clr-namespace:System;assembly=mscorlib"
.Now you can use these resources as follows:
Now if you want to change the default space between controls, you only need to change it in one place.
我使用绑定到 Margin (RelativeSource Self) 的 ValueConverter 并解析 ConverterParameter,给出为“top:123;left:456”。
转换器仅覆盖参数指定的边距。
xaml
TextBlock 将使用 Style 给定的边距(顶部边距除外),该边距将被 0 覆盖。
玩得开心!
I use a ValueConverter bound to Margin (RelativeSource Self) and Parse the ConverterParameter, given as "top:123;left:456".
The Converter only overwrites Margins given by Parameter.
xaml
TextBlock would use the Margin given by Style except the Margin-Top, that will be overwritten with 0.
Have fun with it!
使用转换器,下面的示例代码会将您绑定的双精度数转换为厚度。它将厚度的“顶部”设置为绑定字段。您可以选择使用 ConverterParameter 来确定是否绑定到左侧、顶部、右侧或底部。
。
Use a converter, the sample code below will convert the double you are binding to to a thickness. It will set the "Top" of the thickness to the bound field. You could optionally use a ConverterParameter to determine if you are binding to left, top, right, or bottom.
.
这是一个巧妙的解决方案:
如果将此代码添加到命名空间并定义以下大小:
然后您可以创建 Tiny、Small、Medium、Large 和 Large 大小。像这样的巨大利润:
或
然后代码将根据您的资源创建利润。
Here's a nifty solution:
If you add this code to your namespace and define the following sizes:
You can then create Tiny, Small, Medium, Large & Huge margins like this:
or
The code will then create margins based on your resources.
也许我“迟到了”,但不喜欢任何提供的解决方案,在我看来,最简单、最干净的解决方案是在 ViewModel 中定义 Thickness 属性(或您要绑定的任何内容),然后绑定该属性。像这样:
然后 XAML 就很简单了:
Maybe I am "late to the party", but didn't like any of provided solutions, and it seems to me that simplest and cleanest solution is define Thickness property in ViewModel (or anything that you are binding) and then Bind that property. Something like this:
And then XAML is simple:
如果能够通过指定类似下面的代码示例的内容来完成此操作,那就太好了。
不幸的是,默认情况下,WPF 中似乎不存在此功能,这很遗憾,因为它要求开发人员对已知的默认值进行硬编码,而这种方式稍后会使应用程序的皮肤或主题化变得更加困难。
目前我能想到的最好的解决方案是使用转换器,但是您必须生成的额外代码量来引入它并不理想。
What would be nice is to be able to do this by specifying something like the code example below.
Unfortunately this capability doesn't seem to exist by default in WPF and it's a shame because it requires developers to hard code known default values in a way that later makes it more difficult to skin or theme an application.
The best solution that I can think of at this point is using a converter, but the amount of extra code you have to produce to introduce this is not ideal.