J.Crowcroft@CS.UCL.AC.UK (Jon Crowcroft) (05/23/89)
I have hacked up a version of the Xaw asciiTextwidget that allows a callback to be added, so that a simple text conferincing program can be written - it runs on one machine and opens n text windows on each of n conferee's displays. When input arrives on any window, the callback routine re-dispatches the event to all the equiv output windows on the n-1 other displays. To work properly, there are minor (other) changes to Text, Asciitext, Simple. Also required are alterations to GCManager, to allow the GCs to setup right accross multiple displays... Unfortunately, it works underr all window managers we have here except twm - with which the text widgets resoluteley refuse to accept any key event input. Does anyone have a pointer to where to start looking for the problem before i post a defective application? cheers jon
erik@sravd.sra.JUNET (Erik M. van der Poel) (05/25/89)
In article <8905241809.AA25627@ATHENA.MIT.EDU> J.Crowcroft@cs.ucl.ac.uk (Jon Crowcroft) writes: >Unfortunately, it works underr all window managers we have here except >twm - with which the text widgets resoluteley refuse to accept any key >event input. Try NoTitleFocus. I experienced something that sounds similar in the sense that the widget wouldn't accept key input, but the circumstances may be different. In my case, I would pop up a shell and then pop it back down by pushing a button in a child of the popup shell, but then the main widget wouldn't accept key input any more. I noticed the following sequence: move into main insert main map popup remove main insert main remove main insert main move into popup remove main insert popup unmap popup remove popup insert popup ! remove main ! insert main where insert is InsertFocusEntry(), remove is RemoveGrab(), both in Xt/Event.c. The lines marked with ! are suspect. Does anyone know where the bug is?