Progress
Programming
Handbook
Using Dynamic Widgets
Most applications do not require dynamic widgets other than windows, because widget definitions can be determined statically, at compile time. However, sometimes an application does not have all the information it needs to define a widget until run time. One example is an application that allows the user to add and remove buttons that duplicate menu functions. Another is an application that designs user interfaces for other applications, such as the Progress AppBuilder. All such applications require that you create and delete widget definitions at run time. For applications like these, you must use dynamic widgets.
This chapter describes the basic requirements and techniques for creating and managing dynamic widgets in a user interface, and how they differ from static widgets. These include techniques for managing dynamic widgets individually and as a group. For an introduction to defining static and dynamic widgets, see Widgets and Handles."
Some dynamic widgets require a more focused explanation than the general information described here. For information on dynamic menus and submenus, see Menus." For information on dynamic windows (all windows are dynamic except for the static default window), see Windows."
This chapter describes techniques for:
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |