diff --git a/OpenTabletDriver.Web/Views/Wiki/Development/AddingTabletSupport.md b/OpenTabletDriver.Web/Views/Wiki/Development/AddingTabletSupport.md new file mode 100644 index 0000000..50fccae --- /dev/null +++ b/OpenTabletDriver.Web/Views/Wiki/Development/AddingTabletSupport.md @@ -0,0 +1,5 @@ +--- +title: Adding Tablet Support +--- + +#### WIP diff --git a/OpenTabletDriver.Web/Views/Wiki/Documentation/Logs.md b/OpenTabletDriver.Web/Views/Wiki/Documentation/Logs.md new file mode 100644 index 0000000..4316f50 --- /dev/null +++ b/OpenTabletDriver.Web/Views/Wiki/Documentation/Logs.md @@ -0,0 +1,23 @@ +--- +title: Logs +--- + +### GUI + +To view logs, click on the `Console` tab. Optionally, change filter from `Information` to `Debug` for more detailed logs. + +To export logs, click `Help` -> `Export diagnostics...` in the top menu bar. + +Sometimes OpenTabletDriver crashes hard. This is usually caused by a bug in OpenTabletDriver. Due to the crash, it will be impossible to retrieve the logs from GUI. In this case, you can find a partial log in the following locations: + +| OS | Location | +| --- | --- | +| Windows | `%appdata%\OpenTabletDriver\daemon.log` | +| Linux | `~/.local/share/OpenTabletDriver/daemon.log` | +| macOS | `~/Library/Application Support/OpenTabletDriver/daemon.log` | + +### Daemon + +The output from daemon is the log. + +On Linux when running daemon via systemd service, the log for daemon is recorded by systemd. To view the log, run `journalctl --user-unit opentabletdriver.service`. diff --git a/OpenTabletDriver.Web/Views/Wiki/Documentation/UdevRules.md b/OpenTabletDriver.Web/Views/Wiki/Documentation/UdevRules.md new file mode 100644 index 0000000..08bea9c --- /dev/null +++ b/OpenTabletDriver.Web/Views/Wiki/Documentation/UdevRules.md @@ -0,0 +1,51 @@ +--- +title: Udev Rules +--- + +Make sure that the installed OpenTabletDriver version is at least **0.6.3.0**. If still not working even with the latest version, refer to the instructions below depending on if you installed OpenTabletDriver via: + +- [Package manager](#package-manager) +- [Built from source](#built-from-source) + +### Package manager + +#### Standard FHS distro + +Run the following script in bash as root: + +```bash +echo "Finding old udev rules..." +for c in /etc/udev/rules.d/9{0,9}-opentabletdriver.rules; do + if [ -f "${c}" ]; then + echo "Deleting ${c}" + rm "${c}" + fi +done + +echo "Finding old kernel blacklist rules..." +if [ -f /etc/modprobe.d/blacklist.conf ]; then + echo "Deleting /etc/modprobe.d/blacklist.conf" + rm /etc/modprobe.d/blacklist.conf +done + +udevadm control --reload-rules && udevadm trigger +``` + +> This script cleans up obsolete udev rules and reloads udev. + +Then update the initramfs: + +| Distro | Command | +| --- | --- | +| Arch Linux | `sudo mkinitcpio -P` | +| Debian/Ubuntu | `sudo update-initramfs -u` | + +For other distros, refer to your distro's documentation on how to update the initramfs. + +#### Non-standard FHS distro + +Refer to your distro's documentation on how to remove udev rules of the name `90-opentabletdriver.rules` or `99-opentabletdriver.rules`. + +### Built from source + +Make sure you built OpenTabletDriver via [these instructions](https://github.com/OpenTabletDriver/OpenTabletDriver#linux) and extracted the generic binary tarball correctly. diff --git a/OpenTabletDriver.Web/Views/Wiki/FAQ/Linux.cshtml b/OpenTabletDriver.Web/Views/Wiki/FAQ/Linux.cshtml deleted file mode 100644 index 583d5fd..0000000 --- a/OpenTabletDriver.Web/Views/Wiki/FAQ/Linux.cshtml +++ /dev/null @@ -1,299 +0,0 @@ -@{ - ViewBag.Title = "Linux FAQ"; -} - -

