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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1770 Actions

    Problem Report Number 1770
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0216
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1998-02-12 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 Xt11/tvagtares 3
    Specification Window Management (X11R5): X Toolkit Intrinsics
    Location in Spec See Problem Text
    Problem Summary PIN4W.00021 This IR claims the test improperly tries to set a property using a widget that does not have that property.
    Problem Text
    In the standard Xt release from Xopen if the XtVaGetApplicationResources
    find a parameter of the type XtVaTypedArg it calls _XtTypedArgToArg
    to convert it to Arg. If the resource is not found it issues
    the warning:
    Warning: Unable to find type of resource for conversion
    and takes the default value.
    Please note: this problem will be reported to xbugs@x.org.
    Has the reference code of Xt passed the VSW5?
    I think, all vendors using the reference code (which I assume to be
    almost all) will have problem with this test.
    Test Output
    SECTION: Xt11

    TEST CASE: XtVaGetApplicationResources

    TEST PURPOSE #3
    10|2554 /tset/Xt11/tvagtares/Test 18:41:47|TC Start, scenario ref 1730-0
    VSW5TESTSUITE PURPOSE 3
    Assertion XtVaGetApplicationResources-3.(A)
    On a call to void XtVaGetApplicationResources(w, base,
    resources, num_resources,....) when the name XtVaTypedArg
    is specified in place of a resource name in the variable
    argument list it shall interpret the four arguments
    following this argument as a name/type/value/size tuple.
    PREP: Initialize toolkit, Open display and Create topLevel root widget
    PREP: Create windows for widgets and map them
    TEST: Retrieve resource values from arg list
    WARNING: ****************************************************************
    WARNING: An Xt warning occured during a toolkit call:
    WARNING: Unable to find type of resource for conversion
    WARNING: ****************************************************************
    TEST: Retrieved resource value
    ERROR: Expected "label value", received "XtDefaultLabel"
    FAIL

    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.

    If the WARNING generated by this test is a bug in the code it
    must be fixed. A PIN can not be granted for a bug.

    The ERROR generated by this test is caused by another issue entirely.
    But we still reccommend the request be refused based on the following
    logic.

    Our understanding is that the test is trying to set selected resource
    values in the "base" structure not in the widget, topLevel.

    topLevel is specified solely as a starting point for whatever work is
    necessary to build the resource database. Once this is finished the
    database becomes one of 3 locations searched for the resources
    specified; the argument list, the resource database and the default
    resource list (in order of precedence).

    Since the resource, XtNlabel, is assigned the value, "label value",
    in the argument list to the XtVaGetApplicationResources() call that
    value should take precedence and be assigned to base.label.

    The test results you include lead us to suspect that the default
    from the resource list, XtDefaultLabel, is being erroneously
    assigned.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    This is a known problem in the reference implementation
    and in line with our recent decision to align with
    existing technology we are granting a Permanent Interpretation.
    The problem is fixed in R6.4.

    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