When I updated to Express 266 I found a significant lag when I use ALT_A (or other ALT letters) as an ACCELKEY for a DCPUSHBUTTON. Clicking on button does not lag, neither does using ALT_PGDN as the ACCELKEY.
I am uploading an example program.
Significant lag with DCPUSHBUTTON ACCELKEY in Express 266
Significant lag with DCPUSHBUTTON ACCELKEY in Express 266
- Attachments
-
- Example.zip
- (1.58 KiB) Downloaded 824 times
Re: Significant lag with DCPUSHBUTTON ACCELKEY in Express 26
Thanks for the example.
I can confirm that this is a problem with build 266.
There was a change put into build 266. _DCGETBX.PRG, line 5436.
A customer complained that he had a hot key that didn't force a lost focus.
We determined that a DC_CompleteEvents() would fix that.
Apparently, it has a side effect.
I decided that in the next build I will remove the DC_CompleteEvents() and require that customer to add it to his code block instead.
This way it solves your problem and his problem.
This is what you need to do as a workaround:
Comment out line 5436 in c:\exp20\dclipx\_dcgetbx.prg
Rebuild DCLIPX.DLL by running BUILD20.BAT or BUILD19_SL1.BAT
I can confirm that this is a problem with build 266.
There was a change put into build 266. _DCGETBX.PRG, line 5436.
A customer complained that he had a hot key that didn't force a lost focus.
We determined that a DC_CompleteEvents() would fix that.
Apparently, it has a side effect.
I decided that in the next build I will remove the DC_CompleteEvents() and require that customer to add it to his code block instead.
This way it solves your problem and his problem.
This is what you need to do as a workaround:
Comment out line 5436 in c:\exp20\dclipx\_dcgetbx.prg
Rebuild DCLIPX.DLL by running BUILD20.BAT or BUILD19_SL1.BAT
The eXpress train is coming - and it has more cars.
Re: Significant lag with DCPUSHBUTTON ACCELKEY in Express 26
Great. Thank you.