- Teleporting cursor position -

-
-

- This occurs because another program is reading the tablet at the same time as OpenTabletDriver. - - #68 - -

    -
  1. - Perform the following commands in a terminal - - echo "blacklist wacom" | sudo tee -a /etc/modprobe.d/blacklist.conf - sudo rmmod wacom - -
    2. -
-

-
- -
- -

- Device is currently in use -

-
-

- This occurs typically due to the hid_uclogic kernel module taking priority over OpenTabletDriver. -

-
    -
  1. - Run the following commands, then replug your tablet - - echo "blacklist hid_uclogic" | sudo tee -a /etc/modprobe.d/blacklist.conf - sudo rmmod hid_uclogic - -
    2. -
-
- -
- -
-

- The modules reload after rebooting? -

-

- The solution to this is to rebuild the initramfs. This process varies distro to distro. -

-

- Arch -

-
    - - sudo mkinitcpio -P - -
-

- Debian / Ubuntu -

-
    - - sudo update-initramfs -u - -
-
- -
- -

- Failed to open device streams -

-
-

- This occurs due to a lack of permissions to open a device stream. - It is resolved by creating udev rules that give these permissions. -
- If you installed OpenTabletDriver via your package manager, - you may need to run the following command then replug your tablet. - - sudo udevadm control --reload-rules - -

-

- If this does not work, run the following commands -

- - # Clone the repository, change current directory to the repository - git clone https://github.com/OpenTabletDriver/OpenTabletDriver.git - cd ./OpenTabletDriver - # Generate rules, moves them to the udev rules directory - ./generate-rules.sh - sudo mv ./bin/99-opentabletdriver.rules /etc/udev/rules.d/99-opentabletdriver.rules - # Reload udev rules - sudo udevadm control --reload-rules - # Clean up leftovers - cd .. - rm -rf OpenTabletDriver - -
- -
- -

- Failed to initialize virtual device -

-
-

EACCESS

-

- This occurs usually when the udev rules are not correct, or haven't been reloaded. - Make sure your rules are correct by heading here. -

- - sudo udevadm control --reload-rules - # Skips the step requiring a replug of the tablet. - sudo udevadm trigger - # Helps ensure that OpenTabletDriver uses the tablet correctly. - systemctl --user restart opentabletdriver - -

If the commands above do not resolve your issue, reboot.

- -

ENODEV

-

- Rebooting is the only option here. Your kernel was very likely updated, or some component of - uinput was modified which requires a reboot to resolve. -

- -

ENOENT

-

- This error occurs when the CONFIG_INPUT_UINPUT kernel option is disabled. Make sure it is activated in - your kernel config.
-

-

Gentoo

-

- Check the option CONFIG_INPUT_UINPUT in /usr/src/linux.config. If it is not enabled, use the following steps -

- - cd /usr/src/linux - sudo make menuconfig - -

- Having done that, select y (for always active) or m (for building as a module) for the option in "Device Drivers - ---> - Input Device Support ---> Miscellaneous devices ---> User level driver support" and rebuild the kernel. -

-

Other Distros

-

- Refer to your distribution's documentation regarding kernel configuration to enable this option. -

-
- -
- -

This doesn't work after rebooting?

-
-

- This is probably due to your kernel not having uinput built in, either build your kernel with uinput - support or use a different kernel. -

-
- -
- -

- Poor performance with NVIDIA -

-
-
    -
  1. Disable Force full composition pipeline in the NVIDIA settings panel.
    2. -
-
- -
- -

- Stuck cursor in osu!lazer (Wayland) -

-
-
    -
  1. Make sure you set the SDL_VIDEODRIVER to wayland.
    2. -
- - # Export the environment variable - export SDL_VIDEODRIVER=wayland - # Start osu! lazer via the AppImage assuming its in the working directory - ./osu.AppImage - -
- -
- -

