Hi
I have a few problems porting my working MUI interface (on MUI 3.8) to MUI 4 on MorphOS.

My problem is with the rawkey event and string gadgets. I find that when I activate a string gadget on MUI 4, the keypresses are still being processed by the rawkey handler. The result is you cannot type text into the string. Yet it works no problem on MUI 3.8. I can't figure it out.

I would be grateful for any advice anyone is able to give on this. Thanks!

Care to provide some code showing how you process the raw events?

Thanks for your help. Then IDCMP rawkey is set up in the mSetup function...

PROC mSetup(cl:PTR TO iclass,obj:PTR TO object,msg:PTR TO muip_handleinput)
IF doSuperMethodA(cl,obj,msg)=NIL THEN RETURN FALSE
Mui_RequestIDCMP(obj, IDCMP_MOUSEBUTTONS OR
IDCMP_RAWKEY OR
IDCMP_VANILLAKEY)
ENDPROC MUI_TRUE

The mHandleInput function calls the RAWKEY function...

PROC mHandleInput(cl:PTR TO iclass, obj:PTR TO object, msg:PTR TO muip_handleinput)
...
IF msg.imsg
selectdummy:=msg.imsg.class
qual := msg.imsg.qualifier
code := msg.imsg.code

SELECT selectdummy
CASE IDCMP_RAWKEY; handlerawkeyevent(qual, code)
CASE IDCMP_VANILLAKEY; handlevanillakeyevent(qual, code)
...
ENDSELECT
ENDPROC doSuperMethodA(cl,obj,msg)

And then the handlerawkeyevent() function handles what is actually pressed...

PROC handlerawkeyevent(qualifier, code)
DEF value
IF qualifier AND (IEQUAL_ALT)
SELECT code
CASE CURSOR_UP_KEY
...
ENDSELECT
...
ENDIF
ENDPROC

Am I missing something when it comes to MUI4? Thanks again!

Should mHandleInput check what object the event was triggered by maybe?

You are using deprecated technic for rawkey handling.

That is, RequestIDCMP() is deprecated and it would be better use MUIM_Window_AddEventHandler/MUIM_Window_RemEventHandler methods.

(String.mui have changed in MUI4 so it could have some effect in your application.)

[ Edited by itix 16.03.2012 - 10:41 ]

Thanks very much for your helpful suggestions! I will look again at this.

Still no joy. I have removed the RequestIDCMP code and replaced it with the proper AddEventHandler code. Still the same problem occurs. When I specify RAWKEY and VANILLAKEY events in the event handler node, string input stops working. Right and left arrow keys do still work in the strings for some reason, but typing ordinary letters in the string activates my event handler code instead. Yet it seems to work ok in MUI 3.8.

I am wondering if it is anything to do with ECX MUI modules not being compatible with MUI 4? I tried altering the event handler priority, and a number of other things. But still the same problem. Event handler code is being handled before the active object. Any ideas? Thanks for your help.

Well... it could be that your handler has a higher priority than the one of the string gadget. I suppose you might want a lower pri handler.

Quote:

Oh... you shouldnt use VANILLAKEY in MUI. MUI classes are relying on IDCMP_RAWKEY and when you add IDCMP_VANILLAKEY to IDCMP flags some classes stop working. This is also case in MUI 3 with other text input classes.

So you should use RAWKEY only and using MapRawKey() get vanilla key code. In MorphOS 2/MUI 4 you can also get unicode so you dont have to do conversion anymore:

switch (IntuiMessage->Class)
{
case IDCMP_RAWKEY:
ULONG ucs4_keycode = getv(IntuiMessage, IMSGA_UCS4)
break;
}

That's fantastic! Thanks very much for all your help guys. It was the VANILLAKEY event that was causing the problem. I have managed to fix it using your MapRawKey suggestion. Thanks again!