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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1765 Actions

    Problem Report Number 1765
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0211
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1999-04-19 08:00
    Product Standard X Window System Applications Interface
    Certification Program The Open Brand certification program
    Test Suite VSW version 5.02
    Test Identification Xlib4/XCreateWindow 29, 41
    Specification Xlib - C Language Binding
    Location in Spec See Problem Text
    Problem Summary PIN4W.00026 This request maintains that two visuals of the same type may have different visualids.
    Problem Text
    Failing Testcases: XCreateWindow 29,41
    XChangeWindowAttributes 31,43
    XSetWindowColormap 2


    The testcases listed above fail due to the fact that our implementation
    does not consider visuals which differ only in visualid to be of
    different types (See PG4W.0092 for more detail). We would like to
    request a PIN on the grounds that we believe that this behaviour
    is in fact reasonable (and intuitive). We find it hard to accept
    that the purpose for including the visualid element in the Visual
    structure is to provide another mechanism of differentiating
    between visual types. Many analogies can be drawn and many examples
    can be given of data structures which bundle "ids" along with
    salient data to allow for ease of access/reference as opposed to
    signalling a difference in type.

    Test Output
    TEST CASE: XCreateWindow

    TEST PURPOSE #29
    Assertion XCreateWindow-29.(A)
    When colormap and the window do not have the same visual
    type, then a BadMatch error occurs.
    METH: If two different visual types are supported:
    METH: Create colour map of different visual to window.
    METH: Attempt to set colourmap to created colour map.
    METH: Verify that a BadMatch error occurs.
    METH: else
    METH: UNSUPPORTED.
    REPORT: Got Success, Expecting BadMatch
    29 FAIL

    TEST PURPOSE #41
    Assertion XCreateWindow-41.(A)
    When colormap is CopyFromParent and the window does not
    have the same visual type as the parent window, then a
    BadMatch error occurs.
    METH: If two different visual types are supported:
    METH: Create a parent of one visual type
    METH: Attempt to set colourmap to CopyFromParent on window of different visual type.
    METH: Verify that a BadMatch error occurs.
    METH: else
    METH: UNSUPPORTED.
    REPORT: Got Success, Expecting BadMatch
    41 FAIL

    TEST CASE: XChangeWindowAttributes

    TEST PURPOSE #31
    Assertion XChangeWindowAttributes-31.(A)
    When colormap and the window do not have the same visual
    type, then a BadMatch error occurs.
    METH: If two different visual types are supported:
    METH: Create colour map of different visual to window.
    METH: Attempt to set colourmap to created colour map.
    METH: Verify that a BadMatch error occurs.
    METH: else
    METH: UNSUPPORTED.
    REPORT: Got Success, Expecting BadMatch
    31 FAIL

    TEST PURPOSE #43
    Assertion XChangeWindowAttributes-43.(A)
    When colormap is CopyFromParent and the window does not
    have the same visual type as the parent window, then a
    BadMatch error occurs.
    METH: If two different visual types are supported:
    METH: Create a parent of one visual type
    METH: Attempt to set colourmap to CopyFromParent on window of different visual type.
    METH: Verify that a BadMatch error occurs.
    METH: else
    METH: UNSUPPORTED.
    REPORT: Got Success, Expecting BadMatch
    43 FAIL

    TEST CASE: XSetWindowColormap

    TEST PURPOSE #2
    Assertion XSetWindowColormap-2.(C)
    If more than one type of visual is supported: When the
    colormap argument does not have the same visual type as the
    window specified by the window argument w, then a BadMatch
    error occurs.
    METH: For each supported visual:
    METH: Create a colormap not of that visual type.
    METH: Create a window of that visual type.
    METH: Verify that a call to XSetWindowColormap generates a BadMatch error.
    REPORT: Got Success, Expecting BadMatch
    REPORT: Got Success, Expecting BadMatch
    REPORT: Got Success, Expecting BadMatch
    REPORT: Got Success, Expecting BadMatch
    REPORT: Got Success, Expecting BadMatch
    2 FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We suggest this request be forwarded to the base working group
    for consideration.

    We also believe that the specification did not intend to allow this
    behavior. However, we can find no explicit wording in the current spec
    that disallows this behavior.

    We believe that allowing this behavior may break existing applications.

    Review Type Expert Group Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    It is the opinion of the X Standards task force that the current
    standard is vague in this area and a PIN should thus be granted.

    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