pecan

Fixed svn 13832. Garbage in unintialized variable causing the first mouse right-click to be interpreted as a mouse drag. A missing event.Skip() was causing the request for context popups to be ignored (Linux). On high DPI monitors some mouse right clicks were missed because mouse jitter was being interpreted as a beginning drag.

Fixed svn 13832. Garbage in unintialized variable cause the first mouse right-click to be interpreted as a mouse drag. A missing event.Skip() was causing the request for context popups to be ignored (Linux). On high DPI monitors some mouse right clicks were missed because mouse jitter was being interpreted as a beginning drag.

Right clic does not work the 1st time in the managment window

Fixed svn 13832. Garbage in unintialized variable cause the first mouse right-click to be interpreted as a mouse drag. An missing event.Skip() was causing the request for context popups to be ignored (Linux). On high DPI monitors some mouse right clicks were missed because mouse jitter was being interpreted as a beginning drag.

* DragScroll: Fix missed first Manager mouse Right click.

Thanks for the help chasing this down guys. The cause appears to be (not a missing event.Skip()), but an uninitialized boolean variable that had an int(30) in it. After the first right-click in the management tree, the var got it's first true/false value resulting in correct performance. That would also explain why the difference in compilers would provoke or hide the problem. While I'm here, some changes for high DPI need examination. I'll work with this for awhile to make sure I'm not "halluci...

Thanks for the help chasing this down guys. The cause appears to be (not a missing event.Skip()), but an uninitialized boolean variable that had an int(30) in it. After the first right-click in the management tree, the var got it's first true/false value resulting correct performance. That would also explain why the difference in compilers would provoke or hide the problem. I'll work with this for awhile to make sure I'm not "hallucinating".

Thanks for the help chasing this down guys. The cause appears to be (not a missing event.Skip()), but an uninitialized boolean variable that had an int(30) in it. After the first right-click in the management tree, the var got it's first true/false value resulting correct performance. I'll work with this for awhile to make sure I'm not "hallucinating".