User talk:Johan G/convert: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(→‎Parameter value missing: tricks learned while editing and using the template)
No edit summary
Line 26: Line 26:


:: --[[User:Wkitty42|Wkitty42]] ([[User talk:Wkitty42|talk]]) 14:12, 5 August 2018 (EDT)
:: --[[User:Wkitty42|Wkitty42]] ([[User talk:Wkitty42|talk]]) 14:12, 5 August 2018 (EDT)
i forgot to add, check out my sandbox play with this template [[User:Wkitty42/playing with convert template|here]] :)
--[[User:Wkitty42|Wkitty42]] ([[User talk:Wkitty42|talk]]) 14:16, 5 August 2018 (EDT)

Revision as of 18:16, 5 August 2018

Parameter value missing

does this template automatically add the to-unit units? in other words, if i "convert|100|mph|kts" will it put kts after the converted number?

also all i can get out of it is like seen on the convert page at the top where it just says "Parameter value missing" but i know they're there... see my experiment here...

--Wkitty42 (talk) 10:58, 4 August 2018 (EDT)

Hmm. Looking at the template I nearly immediately spotted the problem. I had used named parameters instead of unnamed/numbered parameters (i.e. using {{{value}}} in the template, requiring the value to be written as value=72 when "calling" the template instead of just 72 as was intended).
With that fixed the issue should be limited to "just" units not yet implemented. :-P
Johan G (Talk | contribs) 13:19, 5 August 2018 (EDT)
yes! it is working great! there are some tricks, though...


  • when using the template, you must have 5 |'s in the parameters.
  • if the exprn has round in it, you have to put a value, even zero, in the decimals field.
  • the hide field is the only field that can be empty.



--Wkitty42 (talk) 14:12, 5 August 2018 (EDT)


i forgot to add, check out my sandbox play with this template here :)

--Wkitty42 (talk) 14:16, 5 August 2018 (EDT)