-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Windows] Handle focus events using FocusManager
(take 2)
#24695
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,6 +13,7 @@ | |
using Microsoft.UI.Xaml.Media.Imaging; | ||
using Windows.Graphics.DirectX; | ||
using Windows.Storage.Streams; | ||
using Microsoft.UI.Xaml.Input; | ||
using Xunit; | ||
using Xunit.Sdk; | ||
using WColor = Windows.UI.Color; | ||
|
@@ -49,42 +50,50 @@ public static Task SendKeyboardReturnType(this FrameworkElement view, ReturnType | |
public static async Task WaitForFocused(this FrameworkElement view, int timeout = 1000) | ||
{ | ||
TaskCompletionSource focusSource = new TaskCompletionSource(); | ||
view.GotFocus += OnFocused; | ||
|
||
FocusManager.GotFocus += OnFocused; | ||
|
||
try | ||
{ | ||
await focusSource.Task.WaitAsync(TimeSpan.FromMilliseconds(timeout)); | ||
} | ||
finally | ||
{ | ||
view.GotFocus -= OnFocused; | ||
FocusManager.GotFocus -= OnFocused; | ||
} | ||
|
||
void OnFocused(object? sender, RoutedEventArgs e) | ||
void OnFocused(object? sender, FocusManagerGotFocusEventArgs e) | ||
{ | ||
view.GotFocus -= OnFocused; | ||
focusSource.SetResult(); | ||
if (e.NewFocusedElement == view) | ||
{ | ||
FocusManager.GotFocus -= OnFocused; | ||
focusSource.SetResult(); | ||
This comment was marked as resolved.
Sorry, something went wrong. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think that could happen considering the event is being unsubscribed in the line above. If there was a race condition, raising an exception would be exactly what we want in this device test. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ooh my bad, I didn't see it's a unit test. Reviewing code from mobile is hard 😅 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Btw: are you interested in this PR for performance reasons? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @MartyIX yes, and it looks like to have a good gotcha on here, so I'm interested in learning new tricks (; |
||
} | ||
} | ||
} | ||
|
||
public static async Task WaitForUnFocused(this FrameworkElement view, int timeout = 1000) | ||
{ | ||
TaskCompletionSource focusSource = new TaskCompletionSource(); | ||
view.LostFocus += OnUnFocused; | ||
|
||
FocusManager.LostFocus += OnUnFocused; | ||
|
||
try | ||
{ | ||
await focusSource.Task.WaitAsync(TimeSpan.FromMilliseconds(timeout)); | ||
} | ||
finally | ||
{ | ||
view.LostFocus -= OnUnFocused; | ||
FocusManager.LostFocus -= OnUnFocused; | ||
} | ||
|
||
void OnUnFocused(object? sender, RoutedEventArgs e) | ||
void OnUnFocused(object? sender, FocusManagerLostFocusEventArgs e) | ||
{ | ||
view.LostFocus -= OnUnFocused; | ||
focusSource.SetResult(); | ||
if (e.OldFocusedElement == view) | ||
{ | ||
FocusManager.LostFocus -= OnUnFocused; | ||
focusSource.SetResult(); | ||
} | ||
} | ||
} | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there no perf issues when there is a super complex UI? If we have maybe 1k elements on screen, will not the add and lookup be slow? It may still be faster than what we had before, but I am getting flashbacks when millions of objects would sub and unsub from the theme changed event.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing an entry from a CWT seems very fast compared to event unsubscription.
https://github.com/dotnet/runtime/blob/main/src/libraries/System.Private.CoreLib/src/System/Runtime/CompilerServices/ConditionalWeakTable.cs#L614
I would rather set an initial capacity of 128 to the CWT to avoid a lot of initial resize operation (which is expensive).
If you're still concerned we have an alternative but much slower implementation:
#24355
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding to CWT is definitely faster because it does not involve interops (perf comparison of
ConnectingHandler
should be persuasive here). CTW should behave like a dictionary and "insert" operation for dictionaries is O(1) (i.e. so in practice it should be ~<10 nanoseconds1; whereas interops are more like milliseconds). So CWT lookups and inserts should be orders of magnitude faster.I think that the CWT approach is strictly better for performance right now. What can be done is that I can try to create a huge grid with 1000 elements and measure performance for that scenario.
That's a good idea.
Footnotes
https://startdebugging.net/2023/08/net-8-performance-dictionary-vs-frozendictionary/ just to get a feel what one might expect. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps @jonathanpeppers can double check my post as he's a performance guru :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@albyrock87 Interestingly, the CTW does not support passing
capacity
as far as I can tell: https://learn.microsoft.com/en-us/dotnet/api/system.runtime.compilerservices.conditionalweaktable-2.-ctor?view=net-8.0 👀