Re: [Iup-users] Fw: Re: Silence Alt-keys

The k_any calllback(s) is processed on WM_KEYDOWN and WM_SYSKEYDOWN events. I made a simple test here and they are correctly returning 0 in the WindowProc and not calling DefWindowProc when IUP_IGNORE is returned. In both IUP_DEFAULT and IUP_IGNORE, Windows is playing the bell sound. Best,

Re: [Iup-users] Possible bug in IupReparent or IupLayoutDialog

> the hidden IupBackgroundBox of an IupExpander is genuinely hidden This was already fixed. > if you drag it back to be a sibling of the IupBackgroundBox it works fine, but IupReparent crashed I just fixed the behavior of inserting a child in an empty IupExpander, it was inserting before

[Iup-users] Fw: Re: Silence Alt-keys

Well, if nothing at all handles a specific keystroke, that is correct. However, I **did** handle it, just can't figure out how to say that I have. Pete > > On Fri, 1/12/17, Antonio Scuri > wrote: > > Subject: Re:

[Iup-users] Fw: Re: Silence Alt-keys

Hi, There is no problem with Alt-F1, or Alt-Home/End/Left/Right etc, but for Alt-X and Alt-, both IUP_DEFAULT and IUP_IGNORE sound the bell. I should perhaps say this is probably a Windows-only problem. The code I am translating, from a win32-only gui, apparently solves the problem by

Re: [Iup-users] Silence Alt-keys

That's the default behavior in any application. The system rings a bell exactly to notify the user that it is a hot key that does nothing. You can try that in Word, Excel, Notepad, etc... Best, Scuri 2017-11-30 22:20 GMT-02:00 Pete Lomax via Iup-users < iup-users@lists.sourceforge.net>: >

Re: [Iup-users] Silence Alt-keys

Hi, Can you try: case K_mF1: return IUP_DEFAULT; break; According with IUP online help: If returns IUP_DEFAULT the key is processed but it is not propagated. If key is processed, maybe solve your case. Best, Ranier Vilela De: Pete