User talk:Johan G/convert: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(does template add trailing units to results? also only get red "value missing" error)
 
(→‎Parameter value missing: Seems I made quite a blunder with the template draft. Now the issue should just be conversions not yet implemented.)
Line 1: Line 1:
== 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?
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?


Line 4: Line 5:


--[[User:Wkitty42|Wkitty42]] ([[User talk:Wkitty42|talk]]) 10:58, 4 August 2018 (EDT)
--[[User:Wkitty42|Wkitty42]] ([[User talk: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 <code><nowiki>{{{value}}}</nowiki></code> in the template, requiring the value to be written as <code><nowiki>value=72</nowiki></code> when "calling" the template instead of just <code><nowiki>72</nowiki></code> as was intended).
: With that fixed the issue should be limited to "just" units not yet implemented. :-P
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:19, 5 August 2018 (EDT)

Revision as of 17:20, 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)