Several times now I have tried to use the tag WINDOW_AppMsgHook, but I still have some questions about it.
I've created a 'small' test program utilising this tag (and, yes I did specify WINDOW_AppPort, WINDOW_AppWindow and WINDOW_IconifyGadget tags too, with proper ti_Data values applied).
When after starting the program, the window opens, dropping an object on the window seems to indeed call the Hookfunction. However, when I have Iconified the program AppMsgPort's SigBit [AllSig |= (1 << AppMsgPort->mp_SigBit)] is added to all the SigBits IExec->Wait() is expected to react upon [AnySig = IExec->Wait(AllSig)]. After de-Iconified the program this AppMsgPort's SigBit is removed from AllSIg [AllSig &= ~(1 << AppMsgPort->mp_SigBit)], but the Hookfunction does no longer seem to work. All messages still seem to be relegated to the 'normal' IExec->Wait() functionality which does not react to the Messages due to the SigBit being removed (i.e. nothing happens).
I'm inclined to leave the whole AppMsgHook for what it was and have all AppMessages dealt with in the IExec->Wait()-cycle (like I have always done). But what is then the advantage of said tag?
Or needs the tag WINDOW_AppMsgHook to be re-applied after de-Iconification in order to take effect (again)?