Window Class for OSButton

[tstalzer]

Hi

One of our customers is now migrating from VA/Smalltalk 7.02 to 7.52. The application is running under Windows.

During this version change, the Window class (Method windowClass) of OSButton changed from "OSButton" to "Button". This is definetly more correct, however the automated Testtool Integration (Silktest) now behaves a different as the class mapping has changed.

Now - my question:
The original implementation in the "initializeWindowProc" method declares the Windows-class "OSButton" and reroutes the default windowProc for buttons. In order to minimize the necessary changes for the Testteam, I would like to go back to the old implementation for the time being. Are there concerns in doing so (other than performance, not tested, etc.)

--Thomas

[wembley]

Thomas -

This change is covered in the Migration Guide. The WindowClass for 2 widgets was changed to be compatible with Windows Theme support. What I don't remember is whether there were other changes to the OSWidgets prompted by the change to the WindowsClass.

I can't guarantee nothing will break if you revert the code, but I think you will be OK.

[tstalzer]

Hi John

Thanks. I think we will roll back OSButton for a while until the testing department has a chance to rework the scripts. ( I know, I should have read the migration guides...)

For the record - they are using Silktest from Microfocus (former Borland, former Segue)

--Thomas