Template:GM/prop/doc: Difference between revisions
< Template:GM | prop
Jump to navigation
Jump to search
(move remarks to Doc-page) |
m (move header title before "[Show/hide]" part in TOC - ("[Show/hide]" part in TOC being a unwelcome side effect)) |
||
| Line 16: | Line 16: | ||
---- | ---- | ||
=== <span class="mw-customtoggle-0" style="font-size:small; display:inline-block; float:right;"><span class="mw-customtoggletext">[Show/hide]</span></span> | === Def Remarks <span class="mw-customtoggle-0" style="font-size:small; display:inline-block; float:right;"><span class="mw-customtoggletext">[Show/hide]</span></span>=== | ||
<div id="mw-customcollapsible-0" class="mw-collapsible mw-collapsed"><pre> | <div id="mw-customcollapsible-0" class="mw-collapsible mw-collapsed"><pre> | ||
Code/system notes: | Code/system notes: | ||
Revision as of 07:48, 17 February 2019
Info
- Game-Menu supplement template.
- Property assignment on used menu's.
- Currently supporting up to 6 parameters. (anonymous type)
- (Only intended to be used from "Menu usage box" template.)
Usage
{{Menu_usage-set_prop|Parm1|Parm2|..|Parm6}}
Used By template
Def Remarks [Show/hide]
Code/system notes:
OLD: The parameter-number offset, between the #set and its leading #if part, is intentionally.
Effectively preventing setting the property on the last given GM-parameter (is object name ... makes no real sense for this property).
NEW: Menu-system seems to have changed (or potential is usage) in such a way that not including the last item makes no sense any more.
Not having the last item is also troublesome when checking the GM used data for potential outdated and/or misfit entries.
ISSUE: rethink if there is an other way to also store the last item(final-menu-items), including it with the others(sub-menu-items) bloats the "Unique data list" in such a way that it effectively becomes unusable. (storing last item is going to be reset in a day or two)
LATER1a: (on hold) Check if target property-name can be safely given as named-parameter here (probably. make sure).
LATER1b: (on hold) see about ditching separate legacy case of this template.