| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I'm seeking for more information how to use the Launch Application facility; especially how to use user-specified arguments. The user manual gives only a few examples and the mcc_common:*.def files don't use it. I would like to gain access to the attribute "TEXT FILE", which is part of the reference partition of each global class entity. I don't bother which class, I just want to easily type out the text file in attribute "TEXT FILE". I have tried using wildcard, but it doesn't work: argument:<*.!.TEXT FILE> I have tried using multiple arguments and specifying them as optional, but it doesn't work: Del_key:* Menu: Applications Button: Type Text_file shell:@mcc_common:type_text_file.com argument:*<NODE4.!.TEXT FILE>* argument:*<SNMP.!.TEXT FILE>* env_type: TERMINAL term_title: Text_file icon_label: Text_file Endmenu: I also don't understand why we have to specify the entity class in a user-specified argument; there is also a keyword "APPLIES_TO". Any help is appreciated. best regards, Roland
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4843.1 | remove the spaces and try again. | TOOK::MCPHERSON | pre-retinal integration | Thu Apr 08 1993 14:41 | 8 |
>I have tried using wildcard, but it doesn't work: > argument:<*.!.TEXT FILE> Try specifying it exactly like it looks in the dictionary (i.e. all scrunched together with no spaces): argument:<NODE4.!.TEXTFILE> | |||||
| 4843.2 | you can't pass arguments for multiple classes ina single def file | KAJUN::NELSON | Thu Apr 08 1993 15:23 | 25 | |
Unfortunately, the launch argument passing facility is limited at this time. The current implementation allows you to pass arguments to only one class at a time. Even though the reference attributes, and in particular, Text File, apply to every registered class, you need a separate launch definition file for each class. If you would like it to work differently, I suggest that you enter a requirement in the EMF_REQ notes conference. That is the medium monitored by product marketing and management for new feature requirements. <*.!.Text File> has no meaning, as the parser does not recognize the`*' as a wildcard character. As stated in the documentation (POLYCENTER Network Manager V1.3 USE manual, page 8-7(?): APPLIES_TO Specifies the global and/or child entitiees to which the application applies. This keyword is used when: . The method of launching the application is "double click". . The Operations menu is part of the Application Interface Definition | |||||
| 4843.3 | each Class needs a seperate Definition file | ZUR01::FUEGLISTER | Roland Fueglister, 760-2498 | Fri Apr 16 1993 13:47 | 18 |
Thank you for pointing out that the current solution is to create for each registered class a launch application definition file like the following: Menu: Operations Button: edit CLASS_Textfile applies_to: CLASS shell:@mcc_common:edit_textfile.com argument:<CLASS.!.TEXT FILE> env_type: TERMINAL term_title: Textfile icon_label: Textfile Endmenu: Best regards, Roland | |||||