Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 2145 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 2145.

Report 2145 Actions

    Problem Report Number 2145
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0612
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Motif Toolkit
    Certification Program The Open Brand certification program
    Test Suite VSM version 4.0.0
    Test Identification widgets/XmSelectionDialog 3
    Problem Summary PG4M.00008 This is the test case fault. Similar case is XmSelectionDialog 4. The default value of XmNlistVisibleItemCount for XmSelectionDialog widget is 8, here we observed 3. The reason here is because the siz...
    Problem Text

    This is the test case fault. Similar case is XmSelectionDialog 4.

    The default value of XmNlistVisibleItemCount for XmSelectionDialog
    widget is 8, here we observed 3.
    The reason here is because the size of the XmSelectionDialog is
    set too small by the test case, it is 125*125(width * height). It is set in
    function mvsSetUpGlobalArgs which is in
    is called by the following function in file ../vsm4/src/mvslib/resources/
    mvsTstStRscs.c:

    widget_info = mvsCreateWidget(widget_class_info, parent_info,
    UseCommonArgs, (ArgList)NULL,0 );

    This size 125*125 is too small to display all the components of the
    XmSelectionDialog widget, so the system reset the size to 125*425 when it is
    realized( This is done by related function of WMShell in Xt lib Shell.c file,
    such as function ComputeWMSizeHints). Because the width is still not wide
    enough , the system wraped "Ok", "Cancel", "Help" buttons around and
    squeeze the size of XmText widget component of XmSelectionDialog widget and
    cause the system reset the XmNlistVisibleItemCount to be 3 depending the size




    of the XmText widget component.
    The normal size of XmSelectionDialog widget in my machine is 358*416
    after it is displayed on the screen.

    /****************************************************************************/
    To make above explanation more detailed:
    When XmSelectionDialog widget is just created in file ../vsm4/src/
    mvslib/widgets/mvsCreateWid.c:

    /* Create actual widget */
    widget_info->widget = (*widget_class_info->proc_CreateWidget)
    (parent_info->widget,args,nargs);

    XmNlistVisibleItemCount here is still 8 because above line will set all the
    resource to default, you can get this value and print it out to demo.
    XmNlistVisibleItemCount will be changed 7 lines down in the same file:

    XtRealizeWidget(widget_info->widget);

    There is a line code in function XtRealizeWidget to change the size of
    XmSelectionDialog and set XmNlistVisibleItemCount to 0:
    CallChangeManaged(widget);
    And later another line will set XmNlistVisibleItemCount to the actual value
    according to XmText widget component size:
    RealizeWidget(widget);

    "CallChangeManaged(widget)" will eventually call related function in Xt lib
    Shell.c for WMShell which is the ancester of DialogShell( DialogShell widget
    is the parent of BulletinBoard, and on BulletinBoard to put the
    XmSelectionDialog widget).

    To correct this problem, just set the size to be 500*500 instead of
    125*125.

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We recommend this request be refused.

    The test failure indicates that when the resources XmNallowOverlap and
    XmNapplyLabelString (which are settable) are modified the resource
    XmNlistVisibleItemCount is also changed.

    XmNlistVisibleItemCount,

    Specifies the number of items displayed in the SelectionBox list.




    It is true that the default value of the resource
    XmNlistVisibleItemCount is defined as 'dynamic' and is dependent on
    the height of the scrolled list SelectionDialog widget. The test
    creates a widget of size 125x125 and this results in
    XmNlistVisibleItemCount to be set to 3.

    It may also be true that specifying a geometry of 500x500 may result
    in the default for this resource set to 8. But the issue here is not
    about the default value of this resource but the fact that this
    resource is being modified by the system when other resources are
    altered.

    But, modifying the resource XmNapplyLabelString from "Apply" (default) to
    "<Key>F8" should not result in the XmNlistVisibleItemCount resource
    being changed (from 3 to 8). The XmNapplyLabelString resource
    only specifies the string to be used as a label for the 'Apply' button.

    It would be interesting to see which other resource modifications
    in this test resulted in the XmNlistVisibleItemCount resource
    being modified. But the submitter has only provided partial
    journal output. Full journals for each test should be provided
    when requesting waivers.


    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority