Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
Problem Description: I have a customer who sets host from one workstation to another,edits a file (or some other VMS function) and finds if he leaves his terminal for sometime he is logged out and recieves the following error message in his DECW$SM.LOG. Has anyone any ideas.... Error Message. X error event recieved from server: BadMatch - parameter mismatch Failed request major op code 42 X_SetInputFocus Failed request minor op code 0 (if applicable) ResourceID 0x30001c in failed request (if applicable) Serial number of failed request 364 Current serial number in output stream 365 Session Error: %NONAME-E-NOMSG,Message number 02DB822A Thanks. GC.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2529.1 | UTRTSC::CAHILL | Thu Mar 29 1990 08:28 | 10 | ||
OK.. let me ask another question.. Any ideas where the error message is generated from and WHY? Thanks again. GC. | |||||
2529.2 | That I can answer... | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Thu Mar 29 1990 18:41 | 11 |
THAT I can answer at some level, anyway. The message is sent from the server to the client. It says that the client tried to do a reqeust called SetInputFocus, and one or more of the parameters was incorrect. In this case, a Match error indicates that the window to which focus was being set was not viewable (perhaps one of its parents was unmapped or some such). Why all this has anything to do with the stated circumstances is the mystery. Burns | |||||
2529.5 | Harmless and expected | DECWIN::KLEIN | Fri Mar 30 1990 11:05 | 11 | |
Assigning focus to an iconified window results in this error (warning) message. Because of the asynchronous nature of the window manager / application execution, this error cannot be avoided. It is up to each application to write an X error handler to ignore this error. Examples of such an error handler have been posted in at least two places (by me) but I don't remember where exactly. The message is harmless and should be ignored by the user if not by the application. -steve- |