- CTL-x100 is not detected -

-
-

- CTL-x100 tablets boots in Android mode instead of PC mode in some rare cases. To fix this, press - the outer 2 express keys for 3-4 seconds until the LEDs change brightness. This toggles the tablet's operating mode - between PC (high LED brightness) and Android mode (low LED brightness). -

- -
- -
- -

- X11/Wayland Session not detected -

-
-

X11 (systemd)

-
-

- Your .xinitrc is likely configured improperly and the DISPLAY environment - variable isn't set for systemd.
- Proper configuration for the .xinitrc file can be found - here.
- - Note: The fix below is just a quick and dirty fix to get OpenTabletDriver running and should - instead be resolved as above. - -

-
    -
  1. - Create an override file - - # Opens with whatever program is set to $EDITOR - systemctl --user edit opentabletdriver.service - -
    2. -
  2. - Add this block below the first 2 lines of the file, then save and exit - - [Service] - Environment=DISPLAY=:0 - -
    3. -
  3. - Finally, run the following commands - - # Reload the systemd user daemon - systemctl --user daemon-reload - # Start the OpenTabletDriver daemon service (restarts if already running) - systemctl --user restart opentabletdriver.service - -
    4. -
-
- -

Wayland (systemd)

-
-
    -
  1. - Create an override file - - # Opens with whatever program is set to $EDITOR - systemctl --user edit opentabletdriver.service - -
    2. -
  2. - Add this block below the first 2 lines of the file, then save and exit - - [Service] - Environment=WAYLAND_DISPLAY=:0 - -
    3. -
  3. - Finally, run the following commands - - # Reload the systemd user daemon - systemctl --user daemon-reload - # Start the OpenTabletDriver daemon service (restarts if already running) - systemctl --user restart opentabletdriver.service - -
    4. -
-
-
- -
- -

- Enabling pressure using Artist Mode -

-
-

- Pressure support is available by changing the output mode of OpenTabletDriver to Artist Mode. - To do this, follow below. -

-
    -
  1. Change output mode (at the bottom left of OpenTabletDriver) to Artist Mode.
    2. -
  2. Remove the Tip Binding in the Pen Settings panel by clicking the 3 dots, then pressing clear.
    3. -
  3. Save your settings and try drawing in an applicantion that supports pressure.
    4. -
