Update the docs for version 6.2.0

Author: TolikPylypchuk

CHANGELOG.md

@@ -1,5 +1,14 @@
 # SharpHook Changelog
 
+## [v6.2.0](https://github.com/TolikPylypchuk/SharpHook/releases/tag/v6.2.0) (July 19, 2025)
+
+- The ability to disable events of type `KeyTyped` was added.
+
+- Simulation of keyboard events was fixed on macOS.
+
+- libuiohook was updated to commit
+[4217638](https://github.com/TolikPylypchuk/libuiohook/tree/42176381d991fc009b369295121bb2bccc9ff705).
+
 ## [v6.1.2](https://github.com/TolikPylypchuk/SharpHook/releases/tag/v6.1.2) (June 22, 2025)
 
 - Simulation of letter keys in different layouts was fixed on Windows – the same keys are simulated regardless of the

SharpHook/README.md

@@ -30,8 +30,8 @@ called.
 - `RunMouse` – creates a mouse-only global hook and runs it on the current thread, blocking it until `Stop` is called.
 - `Stop` – destroys the global hook.
 
-**Important**: You have to remember that only one global hook can exist at a time since calling `SetDispatchProc` will
-override the previously set one.
+> **Important**: You have to remember that only one global hook can exist at a time since calling `SetDispatchProc` will
+> override the previously set one.
 
 Additionally, `UioHook` contains the `PostEvent` method for simulating input events.
 
@@ -89,9 +89,9 @@ propagation by setting the `SuppressEvent` property to `true` inside the event h
 and is only supported on Windows and macOS. You can check the event time and whether the event is real or simulated with
 the `EventTime` and `IsEventSimulated` properties respectively.
 
-**Important**: Always use one instance of `IGlobalHook` at a time in the entire application since they all must use the
-same static method to set the hook callback for libuiohook, so there may only be one callback at a time. Running a
-global hook when another global hook is already running will corrupt the internal global state of libuiohook.
+> **Important**: Always use one instance of `IGlobalHook` at a time in the entire application since they all must use the
+> same static method to set the hook callback for libuiohook, so there may only be one callback at a time. Running a
+> global hook when another global hook is already running will corrupt the internal global state of libuiohook.
 
 You can create a keyboard-only or a mouse-only hook by passing a `GlobalHookType` to the hook's constructor. This makes
 a real difference only on Windows where there are two different global hooks – a keyboard hook and a mouse hook. On

docs/articles/about.md

@@ -55,6 +55,15 @@ You need .NET 9 to build SharpHook.
 
 ## Changelog
 
+### [v6.2.0](https://github.com/TolikPylypchuk/SharpHook/releases/tag/v6.2.0) (July 19, 2025)
+
+- The ability to disable events of type `KeyTyped` was added.
+
+- Simulation of keyboard events was fixed on macOS.
+
+- libuiohook was updated to commit
+[4217638](https://github.com/TolikPylypchuk/libuiohook/tree/42176381d991fc009b369295121bb2bccc9ff705).
+
 ### [v6.1.2](https://github.com/TolikPylypchuk/SharpHook/releases/tag/v6.1.2) (June 22, 2025)
 
 - Simulation of letter keys in different layouts was fixed on Windows – the same keys are simulated regardless of the

docs/articles/native.md

@@ -12,9 +12,9 @@ the hood.
 ## Low-Level Functionality Providers
 
 If you want to use the low-level functionality, you don't need to use the `UioHook` class directly. Instead you can use
-interfaces in the `SharpHook.Providers` namespace. The methods in those interfaces are the same as in the `UioHook`
-class. `SharpHook.Providers.UioHookProvider` implements all of these interfaces and simply calls the corresponding
-methods in `UioHook`. This should be done to decouple your code from `UioHook` and make testing easier.
+interfaces in the `SharpHook.Providers` namespace. The methods and properties in those interfaces are the same as in the
+`UioHook` class. `SharpHook.Providers.UioHookProvider` implements all of these interfaces and simply calls the
+corresponding methods in `UioHook`. This should be done to decouple your code from `UioHook` and make testing easier.
 
 ## Working with the Hook Itself
 
@@ -95,6 +95,12 @@ thread which handles the event. Supressing events works only on Windows and macO
 > after `MouseReleased` if the cursor was not dragged. Since these events are raised by libuiohook, and not the OS,
 > suppressing them has no effect.
 
+Events of type `KeyTyped` can be disabled using the `UioHook.SetKeyTypedEnabled` method. It is recommended to disable
+them if your application doesn't use them as these events may cause slight system-wide side effects. More information
+can be found in [an article on OS-specific constraints](os-constraints.md). `UioHook.IsKeyTypedEnabled` can be used to
+query whether `KeyTyped` events are enabled. By default they are enabled. `SharpHook.Providers.IGlobalHookProvider`
+contains the `KeyTypedEnabled` property which can also be used to control this behaviour.
+
 ## Simulating Input Events
 
 `UioHook` contains the `PostEvent` method for simulating input events. It accepts a `UioHookEvent`, but it doesn't need

docs/articles/os-constraints.md

@@ -8,17 +8,21 @@ This article describes OS-specific constrains and other things that should be no
 
 Only Windows 10 and 11 are supported.
 
-> [!IMPORTANT]
-> If the global hook runs on versions of Windows older than Windows 10 1607, then it will destroy dead keys rendering
-> them unusable. This is because it uses the
-> [`ToUnicodeEx`](https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-tounicodeex) function to
-> determine which characters are typed by key presses, and before Windows 10 1607 this function changed the keyboard
-> state.
-
-> [!IMPORTANT]
-> There is an issue on Windows 10 – when a global hook is running, some editors may insert Unicode characters when the
-> user presses <kbd>Alt</kbd>+<kbd>Up Arrow</kbd> or <kbd>Alt</kbd>+<kbd>Down Arrow</kbd>. This issue is not present on
-> Windows 11.
+### `KeyTyped` Events
+
+It is recommended to disable events of type `KeyTyped` if they are unused since they may cause system-wide side
+effects:
+
+- When a keyboard global hook is running with `KeyTyped` events enabled on versions of Windows older than Windows 10
+1607, it will destroy dead keys rendering them unusable. This is because it uses the
+[`ToUnicodeEx`](https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-tounicodeex) function to
+determine which characters are typed by key presses, and before Windows 10 1607 this function changed the dead key
+state.
+
+- When a keyboard global hook is running with `KeyTyped` events enabled, some editors may insert Unicode characters when
+the user presses <kbd>Alt</kbd>+<kbd>Up Arrow</kbd> or <kbd>Alt</kbd>+<kbd>Down Arrow</kbd>. As of July 2025, on Windows
+11, this issue can be reproduced in Microsoft Visual Studio, but on Windows 10, it can be reproduced in other editors as
+well.
 
 ### Supported Architectures