| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
Looking for the best way....
I'm currently writing a DECWindows based menu for my group. That's
all nice and good. However, some people don't like to see all the
options that are on the menu. That's not all nice and good.
What I'm looking for is the best way to handle this problem. The two
options that I see are:
1) Do not even create the option widgets to begin with
- or -
2) Remove the widgets once they have been created.
Which options to be seen will be determined by a data file of sorts.
That's not important.
I'm using the UIL to define my DECWindows form. I have one main window
and 6 menu choices and 1 exit choice. All of the choices are push
buttons and the main window is a dialog box and all hang off of the
main window dialog box. I pretty much follow the examples of creating
and mapping the widgets outlined in the examples in DECW$EXAMPLES.
If anyone has had to do this, or has any ideas on the best way to
handle this situation, please, please, please let me know. I've
been trying different things so long I'm starting to lose it.
Any and all advice will be greatly appriciated.
Thanks in advance
Greg Bailey
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1841.1 | Is as easy as cake! | GSRC::WALLACE | I bark, therefore I am. -- Descartes dog. | Tue Dec 05 1989 00:26 | 22 |
>> What I'm looking for is the best way to handle this problem. The two >> options that I see are: >> 1) Do not even create the option widgets to begin with >> 2) Remove the widgets once they have been created. >> Which options to be seen will be determined by a data file of sorts. >> That's not important. >> >> I'm using the UIL to define my DECWindows form. I have one main window >> and 6 menu choices and 1 exit choice. All of the choices are push >> buttons and the main window is a dialog box and all hang off of the >> main window dialog box. I pretty much follow the examples of creating >> and mapping the widgets outlined in the examples in DECW$EXAMPLES. The best way to do this as I've been doing for our customer is to create all the push buttons in UIL and fetch/manage each as your data file dictates. This way each user will have only the buttons that are needed. As all these are on the menu bar, parent all the push buttons to the menu bar. Volia! Custom menu push buttons per user. Is as easy as cake, no? Aloha, Richard | |||||