jsakamoto

Hi @accessguru, I published the v.5.0.0 Preview today. - https://www.nuget.org/packages/Toolbelt.Blazor.HotKeys2/5.0.0-preview.3 I believe that the latest preview version will work correctly. But please make sure to avoid disposing of hotkey entries...

Hi @accessguru, Thank you for your feedback! Your contributions must be helpful not only to me but also to every developer who utilizes this library. By the way, I changed...

@accessguru I'm retracting my decision. According to the Microsoft Learn document, we should allow the `Dispose` method to be invoked multiple times. https://learn.microsoft.com/en-us/dotnet/standard/garbage-collection/implementing-dispose So, I'll follow the guidelines above and...

Hello @accessguru, Sorry for the late reply. > Please consider these changes in your DisposeAsync() method... Yeah, actually, you don't need to worry about it because the latest implementation of...

@tnglemongrass Thank you for letting me know about the problem. I must have overlooked the Blazor Hybrid scenario. As a workaround for a while, could you try to add one...

[FYI] This problem is a bug in the .NET SDK. See also: https://github.com/dotnet/maui/issues/15234 Fortunately, I've verified the problem went away on the .NET 9 SDK Preview 5. So, please take...

@Martin-Andersen Currently, it is intentionally by design. See also: https://github.com/jsakamoto/Toolbelt.Blazor.HotKeys2/issues/7#issuecomment-1372142048

Hi everyone, I've changed my opinion that I don't provide the `Add()` methods of overloaded version for `async Task` because so many developers were confused by my decision. So, the...

Hi @phcd30, You must be able to override and prevent the default keyboard shortcuts like `Ctrl+S` without any specials. However, in some cases, you need to use the `HotKeys.CreateContext` in...

Hi @lukas-kyeso, Yes, currently, there are no callbacks for the `keyup` event on this library.