-
Notifications
You must be signed in to change notification settings - Fork 665
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TeachingTip does not display on the target control and IsOpen can't be set from markup #538
Comments
@duke7553 thanks for the bug report! I tried your snippet and wasn't able to repro. When are you setting IsOpen=true? I could believe there is a timing issue where perhaps the TextBox isn't at its final layout position when we try to calculate the TeachingTip position, but I'd like to make sure that's what you're seeing. Do you have an app we could install and debug through? |
Yes, I do have a public app that has this problem.
Thanks for your help. |
I also noticed setting the IsOpen property from markup fails completely. |
@jevansaks ProHome.RibbonTeachingTip is the updated name in the project in case you were wondering. |
Thanks! @StephenLPeters can you debug this project too? |
I think this is the issue. We need to defer calculating position and stuff until everything is loaded. I don't see a bug tracking this so we'll use this. |
@duke7553 To work around this, don't set IsOpen until the Loaded event. |
@jevansaks Thanks! This did the trick. |
Describe the bug
Targeting a teaching tip to a control may display the TeachingTip elsewhere.
Steps to reproduce the bug
I'm unaware of a pattern that can be replicated.
Expected behavior
The TeachingTip should mount/attach itself to the targeted control-in the correct position.
Screenshots
This screenshot shows the teaching tip, which is targeting the bottom of the "Navigate to a path..." TextBox displayed in an incorrect position.
Version Info
NuGet package version:
Microsoft.UI.Xaml 2.1.190405004
Additional context
Code snippet of problem:
The text was updated successfully, but these errors were encountered: