Page 1 of 1

Scroll not working

Posted: Sat 11. Jan 2020, 14:31
by mkad2020
Hello,
I have an issue with my Wacom CTH - 490 The driver installed are the latest
The scroll button works only for move up and move down, But doesn't work for scroll right\left.
My OS is Windows 10 Pro 1909.

- Unchecked use ink windows on wacom properties
- I Tried unistall and reinstall photoshop (2019 and 2020) with the PSUserConfig
- I Tried with different wacom driver and I found some versions that run properly the scroll, but unfortunately they have other problems with camera raw or zoom in\out.
- I Tried to install all (photoshop and wacom driver\software) in other computer and i have the same issue.

So, the issue persist. Do you have any suggestions?

Thanks

Re: Scroll not working

Posted: Mon 13. Jan 2020, 08:42
by wacom5
Hi,
Does this happen only with Photoshop or with other apps as well?
Which scroll setting are you using? Just scroll or Pan/Scroll?
We might need to collect more data to report this to the driver team so could you please contact our support? https://support.wacom.com

Re: Scroll not working

Posted: Tue 14. Jan 2020, 21:48
by mkad2020
Hi,
Thanks for the answer!
The issue are present when I use my pen for scrool.
Before when I held down the first button of the pen, the image scrolled towards where I was moving.
The scroll issue are the same with other app.
The wacom configuration are the default, except for the right keys button (express key) that are configured as zoom in and zoom out.
The touch function are disabled.
Thanks

Re: Scroll not working

Posted: Wed 15. Jan 2020, 08:51
by wacom5
Thank you for the details. I can reproduce the issue. I will report this to the driver team.

Re: Scroll not working

Posted: Thu 16. Jan 2020, 17:52
by mkad2020
Hi,
I await news from you.
Many thanks

Re: Scroll not working

Posted: Sat 1. Feb 2020, 10:34
by mkad2020
Hello,
Any news from the support regarding the issue?
Thank you

Re: Scroll not working

Posted: Mon 3. Feb 2020, 09:16
by wacom5
The driver team was also able to reproduce the issue. It will be fixed in a future update - not sure when.