Difference between revisions of "Template:Ability (LW2)"

From UFOpaedia
Jump to navigation Jump to search
m
m (Does a line break here fix them all?)
Line 1: Line 1:
<div align="center"><div style="position: relative; top:15px;">[[File:{{{ s_image }}}|32px| {{{s_caption|}}}]]</div>{{ #ifexpr: {{{ b_info | 0 }}} | <div style="position: relative; left: 18px;">[[File:Icon_Skill_Info.png|18px|{{{s_info|}}}]]</div>}}</div>{{ #ifexpr: {{{ b_name | 1 }}} or {{{ b_descr | 0 }}} | <div style="text-align: {{{align|center}}}; {{ #ifexpr: ( {{{ b_name | 1 }}} or {{{ b_descr | 0 }}} ) and not {{{ b_info | 0 }}} | position: relative; top: 18px; | }}"> {{ #ifexpr: {{{ b_name | 1 }}} | '''{{{s_name|PerkName}}}'''<br/> | }} {{ #ifexpr: {{{ b_descr | 0 }}} | ''{{{s_descr|PerkDescription}}}'' | }}</div> | }}
+
<div align="center"><div style="position: relative; top:15px;">[[File:{{{ s_image }}}|32px| {{{s_caption|}}}]]</div>{{ #ifexpr: {{{ b_info | 0 }}} | <div style="position: relative; left: 18px;">[[File:Icon_Skill_Info.png|18px|{{{s_info|}}}]]</div>}}</div>{{ #ifexpr: {{{ b_name | 1 }}} or {{{ b_descr | 0 }}} | <div style="text-align: {{{align|center}}}; {{ #ifexpr: ( {{{ b_name | 1 }}} or {{{ b_descr | 0 }}} ) and not {{{ b_info | 0 }}} | position: relative; top: 18px; | }}"> {{ #ifexpr: {{{ b_name | 1 }}} | '''{{{s_name|PerkName}}}'''<br/> | }} {{ #ifexpr: {{{ b_descr | 0 }}} | ''{{{s_descr|PerkDescription}}}'' | }}</div> | }}<br />
  
 
<noinclude>
 
<noinclude>

Revision as of 20:36, 27 January 2017

[[File:{{{ s_image }}}|32px| ]]
PerkName



Skeleton:

{{Ability_(LW2)
| s_image =
| s_caption = 
| s_name = 
| s_descr =
| s_info =
| b_name = {{{ b_name }}}
| b_descr = {{{ b_descr }}}
| b_info = {{{ b_info }}}
}}

Bugs

If using this in Template:Class_Tree_(LW2) you need to add a line break after this template.

If this template is used inside a Template:Class_Tree_(LW2) and b_info is not true, then for some blasted reason the text overflows the cells. With b_info set, the text behaves and stays inside the table's cells as they should. (How very, very annoying.)

The text also behaves if this template is instead used inside a subst: version of the Class_Tree template. It could be some weird issue with the parser/template-rendering-parsing-dohicky.

Update: It appears that for some reason, the subst: version has a bunch of line breaks it in the source code. Weird.