Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Is it expected that x:DeferLoadStrategy changes order of loading?

See original GitHub issue

Create a custom control Widget (note: not a user control!) and the consumer of that control adds the attribute x:DeferLoadStrategy="Lazy" to it in their XAML the order of the following calls and events changes like so:

Without the attribute:

Widget() constuctor
OnApplyTemplate()
Loaded()

But with the attribute:

Widget() constuctor
Loaded()
OnApplyTemplate()

This has the effect that calls to GetTemplateChild() in Loaded will succeed in the first scenario but not the second.

Is this an intended effect of the attribute? If so could it be added to the documentation here, thanks!

https://docs.microsoft.com/en-us/windows/uwp/xaml-platform/x-deferloadstrategy-attribute

Issue Analytics

State:
Created 3 years ago
Reactions:3
Comments:6 (4 by maintainers)

Top GitHub Comments

2reactions

phraemercommented, Jan 8, 2021

@stevenbrix I’ve actually moved on from this job but @gabrielbunselmeyer should be able to check for you

1reaction

StephenLPeterscommented, Oct 9, 2020

That is generally the strategy we take (to save member pointers to template parts in on apply template), however you do need to be careful to clean these up properly. The WinUI 2 project does this via the Tracker_Ref object.