Ensuring synchronization of animation and application

IBM® Rational® Rhapsody® assumes that you are following a certain programming style, outlined in the following notes. You are not forced to follow this style, but if you choose not to, be aware that the animation might get out of sync with the model.

For example, at times, it might be convenient to define a static attribute and use it directly for all class instances. Although it is not the most effective programming approach, it is a quick way to solve a number of problems. You can work this way if you prefer. However, be aware that the value of that attribute might not be updated properly during animation.

The following are standard style guidelines:

Note: On recovery, if you do not follow these guidelines and suspect that a view of a given object is inconsistent with its actual state, try closing the suspect view and reopening it. This action refreshes the view and synchronize it with the actual state of the object.

Feedback