| 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 |
When selecting Customize Applications Definitions from the Session Manager Customize menu, the user must enter a Menu Item:, and a Menu Command:. I am finding problems when using certain characters as part of the Menu Item name. For example, although you are allowed to use an asterick in the menu item name, the menu command will not take. It will let you add the item and command, but the command will be lost. I also am seeing a problem with the period (.). I have a customer who likes to name his menu items prefaced with a dot. .FRANK for example. He can add his item and command succesfully, but notices two possible scenarios: 1-He'll go to the customzie application definition, and his application name will not show up. It does show up in the application menu, and he can run it. 2-He'll go to the customzie applicaiton definition and his application name WILL show up. He modifies the definition, and when he does an apply it fails saying 'you cannot modify a system definition'. This problem does not occur with all of the menu items he has added that start with a period, some are still working. I'm sure the problem is due to conflicts with the resource file, decw$sm_general.dat, as the dot and asterick are special characters for it. Is there a know list of which characters cannot or should not be used? Is this documented anywhere?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3613.1 | not related to xrm | DECWIN::JACKIE | news() { *Iraq+=*Kuwait; free(Kuwait); num_countries--; } | Fri Nov 09 1990 09:54 | 6 |
Command names and definitions are not related to the resource file, so I don't know why they are causing problems. Any more clues as to what works and what doesn't would be helpful. Did you use Command names like .FRANK in version 2? I'll forward this note to the developer. Jackie | |||||
| 3613.2 | CSC32::FORSMAN | Ginny Forsman 522-4731 CSC/CS | Fri Nov 09 1990 12:27 | 19 | |
Yes, it is v2. The reason I thought there would be a problem with the resource file is the commands that are added and written to decw$sm_general.dat in decw$user_defaults. I've pulled out the lines containing the .frank command. sm.frank.command: @loginn sm.applications: #kelly,*ginny,.frank,COMM,CSC32_MAIL,CSC32_NOTES,Comm,D sm.AppMenu: *ginny,.frank,COMM,CSC32_MAIL,CSC32_NOTES,Calculator,Calendar,C With the first line, sm.frank.command, where is the extra . , shouldn't we see two dots here? So far I have only seen problems using the dot, and asterisk. Thanks for your help. Ginny | |||||
| 3613.3 | illegal characters | DECWIN::JACKIE | news() { *Iraq+=*Kuwait; free(Kuwait); num_countries--; } | Mon Nov 12 1990 10:02 | 24 |
I replied to this on Friday, and later realized that I was only looking
at right hand side occurances of the strings. I've deleted my incorrect reply.
Here's the lines from the resource file:
sm.frank.command: @loginn
sm.applications: #kelly,*ginny,.frank,COMM,CSC32_MAIL,CSC32_NOTES,Comm,D
sm.AppMenu: *ginny,.frank,COMM,CSC32_MAIL,CSC32_NOTES,Calculator,Calendar,C
.frank is valid for the right hand side of the resource (after the colon)
but not for the left hand side. (sm.frank.command will make it look for
the command frank.) I guess this restriction should have been noted,
but this is all changed for version 3. By the way, #kelly is invalid also.
Here's the rules for valid resources: (p 349 Gettys DECpress book)
ResourceLine = Comment|ResourceSpec
Comment = "!"string|<empty line>
ResourceSpec = WhiteSpace ResourceName WhiteSpace ":" WhiteSpace value
ResourceName = [Binding] ComponentName {Binding ComponentName}
Binding = "."|"*"
WhiteSpace = {" "|"\t"}
ComponentName = {"a"-"z"|"A"-"Z"|"0"-"9"|"_"|"-"}
value = string
string = {<any character not including "\n">}
| |||||