[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

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

3587.0. "XtProtocol error" by MARX::BARLOW () Mon Nov 05 1990 16:42

    
    I have a program which gets the following error:
    
    X Protocol error detected by server:  BadMatch - parameter mismatch
      Failed request major op code 42 (X_SetInputFocus)
      Failed request minor op code 0 (if applicable)
      ResourceID 0x10008e in failed request (if applicable)
      Serial number of failed request 26547
      Current serial number in output stream 26593
    
    Program exited with code 1
    
    Unfortunately, then the program is not active, so I can't
    use DBX to figure out what is wrong.  I also cannot get the
    problem to reproduce dependably.  I suspect that I am somehow
    overwriting memory so that when I do an XtUnmanageChild, and
    Xt tries to focus on the parent, the data about the parent has
    been overwritten, so Xt thinks the parent doesn't exist.
    
    The sequence events is :
     - click on an item in the list box on the parent window
     - that brings up the child popup_attached_db widget which
    also has a list box.  It populates this list box with varying
    lines of data.  (It depends on what was clicked on in the parent's
    list box.)
     - click on a button labeled "select all", which uses
    DwtListBoxSelectPos in a loop, (i=0; i<DwtNitemsCount; i++)
     - then hit APPLY button, which stores all selected listboxitems
    into a temporary table in the Ingres database and then UnManages
    the child.  
    
    I've stepped through code executed when the APPLY button is hit, and
    it seems to be dieing after the XtUnmanageChild call.
T.RTitleUserPersonal
Name
DateLines
3587.1MARX::BARLOWMon Nov 05 1990 16:447
    
    So, my question is, has anyone seen this before?  Do you 
    have any other theories as to what the problem might be ?
    
    Thanks in advance for any clues,
    Rachael
    
3587.2OXNARD::KLEEKen LeeMon Nov 05 1990 17:025
    Is it possible that the window is not viewable when it receives input
    focus?  That will cause the error you report.
    
    Ken