Change data context of template property












0















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>









share|improve this question

























  • You change the DataContext of a control by setting the DataContext property of it. Your issue is unclear.

    – mm8
    Nov 19 '18 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 '18 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 '18 at 10:38
















0















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>









share|improve this question

























  • You change the DataContext of a control by setting the DataContext property of it. Your issue is unclear.

    – mm8
    Nov 19 '18 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 '18 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 '18 at 10:38














0












0








0








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>









share|improve this question
















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 '18 at 11:05







DerApe

















asked Nov 19 '18 at 6:47









DerApeDerApe

2,28722643




2,28722643













  • You change the DataContext of a control by setting the DataContext property of it. Your issue is unclear.

    – mm8
    Nov 19 '18 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 '18 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 '18 at 10:38



















  • You change the DataContext of a control by setting the DataContext property of it. Your issue is unclear.

    – mm8
    Nov 19 '18 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 '18 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 '18 at 10:38

















You change the DataContext of a control by setting the DataContext property of it. Your issue is unclear.

– mm8
Nov 19 '18 at 12:54





You change the DataContext of a control by setting the DataContext property of it. Your issue is unclear.

– mm8
Nov 19 '18 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 '18 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 '18 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 '18 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 '18 at 10:38












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















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

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







Popular posts from this blog

鏡平學校

ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

Why https connections are so slow when debugging (stepping over) in Java?