🚀 go-pugleaf

My new popupmenu program is almost ready for release.
New features include:
  Now uses SwapBitsRastPortClipRect. (that means speed)
  The delay before opening item & subitem windows is removed.
  Multiple select is supported. (but not drag-select)
  MENUVERIFY is supported.
  Semaphores is used to prevent other tasks from changing the displyed menues.

But there is one bug left.

Sometimes the input.device stops and it is impossible to do anything.
I think intuition tries to do an ActivateWindow or something on the Locked
screen and then stops.
Does intuition do things like that in it's inputhandler???
If i remove the LockLayers out of my code, the menues work alright but they are
overwritten by windows borders.

Whats really happening is:
  I have to screens open.  The workbench and one custom.
  The custom screen is half the way down.
  My testprogram on the workbench screen looks like this:

 FOREVER { 
    Wait(1L << MyWindow->UserPort.mp_SigBit);
    Message = GetMsg(MyWindow->UserPort);
    if (Message->Class == MENUVERIFY)
      WorkbenchToFront();
    ReplyMsg(Message);
  }

  When i press the menubutton in my testprogram window the 
  workbench comes to the front and the inputhandler stops.
  Xoper tells me that the input.device is waiting for a signal
  0x00000040.

Can anyone out there help me with this problem.

Martin Adrian.