A bug... or not a bug... thats the point... Accelerators

forum.gupta.bugreport (2005-2010)
Pedro Vazquez

A bug... or not a bug... thats the point... Accelerators

Post by Pedro Vazquez » 06 Oct 2005, 14:49

 Posted by:  Pedro Vazquez 

Hi there...

I have a sample application with a MDI and two forms... in each of the
forms I have a pushbutton and a datafield...
Both pushbuttons have the same accelerator key ( Page Up ). The MDI
creates the mdifrm1 first and the mdifrm2... the accelerator for the
pushbutton in the mdifrm1 works... but when I have the focus on the mdifrm2
the accelerator stills references to the other control...
See the sample attached and you'll understand...

Is there a way to change this behaviour?... Is this a bug?...

Thanks in advance.

Pedro E. Vazquez
Buenos Aires Software S.A. -- www.bas.com.ar
Argentina

You do not have the required permissions to view the files attached to this post.

Pedro Vazquez

Re: A bug... or not a bug... thats the point... Accelerators

Post by Pedro Vazquez » 06 Oct 2005, 16:49

 Posted by:  Pedro Vazquez 

I find a workaround... not elegant but it does the work...
On SAM_Activate of the forms I create or destroys the accelerators...

Sample attached in case anyone need it...

Thanks anyway.

Pedro E. Vazquez
Buenos Aires Software S.A. -- www.bas.com.ar
Argentina

You do not have the required permissions to view the files attached to this post.

Jim McNamara

Re: A bug... or not a bug... thats the point... Accelerators

Post by Jim McNamara » 07 Oct 2005, 14:44

 Posted by:  Jim McNamara 

AFAIK, that's how it's always worked. The 1st created instance of an
accelerator is the one that gets attention.

Pedro Vazquez

Re: A bug... or not a bug... thats the point... Accelerators

Post by Pedro Vazquez » 07 Oct 2005, 15:30

 Posted by:  Pedro Vazquez 

Jim,

I thought they where private of the form with the focus on...
We had an MDI with multiple forms derived form a class with toolbarbuttons
with Keyboard Accelerators assigned... and only the form with the focus get
the "accelerator call"... it seems to be private of each form.
The only Keyboard Accelerators that we can use ( at least in the "Attribute
inspector" ) are 'F1' ... 'F12', 'Enter' and 'Esc'... but we wanted to use
'PageUp', 'PageDown' .... etc. The only way to assign it is using
VisWinLoadAccelerator...

Get my point???

Sample attached... with a F5 Keyboard accelerator ( from "Attribute
inspector") and 'PageUp' accelerator from VisWinLoadAccelerator...

Regards

Pedro.

You do not have the required permissions to view the files attached to this post.

Return to “gupta.bugreport”

Who is online

Users browsing this forum: [Ccbot] and 0 guests