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

[Gerard DURAND]

OS: Windows 11 updated in march 2026
With my svn 13822 build, the first time I try a right click in the management window, on a project or a file, nothing happens. But if I click again it works as expected: I see a popup window with correct sub-menus. After that, each right click works as expected. It's only the first time that nothing happens.
Note that this behavior does not happen with official nightly 13810.
Main differences: I use last updated Msys2 gcc 15.2 and tools, and wxWidgets 3.3.2 (it aws also the case with 3.3.1), though official nightly use Winlibs distribution (gcc 15.1) and wxWidgets 3.2.8.

[Miguel Gimenez]

r13822 works OK here:

• W7
• wx3.2.10
• 32-bits
• gcc 8.1.0 from MinGW-w64

Also works OK on:

• Mint 18.2
• wx3.0.2
• 32-bits
• gcc 5.4.0

[Miguel Gimenez]

I have just tested Xaviou's last nightly (CB_20260312_rev13823_wx33_win64) with wxWidgets 3.3.2 and works OK. I do not know if he uses MSYS.

[Gerard DURAND]

I have also tested Xaviou's nightly (Win 64, wxWidgets 3.3.2) and effectively it has not the problem I have. So, he uses probably a different compiler set (binary are not compatible). This problem is not very important, just a bit annoying. But I have no idea how to track and identify it.

[Miguel Gimenez]

You can start checking if ProjectManagerUI::OnRightClick() is executed at all on the first click. I just insert a wxBell() for this kind of tests.

[Gerard DURAND]

A few tries but I don't really understand what's happen :
If I insert wxBell(); at line :

• 1465: no bell rings at all. as if it never pass here !
• 1532: it rings only when the menu is displayed, normal
• 1108: it rings only when the menu is displayed when I click on main workspace, normal
• 914: it rings only when the menu is displayed, normal

PS: I have sent a PM to ollydbg because he uses also wxWidgets 3.3.2 and last Msys2

[ollydbg]

I'm using the rev13826, plus I have some patches locally mainly on the codecompletion plugins.

I'm under Windows 10 64bit, and I used the latest GCC version(15.2) in msys2/mingw64 platform. My wxWidgets version is 3.3.2.

I don't have such issue.

[pecan]

I've also experienced this problem. (Windows 11; CB svn 13831; wx328).
Could those having the disappearing mouse right-click problem please list the plugins they are using along with the plugins version.
This problem is usually caused by a missing "event.Skip();" statement in a plugin event.
A list of plugins to inspect would be very useful.

[Gerard DURAND]

After disabling all the plugings and re-enabling them one by one, I think the problem I have comes from the dragscroll plugin: when desactivated, no problem, when activated the problem is there (of course, on my msys2 config, because it seems that with other compilers there is not systematically this problem). To test this, each time, I quit C::B then restart it to be sure that I have this 1rt time behavior.

[ollydbg]

When I looked at the source code of the dragscroll.cpp, especially in the class MouseEventsHandler, do you mean that before each return statement, there is a call to the event.Skip();?

I see some functions do not have that function call.

[pecan]

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 "hallucinating".

[Gerard DURAND]

Cool. Hope to test this work soon!

[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.

[Gerard DURAND]

Thanks. As far I have tested, it's OK now.