| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (5 out of 6)

Managing User Preferences

 When GMS builds menus for a G2 window, it:

When GMS obtains and uses a User Preferences object, the identity of the user is significant only for determining which object to obtain. GMS thereafter manages user preferences by referencing the G2 window with which they are associated, not the user whose preferences they are.

To obtain the current User Preferences object:

Changing User Preferences

When you change the current User Preferences object, or register the user for a different User preference's object, the change does not take effect immediately: the previous preferences still exist in the menu instances, and the same User Preferences object is still associated with the G2 window.

Rebuilding menus inherently puts the new preferences into effect. You can also put new preferences into effect by modifying the existing menu instances, avoiding the overhead of rebuilding them. The new preferences can be specified by changing the current User Preferences object, or putting by another into effect.

To put changes to the current User Preferences object into effect:

To put a different User Preferences object into effect:

Switching preferences does not replace the User Preferences object for which the user is currently registered. Next time GMS rebuilds menus, that object will again take effect.

| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (5 out of 6)

Copyright © 1997 Gensym Corporation, Inc.