Change data context of template property
up vote
0
down vote
favorite
I have a data template property on a control which I would like to wrap to change the behavior a bit.
That template property should be exposed to the user(developer) of my control but I want to change the data context, because the data context I would like to pass the user is somewhere within the visual tree and I don't want the user to navigate there every time. So in the end the binding path is just a bit simplyfied for the user (developer) of the BaseControl
XAML in control wrapper
<BaseControl SomeTemplate="{Binding MyTemplate}" />
Code behind in control wrapper
public static readonly DependencyProperty MyTemplateProperty = DependencyProperty.Register(
"MyTemplate", typeof(DataTemplate), typeof(BaseControl), new PropertyMetadata(default(DataTemplate)));
public DataTemplate MyTemplate { get { return (DataTemplate)GetValue(MyTemplateProperty ); } set { SetValue(MyTemplateProperty , value); } }
Usage of control wrapper
<BaseControl>
<BaseControl.MyTemplateProperty>
<!-- desired -->
<Label Content="{Binding Name}" />
<!-- actual -->
<!-- the data context of "OtherProperty" should be exposed to the user -->
<Label Content="{Binding DataContext.SomeProperty.OtherProperty.Name, RelativeSource={RelativeSource Mode=FindAncestor, AncestorType=SomeType}}" />
</BaseControl.MyTemplateProperty>
</BaseControl>
c# wpf datatemplate dependency-properties
asked Nov 19 at 6:47
DerApe
2,27722643
add a comment |
up vote
0
down vote
favorite
I have a data template property on a control which I would like to wrap to change the behavior a bit.
That template property should be exposed to the user(developer) of my control but I want to change the data context, because the data context I would like to pass the user is somewhere within the visual tree and I don't want the user to navigate there every time. So in the end the binding path is just a bit simplyfied for the user (developer) of the BaseControl
XAML in control wrapper
<BaseControl SomeTemplate="{Binding MyTemplate}" />
Code behind in control wrapper
public static readonly DependencyProperty MyTemplateProperty = DependencyProperty.Register(
"MyTemplate", typeof(DataTemplate), typeof(BaseControl), new PropertyMetadata(default(DataTemplate)));
public DataTemplate MyTemplate { get { return (DataTemplate)GetValue(MyTemplateProperty ); } set { SetValue(MyTemplateProperty , value); } }
Usage of control wrapper
<BaseControl>
<BaseControl.MyTemplateProperty>
<!-- desired -->
<Label Content="{Binding Name}" />
<!-- actual -->
<!-- the data context of "OtherProperty" should be exposed to the user -->
<Label Content="{Binding DataContext.SomeProperty.OtherProperty.Name, RelativeSource={RelativeSource Mode=FindAncestor, AncestorType=SomeType}}" />
</BaseControl.MyTemplateProperty>
</BaseControl>
c# wpf datatemplate dependency-properties
asked Nov 19 at 6:47
DerApe
2,27722643
You change theDataContextof a control by setting theDataContextproperty of it. Your issue is unclear.
– mm8
Nov 19 at 12:54
I have some complex binding path within my control wrapper and I want that path to be simplyfied for the user of that wrapper template
– DerApe
Nov 20 at 8:23
By "user" I guess you mean the developer. That's now how it works. A control inherits a DataContext and if you want some other DataContext, you will have to set it. This is what you would expect as a WPF and XAML developer. Trying to "simplify" or modify fundamental things such as this only makes your control more complex and harder to use.
– mm8
Nov 20 at 10:38
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a data template property on a control which I would like to wrap to change the behavior a bit.
That template property should be exposed to the user(developer) of my control but I want to change the data context, because the data context I would like to pass the user is somewhere within the visual tree and I don't want the user to navigate there every time. So in the end the binding path is just a bit simplyfied for the user (developer) of the BaseControl
XAML in control wrapper
<BaseControl SomeTemplate="{Binding MyTemplate}" />
Code behind in control wrapper
public static readonly DependencyProperty MyTemplateProperty = DependencyProperty.Register(
"MyTemplate", typeof(DataTemplate), typeof(BaseControl), new PropertyMetadata(default(DataTemplate)));
public DataTemplate MyTemplate { get { return (DataTemplate)GetValue(MyTemplateProperty ); } set { SetValue(MyTemplateProperty , value); } }
Usage of control wrapper
<BaseControl>
<BaseControl.MyTemplateProperty>
<!-- desired -->
<Label Content="{Binding Name}" />
<!-- actual -->
<!-- the data context of "OtherProperty" should be exposed to the user -->
<Label Content="{Binding DataContext.SomeProperty.OtherProperty.Name, RelativeSource={RelativeSource Mode=FindAncestor, AncestorType=SomeType}}" />
</BaseControl.MyTemplateProperty>
</BaseControl>
c# wpf datatemplate dependency-properties
asked Nov 19 at 6:47
DerApe
2,27722643
I have a data template property on a control which I would like to wrap to change the behavior a bit.
That template property should be exposed to the user(developer) of my control but I want to change the data context, because the data context I would like to pass the user is somewhere within the visual tree and I don't want the user to navigate there every time. So in the end the binding path is just a bit simplyfied for the user (developer) of the BaseControl
XAML in control wrapper
<BaseControl SomeTemplate="{Binding MyTemplate}" />
Code behind in control wrapper
public static readonly DependencyProperty MyTemplateProperty = DependencyProperty.Register(
"MyTemplate", typeof(DataTemplate), typeof(BaseControl), new PropertyMetadata(default(DataTemplate)));
public DataTemplate MyTemplate { get { return (DataTemplate)GetValue(MyTemplateProperty ); } set { SetValue(MyTemplateProperty , value); } }
Usage of control wrapper
<BaseControl>
<BaseControl.MyTemplateProperty>
<!-- desired -->
<Label Content="{Binding Name}" />
<!-- actual -->
<!-- the data context of "OtherProperty" should be exposed to the user -->
<Label Content="{Binding DataContext.SomeProperty.OtherProperty.Name, RelativeSource={RelativeSource Mode=FindAncestor, AncestorType=SomeType}}" />
</BaseControl.MyTemplateProperty>
</BaseControl>
c# wpf datatemplate dependency-properties
c# wpf datatemplate dependency-properties
asked Nov 19 at 6:47
DerApe
2,27722643
asked Nov 19 at 6:47
DerApe
2,27722643
edited Nov 20 at 11:05
asked Nov 19 at 6:47
DerApe
2,27722643
asked Nov 19 at 6:47
DerApe
2,27722643
asked Nov 19 at 6:47
DerApe
2,27722643
2,27722643
You change theDataContextof a control by setting theDataContextproperty of it. Your issue is unclear.
– mm8
Nov 19 at 12:54
I have some complex binding path within my control wrapper and I want that path to be simplyfied for the user of that wrapper template
– DerApe
Nov 20 at 8:23
By "user" I guess you mean the developer. That's now how it works. A control inherits a DataContext and if you want some other DataContext, you will have to set it. This is what you would expect as a WPF and XAML developer. Trying to "simplify" or modify fundamental things such as this only makes your control more complex and harder to use.
– mm8
Nov 20 at 10:38
add a comment |
You change theDataContextof a control by setting theDataContextproperty of it. Your issue is unclear.
– mm8
Nov 19 at 12:54
I have some complex binding path within my control wrapper and I want that path to be simplyfied for the user of that wrapper template
– DerApe
Nov 20 at 8:23
By "user" I guess you mean the developer. That's now how it works. A control inherits a DataContext and if you want some other DataContext, you will have to set it. This is what you would expect as a WPF and XAML developer. Trying to "simplify" or modify fundamental things such as this only makes your control more complex and harder to use.
– mm8
Nov 20 at 10:38
You change the
DataContext of a control by setting the DataContext property of it. Your issue is unclear.– mm8
Nov 19 at 12:54
You change the
DataContext of a control by setting the DataContext property of it. Your issue is unclear.– mm8
Nov 19 at 12:54
I have some complex binding path within my control wrapper and I want that path to be simplyfied for the user of that wrapper template
– DerApe
Nov 20 at 8:23
I have some complex binding path within my control wrapper and I want that path to be simplyfied for the user of that wrapper template
– DerApe
Nov 20 at 8:23
By "user" I guess you mean the developer. That's now how it works. A control inherits a DataContext and if you want some other DataContext, you will have to set it. This is what you would expect as a WPF and XAML developer. Trying to "simplify" or modify fundamental things such as this only makes your control more complex and harder to use.
– mm8
Nov 20 at 10:38
By "user" I guess you mean the developer. That's now how it works. A control inherits a DataContext and if you want some other DataContext, you will have to set it. This is what you would expect as a WPF and XAML developer. Trying to "simplify" or modify fundamental things such as this only makes your control more complex and harder to use.
– mm8
Nov 20 at 10:38
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369583%2fchange-data-context-of-template-property%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You change the
DataContextof a control by setting theDataContextproperty of it. Your issue is unclear.– mm8
Nov 19 at 12:54
I have some complex binding path within my control wrapper and I want that path to be simplyfied for the user of that wrapper template
– DerApe
Nov 20 at 8:23
By "user" I guess you mean the developer. That's now how it works. A control inherits a DataContext and if you want some other DataContext, you will have to set it. This is what you would expect as a WPF and XAML developer. Trying to "simplify" or modify fundamental things such as this only makes your control more complex and harder to use.
– mm8
Nov 20 at 10:38