-
diff --git a/OpenTabletDriver.Web/Views/Wiki/FAQ/Linux.md b/OpenTabletDriver.Web/Views/Wiki/FAQ/Linux.md new file mode 100644 index 0000000..6c2388f --- /dev/null +++ b/OpenTabletDriver.Web/Views/Wiki/FAQ/Linux.md @@ -0,0 +1,166 @@ +--- +title: "Linux FAQ" +--- + +### My tablet is not detected? + +#### Tablet Connection + +Make sure that the tablet is actually plugged in to your computer properly. Check this by running `lsusb` in a terminal or by watching the output of `dmesg` or `udevadm monitor` when plugging in the tablet. + +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. + +Once the tablet is connected properly, verify if your tablet is in the list of supported tablets [here](/Tablets). 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.](/Discord) +- [Make your own tablet configuration.](/Wiki/Development/AddingTabletSupport) + +#### Troubleshooting + +If your tablet is connected properly and is supported, but is still not detected, [check logs](/Wiki/Documentation/Logs) for any errors or warnings. If you find any, try finding for a match and its accompanying solution below: + +##### UCLogic kernel module is loaded {#hid_uclogic} + +_Symptoms_ + +``` +Another tablet driver found: UC Logic +``` + +``` +ArgumentOutOfRangeException: Value range is [0, 15]. (Parameter 'value) +``` + +[_Solution_](/Wiki/Documentation/UdevRules) + +##### Insufficient permissions {#udev} + +_Symptoms_ + +``` +Not permitted to open HID class device at /dev/hidrawX +``` + +[_Solution_](/Wiki/Documentation/UdevRules) + +#### Tablet-specific Troubleshooting + +##### CTL-x100 + +It is possible for CTL-x100 tablets to boot in Android mode (the mode they use when interfacing with android devices like phones) instead of PC mode in some rare cases. To fix this, press +the outer 2 express keys for 3-4 seconds until the LEDs change brightness. This toggles the tablet's operating mode +between PC (high LED brightness) and Android mode (low LED brightness). + +> Note: If you are sure your tablet is in PC mode, please follow the general instructions [here](#my-tablet-is-not-detected). + +### Tablet is detected but not working? + +#### Fresh Install {#fail-virtual-device} + +If this is a fresh install and you have not configured your tablet yet, [check logs](/Wiki/Documentation/Logs) for any errors or warnings. If you find any, try finding for a match and its accompanying solution below: + +##### Missing uinput device + +_Symptoms_ + +``` +Failed to initialize virtual tablet. (error code ENODEV) +``` + +_Solution_ + +Reboot your computer. + +##### Missing uinput device support + +_Symptoms_ + +``` +Failed to initialize virtual tablet. (error code ENOENT) +``` + +_Solution_ + +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 + +_Symptoms_ + +``` +Failed to initialize virtual tablet. (error code EACCES) +``` + +[_Solution_](/Wiki/Documentation/UdevRules) + +#### Non-fresh Install + +Try disabling your filters one-by-one and see if input finally works. + +### My cursor is stuck in osu!lazer (Wayland) {#osu-lazer-broken-input-wayland} + +Make sure you set the `SDL_VIDEODRIVER` to `wayland`. Some examples: + +```bash +env SDL_VIDEODRIVER=wayland ./osu.AppImage +``` + +```bash +env SDL_VIDEODRIVER=wayland osu-lazer +``` + +### Tablet is working but there is no pressure {#artist-mode} + +Pressure support is available by changing the output mode of OpenTabletDriver to Artist Mode: + +- Change output mode (at the bottom left of OpenTabletDriver) to Artist Mode. +- Remove Tip Binding in the Pen Settings panel by opening advanced binding editor (press '...' next to the binding), then press "Clear". +- Save your settings and then try drawing in an application that supports pressure. + +You will also need to use artist mode mouse bindings in the advanced binding editor instead of regular mouse buttons. Regular mouse buttons are _not_ supported in artist mode. + +### The daemon does not start on boot + +#### systemd {#systemd-autostart} + +Make sure that you have enabled the systemd service: + +```bash +systemctl user enable opentabletdriver.service --now +``` + +If this does not work, this means that the desktop environment is not configured correctly to integrate with systemd. In such case, refer to your desktop environment's documentation on how to autostart processes on login. The command to execute on login is: + +```bash +otd-daemon +``` + +#### Other init systems + +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: + +```bash +otd-daemon +``` + +> This command should be run as user, not root. + +### The cursor feels slow on Artist Mode + +Using artist mode will result in some minor smoothing due to libinput's tablet handling. + +To disable this smoothing, add the contents below to `/etc/libinput/local-overrides.quirks`: + +```ini +[OpenTabletDriver Virtual Tablets] +MatchName=OpenTabletDriver* +AttrTabletSmoothing=0 +``` + +You should restart the OpenTabletDriver daemon after updating this file. + +### I have tried these solutions, but my problem still persists! {#discord} + +If you are still encountering problems with OpenTabletDriver, +it will be easier to help you over in our [Discord](/Discord) server. We will guide you in doing certain debugging steps and will give you different instructions to help resolve your problem. diff --git a/OpenTabletDriver.Web/Views/Wiki/FAQ/Windows.cshtml b/OpenTabletDriver.Web/Views/Wiki/FAQ/Windows.cshtml index 336c91f..30ffbb5 100644 --- a/OpenTabletDriver.Web/Views/Wiki/FAQ/Windows.cshtml +++ b/OpenTabletDriver.Web/Views/Wiki/FAQ/Windows.cshtml @@ -2,70 +2,113 @@ ViewBag.Title = "Windows FAQ"; } -

- Supported tablet not detected +

+ My tablet is not detected?

