Check index in wxItemContainer methods working with client data.
The test for index validity should be done by the base class public methods themselves so that the protected methods in the derived classes don't need to do it because this allows to have the check in one place only and not in every port-specific derived class and also because a protected method can reasonably expect to be called with already validated parameters. This makes it unnecessary to perform the same check in many derived classes and fixes the problem with those that forgot to check for item validity at all before (like wxGTK wxChoice). Also add a unit test checking for the correct behaviour. Unfortunately we don't have any way to test for the precise assert being triggered so the test passed for wxGTK wxChoice even before in debug builds because the expected assert was raised by wxArray::Item() but the code crashed in release build -- whereas now it doesn't any more. Closes #12858. git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@66664 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -170,6 +170,9 @@ void ItemContainerTestCase::ClientData()
|
||||
|
||||
CPPUNIT_ASSERT_EQUAL(static_cast<wxClientData*>(item2data),
|
||||
container->GetClientObject(2));
|
||||
|
||||
WX_ASSERT_FAILS_WITH_ASSERT( container->SetClientObject(-1, item0data) );
|
||||
WX_ASSERT_FAILS_WITH_ASSERT( container->SetClientObject(12345, item0data) );
|
||||
}
|
||||
|
||||
void ItemContainerTestCase::VoidData()
|
||||
@@ -195,6 +198,9 @@ void ItemContainerTestCase::VoidData()
|
||||
container->Insert("item 2", 2, item2);
|
||||
|
||||
CPPUNIT_ASSERT_EQUAL(item2, container->GetClientData(2));
|
||||
|
||||
WX_ASSERT_FAILS_WITH_ASSERT( container->SetClientData(-1, NULL) );
|
||||
WX_ASSERT_FAILS_WITH_ASSERT( container->SetClientData(12345, NULL) );
|
||||
}
|
||||
|
||||
void ItemContainerTestCase::Set()
|
||||
|
Reference in New Issue
Block a user