Merge pull request #136 from X9VoiD/add-counters

Add counters

Author: X9VoiD

site/_includes/wiki/header.html

@@ -1 +1 @@
-<h2 id="page-title">{{ page.title }}</h2>
+<h1 id="page-title">{{ page.title }}</h1>

site/_sections/Framework.md

@@ -2,20 +2,20 @@
 title: Frameworks
 ---
 
-### Windows
+## Windows
 
 [x64](https://aka.ms/dotnet/6.0/windowsdesktop-runtime-win-x64.exe)
 
-### MacOS
+## MacOS
 
 [arm64](https://aka.ms/dotnet/6.0/dotnet-runtime-osx-arm64.pkg)
 
 [x86-64/x64 (Intel based)](https://aka.ms/dotnet/6.0/dotnet-runtime-osx-x64.pkg)
 
-### Linux
+## Linux
 
 See the [official Linux installation documentation](https://docs.microsoft.com/en-us/dotnet/core/install/linux).
 
-### Uncommon builds
+## Uncommon builds
 
 [Windows arm64](https://aka.ms/dotnet/6.0/windowsdesktop-runtime-win-arm64.exe)

site/_wiki/Development/Configurations.md

@@ -2,7 +2,7 @@
 title: Writing OpenTabletDriver Configurations
 ---
 
-### Device Information
+## Device Information
 
 Generic device identification information is required for OpenTabletDriver in order for it to be able to differentiate
 tablets.
@@ -11,12 +11,12 @@ tablets.
 | :--------------: | :------------: | :---------- |
 |       Name       |    `string`    | The name of the device. This is always the device manufacturer's name followed by the device's model number or product name when not applicable.
 
-### Specifications
+## Specifications
 
 Tablet configuration specifications provide OpenTabletDriver with information it needs in order to correctly and
 accurately handle the data the tablet device outputs.
 
-#### Digitizer
+### Digitizer
 
 This refers to the graphics tablet's digitizer, which provides coordinates of where the tool is positioned. This is
 always required for the device to function.
@@ -28,7 +28,7 @@ always required for the device to function.
 | Horizontal Resolution |  `double`  | Device Units | The horizontal resolution of the digitizer in device units
 |  Vertical Resolution  |  `double`  | Device Units | The vertical resolution of the digitizer in device units
 
-#### Pen
+### Pen
 
 This refers to the pen tool for the graphics tablet. It is the source of position and typically the source of pressure
 data. This is almost always required.
@@ -38,7 +38,7 @@ data. This is almost always required.
 |  Max Pressure   |   `uint`   | The maximum pressure reported by the pen in device pressure units. This is used to calculate a percentage of pressure. If there are more than pens supported by this tablet, the pen with the highest pressure value is used.
 |  Button Count   |   `uint`   | The amount of buttons on the pen. This does not include the eraser, if applicable. If there are more than one pens supported by this tablet, use the number of buttons on the pen with the most.
 
-#### Auxiliary Buttons
+### Auxiliary Buttons
 
 This refers to any buttons located on the graphics tablet pad. This should only be enabled if there are any auxililary
 buttons.
@@ -47,21 +47,21 @@ buttons.
 | :-----------: | :---------: | :---------- |
 | Button Count  |   `uint`    | The amount of buttons
 
-#### Touch
+### Touch
 
 This refers to the touch digitizer, which may be built into the pen digitizer. This exists as the resolution of the
 touch digitizer can be different than the pen digitizer. This should only be enabled if the graphics tablet supports
 touch input.
 
 This has the same properties as the [digitizer](#digitizer)
 
-#### Mouse
+### Mouse
 
 This refers to an absolute positioning mouse tool. This should only be enabled if the graphics tablet supports a mouse.
 
 This has the same properties as the [auxiliary buttons](#auxiliary-buttons)
 
-### Identifiers
+## Identifiers
 
 Device identifiers are what actually detect the tablet. Anything defined here is used in the detection process to
 pinpoint devices.

site/_wiki/Documentation/CommandLine.md

@@ -2,20 +2,20 @@
 title: Command Line Arguments
 ---
 
-### UI
+## UI
 
 |        Argument       | Description |
 | :-------------------: | ----------- |
 | `--minimized` or `-m` | Starts the application in a minimized state
 
-### Daemon
+## Daemon
 
 |       Argument      | Description |
 | :-----------------: | ----------- |
 | `--appdata` or `-a` | Uses the specified directory for application data
 | `--config` or `-c`  | Uses the specified directory for searching of tablet configuration overrides
 
-### Console
+## Console
 
 This is a very limited list of the available commands in the console app, since the command names
 can vary between driver versions.

site/_wiki/Documentation/Logs.md

@@ -2,7 +2,7 @@
 title: Logs
 ---
 
-### GUI
+## GUI
 
 To view logs, click on the <kbd>Console</kbd> tab. Optionally, change filter from <kbd>Information</kbd> to <kbd>Debug</kbd> for more detailed logs.
 
@@ -12,7 +12,7 @@ Sometimes, the OpenTabletDriver daemon can crash hard enough that the errors can
 sent to the GUI. In this case, you can find a
 partial log in the location specified [here](#daemon-log).
 
-### Daemon
+## Daemon
 
 The output from daemon is the log.
 
@@ -23,7 +23,7 @@ To view that log, run the following command as your user:
 journalctl --user-unit opentabletdriver.service
 ```
 
-#### Exception Log Location {#daemon-log}
+### Exception Log Location {#daemon-log}
 
 If the daemon crashes from an "unrecoverable" exception, the `daemon.log` file will
 include a stack trace defining where the error happened, which is useful for debugging.

site/_wiki/FAQ/General.md

@@ -2,15 +2,15 @@
 title: General FAQ
 ---
 
-### Is my tablet supported? {#supported-tablets}
+## Is my tablet supported? {#supported-tablets}
 
 Verify if your tablet is in the list of supported tablets [here]({% link _sections/Tablets.md %}). If it is not, you may do one of the following:
 
 - [Create a tablet support request in Github.](https://github.com/OpenTabletDriver/OpenTabletDriver/issues/new?assignees=&labels=configuration&projects=&template=tablet_configuration.yml&title=Add+support+for+)
 - [Create a tablet support thread in #config-creation channel of the Discord server.]({{ site.data.links.project.DiscordInvite }})
 - [Write the tablet configuration.]({% link _wiki/Development/AddingTabletSupport.md %})
 
-### My tablet is supported but not detected? {#tablet-not-detected}
+## My tablet is supported but not detected? {#tablet-not-detected}
 
 OpenTabletDriver currently has *no support* for tablets connected via Bluetooth. Make sure that your tablet is connected via USB. There is partial support for tablets connected via wireless dongle.
 
@@ -29,7 +29,7 @@ Then check [above](#supported-tablets) if your tablet is supported. If it is and
 
 or alternatively, see if there is a [tablet model specific FAQ]({% link _wiki/FAQ/ModelSpecific.md %}) for your tablet.
 
-### Where are my settings and plugins stored? {#appdata}
+## Where are my settings and plugins stored? {#appdata}
 
 The following table describes the location of the default application data directory for each operating system:
 
@@ -47,7 +47,7 @@ The application data directory contents are as follows:
 |      Plugins      | Folder | Contains installed plugins (`.dll` files). This folder should not be modified manually.
 |      Presets      | Folder | Contains saved presets
 
-### My cursor is going crazy! It teleports everywhere! {#emi-interference}
+## My cursor is going crazy! It teleports everywhere! {#emi-interference}
 
 This is caused by electromagnetic interference (EMI) from other devices. Make sure that the tablet is not near any of the following:
 
@@ -58,25 +58,25 @@ This is caused by electromagnetic interference (EMI) from other devices. Make su
 
 If certain that the tablet is not near any of the above, try replacing the pen. If the problem persists, replace the tablet. It's broken!
 
-### I see two moving cursors when hovering my pen! {#two-cursors}
+## I see two moving cursors when hovering my pen! {#two-cursors}
 
 This is caused by another tablet driver running in the background. Make sure that you have
 uninstalled all other tablet drivers before using OpenTabletDriver.
 
-#### Windows
+### Windows
 
 Run [TabletDriverCleanup]({{ site.data.links.external.TabletDriverCleanup.latest }}) to remove
 all other tablet drivers.
 
-#### Linux
+### Linux
 
 See [here]({% link _wiki/Documentation/RequiredPermissions.md %}#setup-linux).
 
-#### macOS
+### macOS
 
 Uninstall any other tablet drivers you have installed.
 
-### Does OpenTabletDriver support pen pressure? {#pressure}
+## Does OpenTabletDriver support pen pressure? {#pressure}
 
 All of our supported tablets has full pen pressure support unless otherwise noted on
 the [Tablets]({% link _sections/Tablets.md %}) page.
@@ -92,15 +92,15 @@ However, to make the driver output the pressure to your operating system, you ma
 [Windows Ink]: {% link _wiki/FAQ/Windows.md %}#win-ink
 [Artist Mode]: {% link _wiki/FAQ/Linux.md %}#artist-mode
 
-### How to convert areas to and from OpenTabletDriver? {#area-conversion}
+## How to convert areas to and from OpenTabletDriver? {#area-conversion}
 
-#### Conversion through the OpenTabletDriver UI
+### Conversion through the OpenTabletDriver UI
 
 - Right click the Tablet Area Editor
 - Click the <kbd>Convert Item</kbd> menu item
 - Select the OEM driver to convert from, then input the appropriate values to the converter
 
-#### Conversion through manual calculation
+### Conversion through manual calculation
 
 Use this reference chart for the upcoming formulas:
 
@@ -118,7 +118,7 @@ Use this reference chart for the upcoming formulas:
 
 Use the following formulas to get values for OpenTabletDriver's area editor's `Width`, `Height`, `XOffset`, and `YOffset` fields:
 
-##### Wacom and Veikk
+#### Wacom and Veikk
 
 |  Term  | Definition |
 | :----: | :--------- |
@@ -136,7 +136,7 @@ XOffset = (Width  / 2) + (Left / LPI * 25.4)
 YOffset = (Height / 2) + (Top  / LPI * 25.4)
 ```
 
-##### XP-Pen
+#### XP-Pen
 
 | Term | Definition |
 | :--: | :--------- |
@@ -154,7 +154,7 @@ XOffset = (Width  / 2) + (XPX / 3.937)
 YOffset = (Height / 2) + (XPY / 3.937)
 ```
 
-##### Huion and Gaomon
+#### Huion and Gaomon
 
 |  Term  | Definition |
 | :----: | --- |

site/_wiki/FAQ/Linux.md

@@ -10,16 +10,16 @@ before continuing.
 > Also check out [Linux App Specific FAQ]({% link _wiki/FAQ/LinuxAppSpecific.md %}) for
 app-specific instructions.
 
-### My tablet is supported but not detected? {#troubleshooting}
+## My tablet is supported but not detected? {#troubleshooting}
 
 > Read [General FAQ]({% link _wiki/FAQ/General.md %}#tablet-not-detected) first before continuing below if you haven't already.
 {:.alert-warning}
 
-#### Common Problems
+### Common Problems
 
 If your tablet is connected properly and is supported, but is still not detected, [check logs]({% link _wiki/Documentation/Logs.md %}) for any errors or warnings. If you find any, try finding for a match and its accompanying solution below:
 
-##### Another driver is found {#hid_uclogic}
+#### Another driver is found {#hid_uclogic}
 
 *Symptoms*:
 
@@ -31,7 +31,7 @@ Another tablet driver found: <driver>
 
 - [See here]({% link _wiki/Documentation/RequiredPermissions.md %}#setup-linux)
 
-##### Insufficient permissions {#udev}
+#### Insufficient permissions {#udev}
 
 *Symptoms*:
 
@@ -43,13 +43,13 @@ Not permitted to open HID class device at /dev/hidrawX
 
 - [See here]({% link _wiki/Documentation/RequiredPermissions.md %})
 
-### Tablet is detected but not working?
+## Tablet is detected but not working?
 
-#### Fresh Install {#fail-virtual-device}
+### Fresh Install {#fail-virtual-device}
 
 If this is a fresh install and you have not configured your tablet yet, [check logs]({% link _wiki/Documentation/Logs.md %}) for any errors or warnings. If you find any, try finding for a match and its accompanying solution below:
 
-##### Missing uinput device
+#### Missing uinput device
 
 *Symptoms*:
 
@@ -61,7 +61,7 @@ Failed to initialize virtual tablet. (error code ENODEV)
 
 - Reboot your computer.
 
-##### Missing uinput device support
+#### Missing uinput device support
 
 *Symptoms*:
 
@@ -71,7 +71,7 @@ Failed to initialize virtual tablet. (error code ENOENT)
 
 Make sure that your kernel has uinput support. If you are using a custom kernel or builds kernel from source, make sure that you have enabled `CONFIG_INPUT_UINPUT` in your kernel configuration. Refer to your distro's documentation regarding kernel configuration.
 
-##### Missing uinput device permissions
+#### Missing uinput device permissions
 
 *Symptoms*:
 
@@ -83,11 +83,11 @@ Failed to initialize virtual tablet. (error code EACCES)
 
 - [See here]({% link _wiki/Documentation/RequiredPermissions.md %})
 
-#### Non-fresh Install
+### Non-fresh Install
 
 Try disabling your filters one-by-one and see if input finally works.
 
-### Tablet is working but there is no pressure {#artist-mode}
+## Tablet is working but there is no pressure {#artist-mode}
 
 Pressure support is available by changing the output mode of OpenTabletDriver to Artist Mode:
 
@@ -97,13 +97,13 @@ Pressure support is available by changing the output mode of OpenTabletDriver to
 
 See [here](#artist-mode-bindings) for setting up bindings for Artist Mode.
 
-### Mouse button bindings are not working when using Artist Mode {#artist-mode-bindings}
+## Mouse button bindings are not working when using Artist Mode {#artist-mode-bindings}
 
 Artist mode does not support regular mouse buttons. You will need to use artist mode pen bindings in the advanced binding editor instead of regular mouse buttons.
 
-### How to autostart daemon on boot? {#autostart}
+## How to autostart daemon on boot? {#autostart}
 
-#### systemd {#systemd-autostart}
+### systemd {#systemd-autostart}
 
 Make sure that you have enabled the systemd service:
 
@@ -117,7 +117,7 @@ configured correctly to integrate with systemd.
 In such case, refer to your desktop environment's documentation on how to autostart processes on
 login using the instructions [below](#other-inits)
 
-#### Other init systems {#other-inits}
+### Other init systems {#other-inits}
 
 OpenTabletDriver offers no official support for other init systems. Refer to your init system's documentation on how to autostart processes on login. The command to execute on login is:
 
@@ -127,7 +127,7 @@ otd-daemon
 
 > This command should be run as user, not root.
 
-### The cursor feels slow on Artist Mode {#libinput-smoothing}
+## The cursor feels slow on Artist Mode {#libinput-smoothing}
 
 Using Artist Mode will result in some minor smoothing due to libinput's tablet handling.
 
@@ -141,6 +141,6 @@ AttrTabletSmoothing=0
 
 You should restart the OpenTabletDriver daemon after updating this file.
 
-### Still have problems? {#discord}
+## Still have problems? {#discord}
 
 If you are still encountering problems with OpenTabletDriver, it will be easier to help you over in our [Discord]({{ site.data.links.project.DiscordInvite }}) server. We will guide you in doing certain debugging steps and will give you different instructions to help resolve your problem.