If your application contains user-written code from Versions 3.0 or 3.5, you might have to update it so that it meshes properly with generated code. In addition, several key member functions are being marked obsolete, so although you are not required to update your code in this release, you might want to do it anyway. A general list of changes that affect user-written code follows.
For example, suppose member function or custom logic code sets the label of an IPushButton* part, named MyButton, that is embedded into a part called MyPart. The current code looks something like this:
iMyButton -> setText("Update");
Generated code for the push button now appears in an implementation class associated with MyPart called fImpl, so your code needs to look like this:
fImpl -> iMyButton() -> setText("Update");
The current event signal looks something like this:
notifyObservers(INotificationEvent(SomeClass::someId, *this, true, (void*)&someEventData));
The preferred form for an event signal now looks something like this:
notifyObservers(INotificationEventFor<someEventDataType>(IInterest(*this, someId), someEventData) );
Generated Code
Using Parts from Previous
Versions of VisualAge
VisualAge User Interface
Parts
