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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 2160 Actions

    Problem Report Number 2160
    Submitter's Classification Specification problem
    State Resolved
    Resolution Temporary Interpretation (TIN)
    Problem Resolution ID TIN.X.0100
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1998-03-15 08:00
    Product Standard Motif Toolkit
    Certification Program The Open Brand certification program
    Test Suite VSM version 1.0.0
    Test Identification Functs/XmGetMenuCursor/XmGetMenuCursor 1
    Specification Motif Toolkit API
    Location in Spec See Problem Text
    Problem Summary TIN4M.00007 The test is checking the behaviour according to the spec, which is correct behaviour for test case. However, it seems that CAE specification has conflicting requirements. According to specification, t...
    Problem Text
    The test is checking the behaviour according to the spec, which is
    correct behaviour for test case. However, it seems that CAE
    specification has conflicting requirements.

    According to specification, the menu cursor resource is to be defined
    in XmScreen widget, and not XmRowColumn Widget. And Specification
    requires that by default the value of XmNmenuCursor resource of
    XmScreen widget be "arrow" and not NULL. The XmScreen widget is
    created automatically when XtAppCreateShell() is called. (to see the
    stack, refer to tmp waiver MSF4M.00001)

    XmGetMenuCursor() and XmSetMenuCursor() functions are for getting and
    setting the XmNmenuCursor resource of XmScreen widget respectively.




    I believe that XmGetMenuCursor() is not intended to check if a
    rowcolumn widget is created in application or not. And hence, it
    should retrieve and return the value stored in XmScreen widget
    structure without modifying its value.

    In this circumstances, XmGetMenuCursor() output should not depend on
    the existance of XmRowColumnWidget in application.

    Test Output
    TEST CASE: XmGetMenuCursor

    TEST PURPOSE #1
    A call to Cursor XmGetMenuCursor(Display *display)
    before the application has created any menus on the
    specified display shall return None.
    PREP: Initialize Xt
    TEST: Call XmGetMenuCursor
    TEST: Return value
    ERROR: Cursor returned was not None
    1 FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We agree with the applicant and recommend that a TIN be granted.


    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    A non-alignment between the reference code and its specification is
    under investigation. Thus it is recommended that a Temporary
    Interpretation be granted for this test while it remains subject to review.
    If a change to the specification results from the conclusion of this
    investigation, then this Temporary Interpretation will be converted
    to a Permanent Waiver. Otherwise this Temporary Interpretation will
    be converted to a Temporary Waiver (Minor System Fault).


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

    Applicability: VSM4.0.0 only.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority