Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop The Open Brand -- Problem Reporting and Interpretations System

Problem Report 2226 Details

Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 2226.

---

Report 2226 Actions Problem Report Number 2226 Submitter's Classification Test Suite problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.1141 Raised 1999-08-05 08:00 Updated 2003-03-13 08:00 Published null Product Standard Motif Toolkit Certification Program The Open Brand certification program Test Suite VSM version 4.1.3 Test Identification Widgets/XmFileXmSelectionBox 4 Specification Motif Toolkit API Problem Summary TSD4M.00048 I think I've mentioned before that the test case name is still wrong! The cause of the failures seen above is that the expected values are determined AFTER the callbacks have been called. From src/mv... Problem Text I think I've mentioned before that the test case name is still wrong! The cause of the failures seen above is that the expected values are determined AFTER the callbacks have been called. From src/mvslib/behavoir/Box.c l. 384 tn[2] = 9 ; tresult = 0 ; msg_prep("Move to Cancel, press/release Btn1, release"); mvsSetFocus(Box_widget, oUserDefined, 0, focus_mode); xisMovePointerTo(Box_widget, oCancelButton, 0, MoveAny); mvsClearCallbacks(); xisPressMouseButton( Btn1 ); xisReleaseMouseButton(Btn1); After this point, the Motif FileSelectionPB function is entered, which calls the qualifySearchDataProc, and then the registered callbacks. The mvsCallbackFunc makes a copy of the XmFileSelectionBoxCallbackStruct. In our implementation of the XmFileSelectionBox (and I can find nothing in the Motif spec that suggests that this is incorrect behaviour), after the callbacks have been called, if the button pressed was OK, or Cancel, the XmNdirSpec (or selection text field) is cleared. However, continuing the extract of code from the VSM test above: if(class_code == mvsXmFileSelBoxWidgetClass) { mvsFileSelPrepCbacks(Box_info); } tresult += mvsCheckCallbacksAndVisual(check_info); Hence the "expected" values are set to the now cleared text field, and are thus not in agreement with the values stored in the mvsCallbackFunc. I would have thought that it makes more sense to determine the expected values before generating the events that lead to the callbacks. Test Output VSM4TESTSUITE PURPOSE 4 The XmFileSelectionBox widget shall exhibit the behavior defined in the Motif Toolkit API specification. ERROR: Expected "" value string but received "foo_bar_and_grillEn un " value str ing for most recent callback XmNcancelCallback of widget XmFileSelectionBox of c lass xmFileSelectionBoxWidgetClass ERROR: Expected 35 length but received 58 length for most recent callback XmNcan celCallback of widget XmFileSelectionBox of class xmFileSelectionBoxWidgetClass ERROR: Expected "" value string but received "no" value string for most recent c allback XmNnoMatchCallback of widget XmFileSelectionBox of class xmFileSelection BoxWidgetClass ERROR: Expected 35 length but received 37 length for most recent callback XmNnoM atchCallback of widget XmFileSelectionBox of class xmFileSelectionBoxWidgetClass ERROR: Expected "" value string but received "foo_bar_and_grillEn un " value str ing for most recent callback XmNcancelCallback of widget XmFileSelectionBox of c lass xmFileSelectionBoxWidgetClass ERROR: Expected 35 length but received 58 length for most recent callback XmNcan celCallback of widget XmFileSelectionBox of class xmFileSelectionBoxWidgetClass ERROR: Expected "" value string but received "no" value string for most recent callback XmNnoMatchCallback of widget XmFileSelectionBox of class xmFileSelectio nBoxWidgetClass ERROR: Expected 35 length but received 37 length for most recent callback XmNno MatchCallback of widget XmFileSelectionBox of class xmFileSelectionBoxWidgetClas s ERROR: Expected "" value string but received "foo_bar_and_grillEn un " value st ring for most recent callback XmNcancelCallback of widget XmFileSelectionBox of class xmFileSelectionBoxWidgetClass ERROR: Expected 35 length but received 58 length for most recent callback XmNca ncelCallback of widget XmFileSelectionBox of class xmFileSelectionBoxWidgetClass ERROR: Expected "" value string but received "no" value string for most recent callback XmNnoMatchCallback of widget XmFileSelectionBox of class xmFileSelectio nBoxWidgetClass ERROR: Expected 35 length but received 37 length for most recent callback XmNno MatchCallback of widget XmFileSelectionBox of class xmFileSelectionBoxWidgetClas s ERROR: Expected "" value string but received "foo_bar_and_grillEn un " value st ring for most recent callback XmNcancelCallback of widget XmFileSelectionBox of class xmFileSelectionBoxWidgetClass ERROR: Expected 35 length but received 58 length for most recent callback XmNca ncelCallback of widget XmFileSelectionBox of class xmFileSelectionBoxWidgetClass ERROR: Expected "" value string but received "no" value string for most recent callback XmNnoMatchCallback of widget XmFileSelectionBox of class xmFileSelectio nBoxWidgetClass ERROR: Expected 35 length but received 37 length for most recent callback XmNno MatchCallback of widget XmFileSelectionBox of class xmFileSelectionBoxWidgetClas s Review Information Review Type TSMA Review Start Date null Completed null Status Complete Review Recommendation No Resolution Given Review Response A test suite deficiency is recommended. Review Type SA Review Start Date null Completed null Status Complete Review Resolution Test Suite Deficiency (TSD) Review Conclusion This is an agreed Test Suite Deficiency. Problem Reporting System Options: View Report 2226 List All PRs Search Reports Email the System Administrator View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority