HomeAbout Us A-Z IndexSearch * Contact Us Register LoginPress Shop

The Open Brand -- Problem Reporting and Interpretations System


Problem Report 2191 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 2191.


Report 2191 Actions


    Problem Report Number 2191
    Submitter's Classification Minor System Fault
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.1110
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1998-08-18 08:00
    Product Standard Motif Toolkit
    Certification Program The Open Brand certification program
    Test Suite VSM version 4.0.0
    Test Identification vsm4/tset/widgets/XmSelectionDialog4 test4A
    Problem Summary TSD4M.00016 This report is asking for such kind of error: INFO: --XmNresizePolicy=2 ERROR: Resource XmNlistVisibleItemCount: Expected 3, received 8 or INFO: --XmNresizePolicy=1 ERROR: Resource XmNlistVisibleItemC...
    Problem Text
    This report is asking for such kind of error:

    INFO: --XmNresizePolicy=2
    ERROR: Resource XmNlistVisibleItemCount: Expected 3, received 8

    or

    INFO: --XmNresizePolicy=1
    ERROR: Resource XmNlistVisibleItemCount: Expected 3, received 11

    This is caused by the system design problem. Refer to report.zw030
    for related information and TSD4M.00013 for waiver.
    The test case is in ../vsm4/tset/selectiond.c/test4A.
    The stack sequence to reach where the errors happen is:

    (*testWidgetClassInfo->proc_TestBehavior) (testWidgetClassInfo,
    parentWidgetInfo);
    /**** ../vsm4/tset/selectiond.c/test4A. *******/

    static void TestBehavior(widget_class_info, parent_info)
    MvsWidgetClassInfo *widget_class_info;
    MvsWidgetInfoRecord *parent_info;
    {
    for( i = start ; i < end ; i++ ) {
    ...........................................................
    mvsBoxBehaviorSet(widget_class_info,parent_info,focus_mode,
    args,nargs, i+1);

    } /* End for( i < end ) */
    /*** ../vsm4/src/mvslib/instances/SelectionD.c ********/

    Function mvsBoxBehaviorSet is defined in
    mvsSetValues(Box_info, args, n) and this is where the errors happen.

    The error happens in this functional call: "mvsSetValues(Box_info,




    args, n);" in file ../vsm4/src/mvslib/behavior/Box.c, function
    mvsBoxBehaviorSet, around line #223. Reference to report.zw030 for similar
    stack sequence for functional call mvsSetValues.

    This report is asking waiver for a case similar to report.zw030
    which is granted.
    There are 3 kinds of values for XmNresizePolicy here, in Xm.h:

    enum{ XmRESIZE_NONE, XmRESIZE_GROW,
    XmRESIZE_ANY
    } ;

    From above you can see, XmRESIZE_GROW is 1, XmRESIZE_ANY is 2 which
    is default value for resource XmNresizePolicy of XmSelectionDialog widget in
    this test case(in ../mvslib/instances/SelectionD.c)

    I have got waiver for the following error in report.zw030:

    INFO: --XmNresizePolicy=2
    ERROR: Resource XmNlistVisibleItemCount: Expected 3, received 8

    So here I only ask waiver for this kind of error:

    INFO: --XmNresizePolicy=1
    ERROR: Resource XmNlistVisibleItemCount: Expected 3, received 11

    The reason here received 11 instead of 8 is because XmNresizePolicy
    is different, it is XmRESIZE_GROW(1). As I explained in report.zw030,
    when this XmSelectionDialog widget is created, its size is 125x125 which is
    too small to display all the component of the selection dialog widget, so
    the system change it to 125x378 in my machine and set the widget resource
    XmNlistVisibleItemCount to be 3 according to the actually widget size, not
    to be the default value 8. Later on when we call XtSetValues in "mvsSetValues"
    to set any resource, the system will blowup this widget and make it more
    beatiful, so that it is not narrow and long(think 125x378). When the
    resource XmNresizePolicy is XmRESIZE_ANY(which is default), in my machine the
    system will make the widget to be 328x325, and reset XmNlistVisibleItemCount
    to be default value 8, this is what I explained in report.zw030. When the
    resource XmNresizePolicy is XmRESIZE_GROW, since the height of the realized
    widget is 378 and cannot be shrinked, so the system make the widget to be
    328x378 in my machine, this time the widget is a little bit bigger, and it can
    display 11 lines of text, so comes the value of XmNlistVisibleItemCount.

    Take a look at file SelectioB.c of Xm, this file is for
    XmSelectionDialog widget. In this SelectioB.c file, there is a "SetValues"
    function, in the end of this function, it has:
    ..................................................................
    if( XtClass( new_w) == xmSelectionBoxWidgetClass )
    {
    _XmBulletinBoardSizeUpdate( (Widget) new_w) ;
    }
    ..................................................................




    Function _XmBulletinBoardSizeUpdate is defined in Xm BulletinB.c,
    in this function, it has:
    ..................................................................
    _XmHandleSizeUpdate( (Widget) bbWid, BB_ResizePolicy( bbWid),
    classPtr->bulletin_board_class.geo_matrix_create) ;
    ..................................................................

    Function _XmHandleSizeUpdate is defined in Xm GeoUtils.c. In this
    function, it calculates the bulletin board size according to different
    XmNresizePolicy resource value. Take a look at this function, then it will
    become very clear why XmNlistVisibleItemCount is 11 this time when the
    XmNresizePolicy is XmRESIZE_GROW instead of XmRESIZE_ANY.

    Test Output

    TEST CASE: XmSelectionDialog

    TEST PURPOSE #4
    The XmSelectionDialog widget shall exhibit the behavior
    defined in the Motif Toolkit API specification.
    INFO: Key code collision between osfCancel and Escape
    INFO: This may be a problem: Check your .motifbind file
    INFO: ***************** Beginning Iteration 1 of 48 ****************
    INFO: --XmNsensitive=True
    INFO: --XmNallowOverlap=True
    INFO: --XmNautoUnmanage=True
    INFO: --XmNmustMatch=True
    INFO: --XmNresizePolicy=0
    TEST: ListButtonMotion
    PREP: Unmap on activate of Cancel
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    TEST: New active region
    TEST: Causes the current gadget to be armed.
    TEST: Causes the current gadget to be activated.
    TEST: The cancel button is the selected region
    TEST: Activation of the Ok button results in no match callback when Text selecti
    on does not match
    TEST: Activation of the Apply button results in apply callback
    TEST: Activation of the Help button results in help callback
    TEST: Activation of the Ok button results in ok callback
    TEST: Call the cancel callback if a cancel button exists




    PREP: Map
    TEST: Call the callbacks for XmNmapCallback when map occurs
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    PREP: Unmap
    TEST: Call the callbacks for XmNunmapCallback when unmap occurs
    PREP: Map
    TEST: Call the callbacks for XmNmapCallback when map occurs
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    PREP: Activate of Help
    TEST: New active region
    TEST: Causes the current gadget to be armed.
    TEST: Causes the current gadget to be activated.
    TEST: The cancel button is the selected region
    TEST: Activation of the Ok button results in no match callback when Text selecti
    on does not match
    TEST: Activation of the Apply button results in apply callback
    TEST: Activation of the Help button results in help callback
    TEST: Activation of the Ok button results in ok callback
    PREP: Unmap on activate of Ok
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    TEST: New active region
    TEST: Causes the current gadget to be armed.
    TEST: Causes the current gadget to be activated.
    TEST: The cancel button is the selected region
    TEST: Activation of the Ok button results in no match callback when Text selecti
    on does not match
    TEST: Activation of the Apply button results in apply callback
    TEST: Activation of the Help button results in help callback
    TEST: Activation of the Ok button results in ok callback
    TEST: Activate of Ok with autoUnmanage causes ok callback and unmap callback
    PREP: Destroy Box Manager
    TEST: Destroying the widget results in a destroy callback
    INFO: ***************** Beginning Iteration 2 of 48 ****************
    INFO: ***************** Beginning Iteration 17 of 48 ****************
    INFO: --XmNsensitive=True
    INFO: --XmNallowOverlap=True
    INFO: --XmNautoUnmanage=True
    INFO: --XmNmustMatch=True
    INFO: --XmNresizePolicy=2
    ERROR: Resource XmNlistVisibleItemCount: Expected 3, received 8
    PREP: Unmap on activate of Cancel
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    TEST: New active region
    TEST: Causes the current gadget to be armed.
    TEST: Causes the current gadget to be activated.
    TEST: The cancel button is the selected region
    TEST: Activation of the Ok button results in no match callback when Text selecti
    on does not match
    TEST: Activation of the Apply button results in apply callback
    TEST: Activation of the Help button results in help callback
    TEST: Activation of the Ok button results in ok callback
    TEST: Call the cancel callback if a cancel button exists




    PREP: Map
    TEST: Call the callbacks for XmNmapCallback when map occurs
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    PREP: Unmap
    TEST: Call the callbacks for XmNunmapCallback when unmap occurs
    PREP: Map
    TEST: Call the callbacks for XmNmapCallback when map occurs
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    PREP: Activate of Help
    TEST: New active region
    TEST: Causes the current gadget to be armed.
    TEST: Causes the current gadget to be activated.
    TEST: The cancel button is the selected region
    TEST: Activation of the Ok button results in no match callback when Text selecti
    on does not match
    TEST: Activation of the Apply button results in apply callback
    TEST: Activation of the Help button results in help callback
    TEST: Activation of the Ok button results in ok callback
    PREP: Unmap on activate of Ok
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    TEST: New active region
    TEST: Causes the current gadget to be armed.
    TEST: Causes the current gadget to be activated.
    TEST: The cancel button is the selected region
    TEST: Activation of the Ok button results in no match callback when Text selecti
    on does not match
    TEST: Activation of the Apply button results in apply callback
    TEST: Activation of the Help button results in help callback
    TEST: Activation of the Ok button results in ok callback
    TEST: Activate of Ok with autoUnmanage causes ok callback and unmap callback
    PREP: Destroy Box Manager
    TEST: Destroying the widget results in a destroy callback
    INFO: ***************** Beginning Iteration 18 of 48 ****************
    INFO: --XmNsensitive=False
    INFO: --XmNallowOverlap=True
    INFO: --XmNautoUnmanage=True
    INFO: --XmNmustMatch=True
    INFO: --XmNresizePolicy=2
    ERROR: Resource XmNlistVisibleItemCount: Expected 3, received 8
    PREP: Click KHelp over manager
    PREP: Destroy Box Manager
    TEST: Destroying the widget results in a destroy callback
    INFO: ***************** Beginning Iteration 19 of 48 ****************
    INFO: ***************** Beginning Iteration 33 of 48 ****************
    INFO: --XmNsensitive=True
    INFO: --XmNallowOverlap=True
    INFO: --XmNautoUnmanage=True
    INFO: --XmNmustMatch=True
    INFO: --XmNresizePolicy=1
    ERROR: Resource XmNlistVisibleItemCount: Expected 3, received 11
    PREP: Unmap on activate of Cancel
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget




    TEST: New active region
    TEST: Causes the current gadget to be armed.
    TEST: Causes the current gadget to be activated.
    TEST: The cancel button is the selected region
    TEST: Activation of the Ok button results in no match callback when Text selecti
    on does not match
    TEST: Activation of the Apply button results in apply callback
    TEST: Activation of the Help button results in help callback
    TEST: Activation of the Ok button results in ok callback
    TEST: Call the cancel callback if a cancel button exists
    PREP: Map
    TEST: Call the callbacks for XmNmapCallback when map occurs
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    PREP: Unmap
    TEST: Call the callbacks for XmNunmapCallback when unmap occurs
    PREP: Map
    TEST: Call the callbacks for XmNmapCallback when map occurs
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    PREP: Activate of Help
    TEST: New active region
    TEST: Causes the current gadget to be armed.
    TEST: Causes the current gadget to be activated.
    TEST: The cancel button is the selected region
    TEST: Activation of the Ok button results in no match callback when Text selecti
    on does not match
    TEST: Activation of the Apply button results in apply callback
    TEST: Activation of the Help button results in help callback
    TEST: Activation of the Ok button results in ok callback
    PREP: Unmap on activate of Ok
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    TEST: New active region
    TEST: Causes the current gadget to be armed.
    TEST: Causes the current gadget to be activated.
    TEST: The cancel button is the selected region
    TEST: Activation of the Ok button results in no match callback when Text selecti
    on does not match
    TEST: Activation of the Apply button results in apply callback
    TEST: Activation of the Help button results in help callback
    TEST: Activation of the Ok button results in ok callback
    TEST: Activate of Ok with autoUnmanage causes ok callback and unmap callback
    PREP: Destroy Box Manager
    TEST: Destroying the widget results in a destroy callback
    INFO: ***************** Beginning Iteration 34 of 48 ****************
    INFO: --XmNsensitive=False
    INFO: --XmNallowOverlap=True
    INFO: --XmNautoUnmanage=True
    INFO: --XmNmustMatch=True
    INFO: --XmNresizePolicy=1
    ERROR: Resource XmNlistVisibleItemCount: Expected 3, received 11
    PREP: Click KHelp over manager
    PREP: Destroy Box Manager
    TEST: Destroying the widget results in a destroy callback




    INFO: ***************** Beginning Iteration 35 of 48 ****************
    INFO: --XmNsensitive=True
    INFO: --XmNallowOverlap=False
    INFO: --XmNautoUnmanage=True
    INFO: --XmNmustMatch=True
    INFO: --XmNresizePolicy=1
    ERROR: Resource XmNlistVisibleItemCount: Expected 3, received 11
    PREP: Unmap on activate of Cancel
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    TEST: New active region
    TEST: Causes the current gadget to be armed.
    TEST: Causes the current gadget to be activated.
    TEST: The cancel button is the selected region
    TEST: Activation of the Ok button results in no match callback when Text selecti
    on does not match
    TEST: Activation of the Apply button results in apply callback
    TEST: Activation of the Help button results in help callback
    TEST: Activation of the Ok button results in ok callback
    TEST: Call the cancel callback if a cancel button exists
    PREP: Map
    TEST: Call the callbacks for XmNmapCallback when map occurs
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    PREP: Unmap
    TEST: Call the callbacks for XmNunmapCallback when unmap occurs
    PREP: Map
    TEST: Call the callbacks for XmNmapCallback when map occurs
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    PREP: Activate of Help
    TEST: New active region
    TEST: Causes the current gadget to be armed.
    TEST: Causes the current gadget to be activated.
    TEST: The cancel button is the selected region
    TEST: Activation of the Ok button results in no match callback when Text selecti
    on does not match
    TEST: Activation of the Apply button results in apply callback
    TEST: Activation of the Help button results in help callback
    TEST: Activation of the Ok button results in ok callback
    PREP: Unmap on activate of Ok
    TEST: Call the callbacks for XmNfocusCallback when focus enters widget
    TEST: New active region
    TEST: Causes the current gadget to be armed.
    TEST: Causes the current gadget to be activated.
    TEST: The cancel button is the selected region
    TEST: Activation of the Ok button results in no match callback when Text selecti
    on does not match
    TEST: Activation of the Apply button results in apply callback
    TEST: Activation of the Help button results in help callback
    TEST: Activation of the Ok button results in ok callback
    TEST: Activate of Ok with autoUnmanage causes ok callback and unmap callback
    PREP: Destroy Box Manager
    TEST: Destroying the widget results in a destroy callback
    INFO: ***************** Beginning Iteration 36 of 48 ****************




    INFO: ***************** Beginning Iteration 48 of 48 ****************
    INFO: --XmNsensitive=False
    INFO: --XmNallowOverlap=False
    INFO: --XmNautoUnmanage=False
    INFO: --XmNmustMatch=False
    INFO: --XmNresizePolicy=1
    ERROR: Resource XmNlistVisibleItemCount: Expected 3, received 11
    PREP: Click KHelp over manager
    PREP: Destroy Box Manager
    TEST: Destroying the widget results in a destroy callback
    4 FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The value of the XmNhistoryVisibleItemCount resource is defined to
    be dynamic and should reflect adjustments to the widget size
    which occur as a result of normal client windown manager intervention,
    as appears to have happened in this case and the case of TSD4M.00013 and
    TSD4M.00014.

    We recommend that this waiver request be granted as a TSD.


    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion
    This is an agreed Test Suite Deficiency.


    Problem Reporting System Options:

     

    Back   


Contact the Certification Authority