Changing Wacom settings, like the wacom input area or screen area, when the EasyTab client app is open requires the client to handle it.
Changing display settings (like turning off one display) also requires the client to handle it, since the Wacom context needs to be rebuilt.
In my case, I am currently not handling it. My app needs a restart whenever those two particular cases happen. Not a huge deal, but the other applications I test seem to handle these cases without problems.
I was debating whether to open this issue or not, since this is one of those "Drop the Easy from EasyTab" issues.
The applications I mentioned that handle these cases seem to work when the wacom driver crashes, so I have to assume that they are using the Windows Stylus API. Also, the Wacom sample code is not helpful at all for cases like these.
So I'm thinking that one way forward should be to support the Stylus API and leave the Wacom layer as a fallback for when the Stylus API is not available or when EasyTab is compiled as C99.
This could add a lot of complexity to the code, so it might be a bad idea? I just wanted to write my thoughts somewhere that wasn't email, since this is an open source project. I'm curious to read your thoughts, but feel free to close the issue, since there is no code to show yet :)