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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1782 Actions

    Problem Report Number 1782
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Temporary Interpretation (TIN)
    Problem Resolution ID TIN.X.0081
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1996-11-11 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 tset/Xt5/XtUnmanageChildren 004
    Specification Window Management (X11R5): X Toolkit Intrinsics
    Location in Spec See Problem Text
    Problem Summary TIN4W.00001 This test may fail because the requirement an error be generated has been changed to require a warning by the X Consortium in R6.1.
    Problem Text
    Several problems here:

    First - notice that the abstract of the above test asserts that a
    "warning" message shall be issued. Also notice that the test
    is in error because a "Warning" was issued instead of an error.

    Second - In chapter 3, the Xt Spec says that an "error" shall be generated
    for this condition. However, in appendix D, it says that this
    is a "warning". The sample implementation treats this as a
    "warning".

    Third - Bug report was sent to the X-Consortium, and they intend to change
    the spec to be a warning. (See below).


    >From Ralph R. Swick
    Subject: XtManageChildren/XtUnmanageChildren: change Error to Warning
    Date: Fri, 01 Nov 1996 09:28:19 EST

    Donna and I debated this a long time last year but I guess we never
    remembered to bring it out to the list.

    In all releases since R3 the Consortium implementation of both
    XtManageChildren and XtUnmanageChildren has issued only a warning
    (and returned) when the children were not of the same parent.
    (R2 allowed a mix of parents but it was decided that the spec
    did not need to require this.)

    In all releases prior to R6.1 the class of the parent was not
    checked in XtUnmanageChildren; no warning or error was issued.
    If the parent was not a CompositeWidget the implementation would
    dereference an uninitialized pointer. XtManageChildren has
    always checked the class of the parent and returned an error
    if it was not a CompositeWidget.

    When XtChangeManagedSet was added in the R6 specification its rules
    were inconsistent with XtManageChildren and XtUnmanageChildren. The
    R6 implementation, however, issued a warning when there were multiple
    parents and an error if the parent was not a CompositeWidget, matching
    XtManageChildren.

    When discussing the appropriate solution to the inconsistency, Donna
    and I chose to follow a path that was least likely to cause hardship
    to existing programs.

    The summary of XBUG #7486 (closed on 29-Jun-1995 and shipped in R6.1)
    best summarizes our conclusion:

    SYNOPSIS:
    When XtUnmanageChildren is called, if the parent is not a subclass
    of composite, an error message should be issued. In earlier
    implementations, this error message wasn't included.

    DESCRIPTION:
    Each of XtManageChildren, XtUnmanageChildren, and in R6 the new
    function XtChangeManagedSet should, check and treat consistently
    these two conditions:
    a) condition: all children have the same parent.
    treatment: if not, issue a warning, and continue.
    b) condition: the parent is a subclass of Composite
    treatment: if not, issue an error

    Given the attached new bug report, I think we should formally
    modify the specification to conform to the previous paragraph.


    Test Output
    TEST PURPOSE #4
    Assertion XtUnmanageChildren-4.(A)
    When the widgets specified by children do not all have the
    same parent a call to void XtUnmanageChildren(children,
    num_children) shall issue a warning message.
    PREP: Initialize toolkit, Open display and Create topLevel root widget
    PREP: Create managed child widget labelw1 in boxw1
    PREP: Create rowcolw_good widget in boxw1 widget
    PREP: Create managed child widget labelw2 in rowcolw_good
    PREP: Create windows for widgets and map them
    PREP: Register error handler
    PREP: Unmange children, with different parents
    TEST: Error message was generated
    ERROR: Error handler was not invoked
    ERROR: Warning message was issued instead of error message
    4 FAIL

    Review Information

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

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

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority