Path: utzoo!attcan!uunet!pyrdc!pyrnj!rutgers!gatech!gt-eedsp!jensen From: jensen@gt-eedsp.UUCP (P. Allen Jensen) Newsgroups: comp.windows.x Subject: Re: dialogWidget and scrollBarWidget problems under X11R2 Summary: XtWaitForReadable - should have been XWaitForReadable Keywords: Widget,dialog,ScrollBar,problem,X11R2 Message-ID: <436@gt-eedsp.UUCP> Date: 9 Sep 88 13:48:50 GMT References: <433@gt-eedsp.UUCP> Organization: Georgia Institute of Technology Lines: 39 In article <433@gt-eedsp.UUCP>, jensen@gt-eedsp.UUCP (P. Allen Jensen) writes: > ........... > 1) I have a Dialog Widget with a command button for getting a file name > from the user. The server is a uVax QVSS and the Client is a Multiflow > Trace. The Client is running BSD4.3 and the Server is running Ultrix 1.1 > > There are other command buttons and scrollbars used by the program. > Everything is fine until I try to type the filename into the dialogWidget > input area. The program then hangs in XtWaitForReadable. Sorry, that should have been XWaitForReadable - The full traceback is: (dbx) where >select(4, -27980, 0, 0, 0) at 0x11c324 _XWaitForReadable(1376256) at 0xecd48 _XRead(1376256, 1380352, 1328) at 0xdd284 XGetKeyboardMapping(1376256, 86, 166, 1376424) at 0xeec0c $libX$XKeyBind.Initialize(1376256) at 0xb75b4 XLookupKeysym(-25884, 0) at 0xb6f40 XEventToTMEvent(-25884, -27248) at 0x8b5f0 _XtTranslateEvent(1369600, 1369676, -25884) at 0x8b9f4 DispatchEvent(-25884, 1369600, 1) at 0x5533c XtDispatchEvent(-25884) at 0x5638c XtMainLoop() at 0x58180 main(argc = 1, argv = 0xffff9c88), line 31 in "xsignal.c" mlsetup(-25468) at 0x69c call_mlsetup() at 0x184 (dbx) As you can see - it is stuck in the select. That is why I think it may be a BSD4.3 vs Ultrix 1.1 incompatability in the network protocols. Any ideas anyone ? -- P. Allen Jensen Georgia Tech, School of Electrical Engineering, Atlanta, GA 30332-0250 USENET: ...!{allegra,hplabs,ihnp4,ulysses}!gatech!gt-eedsp!jensen INTERNET: jensen@gteedsp.gatech.edu