T.R | Title | User | Personal Name | Date | Lines |
---|
308.1 | allowed on entities | TOOK::HAO | | Thu Sep 06 1990 11:01 | 6 |
| Full instance wildcarding on entities is allowed by FCL, regardless
of what the datatype is. Partial instance wildcarding is only allowed
on those entities whose instance datatype supports wildcarding.
Christine
|
308.2 | instance wildcards | GOSTE::CALLANDER | | Thu Sep 06 1990 13:33 | 15 |
| The SRM might not do a good job of it, but the next version of the
SRM clarifies it.
The wildcarding rules listed in the data types chapter are specific
to the data type. In addition to these rules further explainations
have been added to explain the entity wildcard (for full instance
wildcarding) is independent of the data type. To support this the
wildtype parameter was added to the AES routines so that this type
of information could be encoded regardless of datatype and identifier.
But note that this is only for FULL instance wildcarding. If you
want to do partial wildcarding on an entity instance, then the
wildcarding rules specified for the identifiers data type DO apply.
|
308.3 | DECwindows and wildcarding? | MICROW::LANG | | Tue Apr 07 1992 13:35 | 15 |
| >Full instance wildcarding on entities is allowed by FCL,regardless
>of what the datatype is. Partial instance wildcarding is only allowed
>on those entities whose instance datatype supports wildcarding.
Is this true for DECwindows too?
How is the information passed to the MM? Do the AES calls
support wildcarding for any datatype and are there
other implications of support that is missing because the
datatype itself does not support wildcarding?
thanks,
Bonnie
|
308.4 | wildcarding==multi selections in map | TOOK::CALLANDER | MCC = My Constant Companion | Mon May 11 1992 16:22 | 3 |
| wildcarding in the map is done through explict multiple icon
selections. So the internal premise is a bit different.
|