6,576
edits
![]() |
Progress Continues
We've already had 21777 updates since Dolphin 5.0. Keep up with Dolphin's continuing progress through the Dolphin Blog: February, March, and April 2024 Dolphin Progress Report. |
![]() |
The Dolphin Emulator Wiki needs your help! Dolphin can play thousands of games, and changes are happening all the time. Help us keep up! Join in and help us make this the best resource for Dolphin. |
mNo edit summary |
|||
Line 70: | Line 70: | ||
:Gecko template really need a way to display output in pre tags. I can't think of any other use-cases that need this, but preferably not, I can see this becoming rival against Gecko template. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 01:15, 7 January 2018 (CET) | :Gecko template really need a way to display output in pre tags. I can't think of any other use-cases that need this, but preferably not, I can see this becoming rival against Gecko template. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 01:15, 7 January 2018 (CET) | ||
::It screws up the documentation on the page though by consuming the includeonly tags, leaving that empty code box at the top of the page. I don't see how a workaround template here would compete with the gecko template, we already have a few smaller templates for stuff like this like [[Template:Hover]], so there's precedent. - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 09:31, 8 January 2018 (CET) | ::It screws up the documentation on the page though by consuming the includeonly tags, leaving that empty code box at the top of the page. I don't see how a workaround template here would compete with the gecko template, we already have a few smaller templates for stuff like this like [[Template:Hover]], so there's precedent. - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 09:31, 8 January 2018 (CET) | ||
:::Luckily I don't think the weird bar we see above is distracting. When I said Pre template would compete Gecko template I meant that users might use Pre templates for their Geck codes. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 21:41, 8 January 2018 (CET) | :::Luckily I don't think the weird bar we see above is very distracting. When I said Pre template would compete Gecko template I meant that users might use Pre templates for their Geck codes. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 21:41, 8 January 2018 (CET) | ||
== Widescreen == | == Widescreen == | ||
Line 76: | Line 76: | ||
:Which game? It looks like there are variety cheat description for 16:9 code than I though. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 23:40, 7 January 2018 (CET) | :Which game? It looks like there are variety cheat description for 16:9 code than I though. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 23:40, 7 January 2018 (CET) | ||
::[[Lemony Snicket's A Series of Unfortunate Events]] is one game that needs the widescreen hack. I'm sure I've seen it on other more high profile games too, but I can't think of them off the top of my head. Maybe add a <code>|widescreenhack=true</code> or <code>false</code> into the template for 16:9, then have a sentence like "Make sure the widescreen hack is '''disabled''' / '''enabled'''" depending on what it's set to? - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 09:14, 8 January 2018 (CET) | ::[[Lemony Snicket's A Series of Unfortunate Events]] is one game that needs the widescreen hack. I'm sure I've seen it on other more high profile games too, but I can't think of them off the top of my head. Maybe add a <code>|widescreenhack=true</code> or <code>false</code> into the template for 16:9, then have a sentence like "Make sure the widescreen hack is '''disabled''' / '''enabled'''" depending on what it's set to? - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 09:14, 8 January 2018 (CET) | ||
:::Thanks, but I'm not comfortable with having another parameter to determine between disabled/enabled requirement for the widescreen code. The sentencing is awkward, I think using a generic cheat description is better suited for the code that requires widescreen hack, it may trigger a "not 16:9" category, but that seems okay to me as it's | :::Thanks, but I'm not comfortable with having another parameter to determine between disabled/enabled requirement for the widescreen code. The sentencing is awkward, I think using a generic cheat description is better suited for the code that requires widescreen hack, it may trigger a "not 16:9" category, but that seems okay to me as it's an incomplete code that doesn't do 16:9 yet. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 21:35, 8 January 2018 (CET) |
edits