- This is most commonly the result of manufacturer driver leftovers.
+ Please check that your tablet is actually plugged in to your PC. Windows by default will indicate when a device is plugged in + with a sound.
If you do not get this sound consider replacing the cable (make sure the cable supports both power and data + transfer).

+ + Once you are sure that your tablet is connected to your computer, ensure that your specific tablet make and model is supported by checking our list of supported tablets here.
+ + We currently do not support tablets that connect directly to a computer via Bluetooth, + and there is only limited support for tablets that use wireless USB receivers, so please make sure your tablet is connected via cable. +

+

It is a supported tablet, but still doesn't detect?

+

+ Please make sure that you have no other tablet drivers on the system. To ensure your system is clean, follow the instructions for our Tablet Driver Cleanup Utility, then resume here.

+ + Please check if your tablet requires WinUSB here (it will say in the notes). If it does, follow the
+ instructions and return here. Continue below for troubleshooting instructions if your tablet still isn't detected.

+ + If you are running OpenTabletDriver.UX, navigate from the top to the Console tab, if you are running the daemon standalone, look for a log that resembles the following:
+ +

Tablet driver interefence
+ + + Another tablet driver found: <name> + + If you see this log message you should follow the instructions for TabletDriverCleanup + if you haven't already, making sure to say yes to everything. If the log entry is still there after following the instructions and restarting OTD, try + joining our support Discord for further help.
+ +
Invalid WinUSB driver installation state.
+ + Failed to open file handle to WinUSB interface + SafeHandle cannot be null. (Parameter 'pHandle') + + This is usually resolved when you restart your PC.

+ + If nothing above applies, remove %localappdata%/OpenTabletDriver or the contents of the userdata folder next to the binaries (if applicable).
+ If you still need more help after this, join our Discord and give us a shout in the #support-windows channel, mentioning what you have tried. +

+ +

It is not a supported tablet, what can I do about that?

+

+ If you want to add support for your tablet on your own, feel free to look at a similar configuration on our GitHub and our configuration documentation.
+ If you would like help with supporting your tablet, or would prefer us to do it, join our Discord and create a post in #config-creation or a support channel.

-
    -
  1. - Uninstall any tablet drivers that are currently installed.
    - - Deleting files is not a proper method to uninstall drivers, - it will cause issues. - Use the Settings app or Control Panel instead. - -
    2. -
  2. - Use the WinUSBCleanup - script to automatically clean up any leftovers that uninstallers failed to clean up. -
    3. -
-

- Teleporting cursor position +

+ My tablet is detected, but my settings don't work.

- This occurs because another tablet driver is sending input. To resolve this, - uninstall all other tablet drivers on your computer, then replug your tablet. + If your area/bindings are not working correctly despite detection, try following our troubleshooting steps below.

+ + Make sure that you have saved your settings by pressing the save button in the bottom right of the OpenTabletDriver interface.

+ + If you have done the above and your settings still do not apply then make sure that you don't have other drivers installed on your computer, + you can remove these by running and following the instructions for TabletDriverCleanup, + come back here.

+ + If your cursor is teleporting you usually have another driver installed or you have broken settings, you can resolve the former by following the former with + TabletDriverCleanup and you can solve the latter with + file > reset to defaults and clicking save.

+ + If the issue is still unresolved after trying the instructions above, please join our Discord for extra assistance.

-

- Input does not work in osu! +

+ My cursor doesn't function correctly in osu!

- Disable Map raw input to osu! window in the ingame settings.

- OpenTabletDriver has since v0.4.0 supported Raw Input as it uses the Windows SendInput API to position the cursor.
- Therefore, it is not necessary to disable raw input itself. + Either disable Raw Input in the game settings entirely or disable Map raw input to osu! window + in the ingame settings and make sure that sensitivity is set to 1x.
+

+ Note: OpenTabletDriver has since v0.4.0 supported Raw Input as it uses the Windows SendInput API to position the cursor. + Therefore, it is not necessary to disable raw input itself, but it provides no merit on tablets to have it enabled. +

- Windows Ink pressure support + How do I get pressure support?

