1) - When I try that I get "There is no method in an ancester class to be overridden". (it's not virtual...?)

2) - Tried that with my current message handling code and nothing happens.

My object is:

TWinControl -> TMScrollingWinControl -> TCheckBook

I'm trying to make sure that menu shortcuts happen even when my control has focus.

I can't seem to override the DoKeyUp on the TWinControl. I looked in the LCL and it's not listed as virtual. If I don't use "override" the routine is never called. If I do, it gives me the error listed above by 1).

I also tried handling the message as before, and adding "DoKeyUp(Message)" at the end if I haven't handled it, but nothing happens.

I tried handling the message, leaving result zero and calling inherited in the message handler to no avail.

Can someone point me to a sample component in the LCL that implements something like this?

Thanks,
Tony

1. You can override DoKeyUp instead.
2. Did you add an 'inherited'?

Mattias

I'm handling a:

procedure WMKeyUp(var Message: TLMKeyUp); message LM_KEYUP;

How can I only make use of the keys that I want, and pass the remaining on to the parent component(s)?

I just want to grab arrows, without interfering with menu keyboard shortcuts.

Currently I have the following within the procedure:

if Message.CharCode = VK_UP then begin
   ... do my stuff ...
    exit;
end;

Which works great for handling the VK_UP, but it's not passing on the ones I don't handle.

Thanks,

Tony

Meaning, if my custom control doesn't handle it the form gets a chance and the app finally. My real problem is that menu hotkeys don't function if my custom controls have focus and grab the key message.

I'll try to override the KeyPress and see what happens. Thanks.

-Tony

Sorry. I ment KeyDown, KeyUp and KeyPress.
To mark the "key" as used, set it to VK_UNKNOWN.

What do you mean with "on to the parent component(s)"?

Mattias

Mmm... okay then let me rephrase.

I have a custom control that when selected doesn't allow the accelerators to work. It's a TWinControl descendant.

I've removed all references to grabbing key events, etc from my component and it _still_ doesn't let menu shortcuts work. (This, I didn't know until just now.)

Is there a flag when the component is created that tells it to disable this, kind of like csAcceptsControls triggers if you can drop in another control?

I suppose it's possible I changed a setting somewhere that affected accelerators and never realized it.

Thanks,

-Tony

It's not the LCL. The WM+gtk does.
It should be possible to get the key event, before the gtk accelerators process it. But this needs to be implemented in the gtk intf.

Mattias

Still no luck... I can see it pass the virtual keycode to inherited, but menu shortcuts still don't work, which was the goal with this.

What triggers a menu shortcut to occur in the LCL? I can't find anything on it...

Thanks,

Tony

Can you send me the example?

Mattias