I am using many years CLCL to control clipboard, to show menu it is very convinient to press Shift-Shift keys combination. This feature workd fine for all RADs with previous Gexpert versions, but version 1.38 bloks this keys combination in Tokio.
RAD 10.1.Berlin works fine with Gexpert 1.38.
Unfortunately I have no idea what could cause this problem. Since I don't use that tool, in my installation Alt+C opens the "Component" menu item which is as it should.
Does anything at all happen in your IDE when you press Alt+C?
Alt-C works fine. This issue conserned only Tokio.
I've fixed this issue, for this purpose I recompiled version 1.38 (from May 2016) under Tokio, this version works fine with Shift-Shift.
So, what exactly does not work with the latest version?
To invoke menu from CLCL I have to press quickly Shift two times. This combination works fine with all EMB Studious and other programs, but RAD 10.2 Tokio does not allow to use this combination when latest Gexpert was installed, without GExpert this keys work fine, recompiled GExpert 1.38 also work fine.
OK, I have downloaded and installed CLCL and can reproduce the problem. But for me, it does not work in Delphi 2007, 10.1 and 10.2 (haven't checked the others), if GExperts is active. You said it works in all EMB Studios but 10.2. Could you please verify this?
Yes, you are right, I mean that previous version of the Gexpert (1.38) works fine for all versions of the EMB, but I've just tested the latest 1.38.50 for RAD Berlin and Shif-Shift does not work.
Hello, As i can see this bug is not fixed in the last version?
On Thu, Jul 20, 2017 at 12:48 PM Thomas Mueller twm@users.sf.net wrote:
Related
Bugs:
#43Last GExperts version that works: 2.38-2016-06-05
First GExperts version that doesn't work: 2.38-2016-10-03
The change which caused behaviour apparently is in eChangeCase.pas.
It's probably the keybard hook I installed there to track when the user closes the popup menu using the enter key.
Yes, it's the keyboard hook, disabling it makes the problem go away.
Calling CallNextHookEx from the installed keyboard hook fixed the problem.
If everything else fails, read the doc! :-(
fixed in revision 2423