- OpenTabletDriver has many plugins that implement different features. WindowsInk is - one of these plugins, as given in the plugins name, it allows for use of the Windows Ink pressure api. - To use it, follow below. + You can get Windows Ink pressure support with the Windows Ink plugin that is accessible through the Plugin Manager. To use it, follow the instructions below.

-
    +
    1. Install VMulti Driver (This is NOT VMultiMode)
    2. Follow the instructions from the WindowsInk wiki
    3. Make sure that the application you are trying drawing in is set to WindowsInk/Windows 8+ Mode and the brush you are using has pressure support!
    +

    + If you already have a different installation of VMulti it is recommended that you first run + TabletDriverCleanup to avoid any potential conflicts. +

    Note: Recently, a change in Windows made it so Windows Ink's and normal Mouse's cursor position is handled separately. This makes it so your cursor will appear to "jump" when switching from tablet to mouse while using Windows Ink output modes. @@ -75,25 +118,46 @@

    +

    + What is convert_to_portable.bat? +

    +
    +

    + This file moves OpenTabletDriver's settings to a folder called userdata next to OpenTabletDriver itself + rather than being stored in %localappdata%\OpenTabletDriver. This allows OpenTabletDriver to be completely portable, + all in one folder. +

    +
    + +
    +

    - Stuck at connecting to Daemon + It says it fails to connect to the daemon?

    - This is usually caused by one of two things. Either you didn't follow the installation guide correctly - or the settings file is corrupted. To remedy this case follow this below. + This can be caused by a few different problems. Primarily, this will result from incorrectly following the installation guide on installation.

    + + If you are sure that you have followed the installation guide correctly, or this issue just began occurring after an update to OTD, then it is likely that you have + broken settings or outdated plugins installed. You can remedy this with the below.

    1. Press Win + R and type in %localappdata%\OpenTabletDriver
    2. Delete or move the settings.json file from inside this folder.
    3. If this persists after also remove the Plugins folder.
    +

    + If you have a userdata folder next to the binaries of OpenTabletDriver, you will need to remove the files above from that folder instead.

    + + If you still can't get it working after the solutions above please join our Discord. + It might be a completely different issue! +

    - Open at startup + How do I make OTD start automatically when I boot my PC?

    @@ -113,35 +177,35 @@

    -

    - OpenTabletDriver gives an Administrator warning +

    + Plugin Manager won't open/I get a warning on startup?

    - When Starting OpenTabletDriver you may get an error warning you about Administrator Permissions. OpenTabletDriver - shouldn't be run as Administrator. This causes the plugin manager, FAQ page and Tablet debugger to not work along with - other features. + When Starting OpenTabletDriver you may get an error warning you about Administrator Permissions. OpenTabletDriver + should NEVER be run as Administrator or with Administrator permissions. This causes the plugin manager, FAQ page, and Tablet debugger to not work, and can interfere with several + other features.

    + + The following instructions should fix your issue under normal circumstances, but if you're using the (disabled in a fresh windows install by default) account called "Administrator", + usually because you're using a "custom" iso (unofficial version of Windows, also sometimes referred to as a "debloated windows") install, these instructions will not work for you. We generally recommend against using altered or 3rd party versions of windows, as OTD is likely to not be the only software adversely affected by the changes these custom ISOs make.

    1. Press the Windows key and search User Account Control.
    2. Move the slider to one of the top 2 options.
    3. Click OK, then restart your computer.
    -

    - If this does not solve the issue, check that you are not using the "Administrator" named account as it overrides User Account - Control. -

    - Blank window or crashing when opening OpenTabletDriver + Why is my interface completely blank?

    - This can be caused by RivaTuner Statistics Server attempting to hook onto OpenTabletDriver, preventing the UX - from responding due to failed hooks. If you use this application, make sure it doesn't hook onto OpenTabletDriver. + If you are experiencing random crashes with no warning, or the interface is completely blank and/or not accepting input, and you have RiverTuner Statistics Server + installed, it may be hooking into OpenTabletDriver and preventing the UX from functioning correctly. + If you use this application, make sure it doesn't hook onto OpenTabletDriver by blacklisting it in RiverTuner's settings.

    1. Open RivaTuner Statistics Server.
      2. @@ -154,7 +218,7 @@

      - Using VMulti to play Valorant + Cursor doesn't move with Valorant open?

      @@ -182,4 +246,5 @@ There is no fix this, as even Logitech G Hub, Razer Synapse, HawkuTD, DevocubTD, and even XP-Pen, Huion, Gaomon, Veikk drivers are affected without exceptions. As long as the input source is not a real physical mouse, Vanguard will impose such quirks intentionally.

      -
      \ No newline at end of file +
    + diff --git a/OpenTabletDriver.Web/Views/Wiki/Index.cshtml b/OpenTabletDriver.Web/Views/Wiki/Index.cshtml index c9e4d0a..97d56d1 100644 --- a/OpenTabletDriver.Web/Views/Wiki/Index.cshtml +++ b/OpenTabletDriver.Web/Views/Wiki/Index.cshtml @@ -23,6 +23,9 @@
  1. Writing OpenTabletDriver Configurations
    2. +
  2. + Adding Tablet Support +
    3. -
