PureBasic Forums - English

PMV wrote: Additional, you can disable this button manually for every
program, where it is not allowed to be.

Yes... it was done already for Chrome or Opera. Didn't I wrote that already? - Thanks but I already know how to workaround by teaching my users (if they are willing to hear and finally tell me that they are at least using teamviewer). It would still be way better if PB and TeamViewer would not conflict from scratch because I learned already it's sometimes not that easy to get the information you need.


Plan B:
*) Ask user if he is using QuickConnect in TeamViewer
*) Ask him again if he is using at least TeamViewer
*) Tell him what QuickConnect is and that this could cause issues
*) Tell the user it's not my fault
*) Try to give him instructions how to disable it
*) *sigh*

Plan A:
*) Ask Fred if it's easy to avoid that issue at PB side. If not it's ok. But if it's not that complicated this could probably save lot of time and would be nerfe-sparing.

At least it wasted already a lot of my own time so this bug-report is here now for others that might find it via the search (which probably is not necessary if there is a not too complicated way to avoid on PBs side).

After investigation, TeamViewer hook the window callback and doesn't call the previous installed callback properly. This is a major bug in TeamViewer, as every software which use the 'WM_NCDESTROY' message when a window close won't have their code called (as it is the case in PB, where cleanup are done). That's probably why chrome & co fails with TeamViewer. Feel free to forward the bug to them. I moved the bug for further references.

This is a major bug in TeamViewer as every software which use the 'WM_NCDESTROY' message when a window close won't have their code called

Thanks for your investigation.