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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1772 Actions

    Problem Report Number 1772
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0218
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1997-02-03 08:00
    Product Standard Window System Application Interface V2
    Certification Program The Open Brand certification program
    Test Suite VSW version 5.0.0
    Test Identification Xt8/tmkgmreqt 3
    Specification Window Management (X11R5): X Toolkit Intrinsics
    Location in Spec See Problem Text
    Problem Summary PIN4W.00019 This test may fail on implementations because the standard makes conflicting statements about primitive/non-composite widgets.
    Problem Text
    This interpretation request is also for Xt8/tmkrsizrt 3.

    This test may fail on implementations because the standard makes
    conflicting statements about primitive/non-composite widgets.

    The assertion tests the following statement in section 8.2 of the X
    Toolkit Intrinsics standard:

    If the parent's class is not a subclass of
    compositeWidgetClass or the parent's geometry_manager field is
    NULL, it issues an error.

    The problem is that conflicting statements about
    non-compositWidgeClass objects are made. The standard states
    in the same section:

    If the widget is unmanaged or the widget's parent is not
    realized, it makes the changes and returns XtGeometryYes.

    Furthermore, it states:

    Children of primitive widget are always unmanaged; therefore,
    XtMakeGeometry-Request always returns XtGeometryYes when
    called by a child of a primitive widget.

    We expect to return XtGeometryYes because of the last statement, but
    the test expects the opposite to occur and an error to be returned.
    Test Output

    TEST CASE: XtMakeGeometryRequest

    TEST PURPOSE #3
    Assertion XtMakeGeometryRequest-3.(A)
    When the class of the parent of the widget w is not a
    subclass of compositeWidgetClass a call to XtGeometryResult
    XtMakeGeometryRequest(w, request, reply_return) shall issue
    an invalidParent error.
    PREP: Initialize toolkit, Open display and Create topLevel root widget
    PREP: Create core class test widgets
    TEST: Call XtMakeGeometryRequest
    TEST: Error handler was invoked
    ERROR: Error handler was not invoked
    3 FAIL

    TEST CASE: XtMakeResizeRequest

    TEST PURPOSE #3
    Assertion XtMakeResizeRequest-3.(A)
    When the class of the parent of the widget w is not a
    subclass of compositeWidgetClass a call to XtGeometryResult
    XtMakeResizeRequest(w, width, height, width_return,
    height_return) shall issue an invalidParent error.
    PREP: Initialize toolkit, Open display and Create topLevel root widget
    PREP: Create test widgets
    TEST: Call XtMakeResizeRequest
    TEST: Error handler was invoked
    ERROR: Error handler was not invoked
    3 FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    A permanent interpretation is recommended.

    This assertion tests the following statement in section 8.2 of the X
    Toolkit Intrinsics standard:

    If the parent's class is not a subclass of
    compositeWidgetClass or the parent's geometry_manager field is
    NULL, it issues an error.

    However, the standard later states:

    Children of primitive widget are always unmanaged; therefore,
    XtMakeGeometry-Request always returns XtGeometryYes when
    called by a child of a primitive widget.

    A primitive widget is the same as a widget that is not a subclass of
    compositeWidgetClass because a widget can only be composite or primitive as
    described in Chapter 4.

    As a result, the standard conflicts since one requires an error and
    the other requires a XtGeometryYes to be returned. In practice, it
    appears that XtGeometryYes is returned.


    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Permanent Interpretation (PIN)
    Review Conclusion
    A Permanent Interpretation is granted.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority