You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the biggest feature that exists only in the Windows native viewer, and it exists only in that viewer because I tried and failed to implement it in the Windows/Java TurboVNC Viewer. However, after having implemented Wacom support in the Mac/Java TurboVNC Viewer, I have some new ideas regarding how to make it work in the Windows/Java TurboVNC Viewer. Fortunately, I still have the code from the failed experiment.
The text was updated successfully, but these errors were encountered:
Furthermore, it seems as if we will need to use the Windows Ink API, rather than Wintab, in order to support newer Wacom tablets. It may also be necessary to use the Wintab API for older tablets, perhaps as a fallback mechanism. This would all happen within the Windows TurboVNC Helper.
dcommander
changed the title
Wacom tablet support in the Windows/Java TurboVNC Viewer
Wacom tablet support in the Windows/Java TurboVNC Viewer + support newer Wacom tablets on Windows
Aug 29, 2019
Removing this feature from the Windows TurboVNC Viewer Migration milestone. That milestone is meant to reflect potential feature regressions from dropping the Windows native TurboVNC Viewer in favor of the Windows/Java TurboVNC Viewer. Since newer Wacom tablets aren't supported in the current Windows TurboVNC Viewer anyhow, and since Wintab has a lot of other problems, the current lack of tablet support in the Windows/Java TurboVNC Viewer isn't a major feature regression.
This is the biggest feature that exists only in the Windows native viewer, and it exists only in that viewer because I tried and failed to implement it in the Windows/Java TurboVNC Viewer. However, after having implemented Wacom support in the Mac/Java TurboVNC Viewer, I have some new ideas regarding how to make it work in the Windows/Java TurboVNC Viewer. Fortunately, I still have the code from the failed experiment.
The text was updated successfully, but these errors were encountered: