Creating an object label for the current location: Difference between revisions
Jump to navigation
Jump to search
m (1 revision(s)) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Any subsystem can create an object label reference for its owning portal using the routine operation Label->Create SubSystem Label. | |||
This is very useful in cases where a parent portal has been dynamically copy/pasted and a portal contained therein needs to also be referenced using an object label reference. A routine executing within this other subsystem can allocate and obtain a label reference for that subsystem and store it in an attribute, in effect creating a "handle" to that subsystem. | |||
This helps avoid having to copy/paste systems in layers in order to get label references to subsystems deeper in the hierarchy which is copy/pasted. | |||
---- | |||
<font size="2">idkbase note 43</font> | |||
[[Category:Labellist]] | |||
[[Category:Labellist | |||
[[Category:Dynamic Structure]] | [[Category:Dynamic Structure]] | ||
[[Category:Object]] | |||
Latest revision as of 00:25, 13 January 2008
Any subsystem can create an object label reference for its owning portal using the routine operation Label->Create SubSystem Label.
This is very useful in cases where a parent portal has been dynamically copy/pasted and a portal contained therein needs to also be referenced using an object label reference. A routine executing within this other subsystem can allocate and obtain a label reference for that subsystem and store it in an attribute, in effect creating a "handle" to that subsystem.
This helps avoid having to copy/paste systems in layers in order to get label references to subsystems deeper in the hierarchy which is copy/pasted.
idkbase note 43