\ No newline at end of file + diff --git a/OpenTabletDriver.Web/Views/Wiki/Install/MacOS.cshtml b/OpenTabletDriver.Web/Views/Wiki/Install/MacOS.cshtml index 7e9b0bb..33fb06c 100644 --- a/OpenTabletDriver.Web/Views/Wiki/Install/MacOS.cshtml +++ b/OpenTabletDriver.Web/Views/Wiki/Install/MacOS.cshtml @@ -18,3 +18,10 @@ Run the OpenTabletDriver app. + +
+ +

+ Post-Installation +

+

Take a look at the FAQ if you encounter any problems.

diff --git a/OpenTabletDriver.Web/Views/Wiki/Install/Windows.cshtml b/OpenTabletDriver.Web/Views/Wiki/Install/Windows.cshtml index 35850d4..672a10f 100644 --- a/OpenTabletDriver.Web/Views/Wiki/Install/Windows.cshtml +++ b/OpenTabletDriver.Web/Views/Wiki/Install/Windows.cshtml @@ -77,4 +77,11 @@
  • Find your tablet on the device list and the interface.
  • Click Replace Driver.
    • - \ No newline at end of file + + +
    + +

    + Post-Installation +

    +

    Take a look at the FAQ if you encounter any problems.

    diff --git a/OpenTabletDriver.Web/Views/Wiki/WikiMarkdownPage.cshtml b/OpenTabletDriver.Web/Views/Wiki/WikiMarkdownPage.cshtml index 7f705e3..4fc5974 100644 --- a/OpenTabletDriver.Web/Views/Wiki/WikiMarkdownPage.cshtml +++ b/OpenTabletDriver.Web/Views/Wiki/WikiMarkdownPage.cshtml @@ -16,25 +16,16 @@ width: 65%; } - .markdown-content > table { - margin-left: 1rem; - width: calc(100% - 1rem) - } - + .markdown-content > h5, + .markdown-content > h4, .markdown-content > h3 { - margin-bottom: .5rem - } - .markdown-content > h4 { - margin-left: 1rem - } - .markdown-content > p { - margin-left: 1rem + margin-bottom: 1rem; } .markdown-content > blockquote > p { color: #888; font-size: small; - margin-left: 2rem + margin-left: 1rem; } } diff --git a/OpenTabletDriver.Web/Views/Wiki/_WikiLayout.cshtml b/OpenTabletDriver.Web/Views/Wiki/_WikiLayout.cshtml index e057c47..60a41e3 100644 --- a/OpenTabletDriver.Web/Views/Wiki/_WikiLayout.cshtml +++ b/OpenTabletDriver.Web/Views/Wiki/_WikiLayout.cshtml @@ -19,7 +19,7 @@
    -
    +
    Contents
      @@ -51,4 +51,4 @@ @await RenderSectionAsync("Scripts", required: false) - \ No newline at end of file +