Changeset View
Changeset View
Standalone View
Standalone View
binaries/data/mods/public/gui/lobby/lobby.xml
Context not available. | |||||
size="0 0 100% 100%" | size="0 0 100% 100%" | ||||
font="sans-bold-stroke-13" | font="sans-bold-stroke-13" | ||||
> | > | ||||
<column id="buddy" width="12"> | |||||
<translatableAttribute id="heading">■</translatableAttribute> | |||||
elexis: Don't need to translate an empty string I propose | |||||
</column> | |||||
<column id="status" width="26%"> | <column id="status" width="26%"> | ||||
<translatableAttribute id="heading">Status</translatableAttribute> | <translatableAttribute id="heading">Status</translatableAttribute> | ||||
</column> | </column> | ||||
<column id="name" width="48%"> | <column id="name" width="45%-12"> | ||||
<translatableAttribute id="heading">Name</translatableAttribute> | <translatableAttribute id="heading">Name</translatableAttribute> | ||||
</column> | </column> | ||||
<column id="rating" width="26%"> | <column id="rating" width="26%"> | ||||
Context not available. | |||||
</column> | </column> | ||||
<action on="SelectionChange"> | <action on="SelectionChange"> | ||||
displayProfile("lobbylist"); | displayProfile("lobbylist"); | ||||
unhideToggleBuddy(this); | |||||
</action> | </action> | ||||
<action on="SelectionColumnChange"> | <action on="SelectionColumnChange"> | ||||
updatePlayerList(); | updatePlayerList(); | ||||
Context not available. | |||||
</object> | </object> | ||||
<object name="leftButtonPanel" size="20 100%-75 20% 100%-20"> | <object name="leftButtonPanel" size="20 100%-75 20% 100%-20"> | ||||
<object name="leaderboardButton" type="button" style="ModernButtonRed" size="0 0 100% 25"> | <object name="toggleBuddy" type="button" style="ModernButtonRed" size="0 100%-85 100% 100%-60" hidden="true"> | ||||
<translatableAttribute id="caption" comment="Toggle Buddy">Toggle Buddy</translatableAttribute> | |||||
<action on="Press"> | |||||
toggleBuddy(); | |||||
</action> | |||||
Not Done Inline ActionsI know we rejected doubleclick before, in particular since the feature might go entirely unnoticed if we didn't have a button instead, but IMO it is great to have both the button and the doubleclick feature, so we can quickly set many buddies without moving the mouse over half the screen. We can remove it later if we want to use doubleclicking for something else. elexis: I know we rejected doubleclick before, in particular since the feature might go entirely… | |||||
</object> | |||||
<object name="leaderboardButton" type="button" style="ModernButtonRed" size="0 100%-55 100% 100%-30"> | |||||
<translatableAttribute id="caption">Leaderboard</translatableAttribute> | <translatableAttribute id="caption">Leaderboard</translatableAttribute> | ||||
<action on="Press"> | <action on="Press"> | ||||
Engine.SendGetBoardList(); | Engine.SendGetBoardList(); | ||||
Context not available. | |||||
displayProfile("leaderboard"); | displayProfile("leaderboard"); | ||||
</action> | </action> | ||||
</object> | </object> | ||||
<object name="userprofileButton" type="button" style="ModernButtonRed" size="0 30 100% 100%"> | <object name="userprofileButton" type="button" style="ModernButtonRed" size="0 100%-25 100% 100%"> | ||||
<translatableAttribute id="caption">User Profile Lookup</translatableAttribute> | <translatableAttribute id="caption">User Profile Lookup</translatableAttribute> | ||||
<action on="Press"> | <action on="Press"> | ||||
Engine.GetGUIObjectByName("profileFetch").hidden = false; | Engine.GetGUIObjectByName("profileFetch").hidden = false; | ||||
Context not available. | |||||
<action on="SelectionChange">updateGameSelection();</action> | <action on="SelectionChange">updateGameSelection();</action> | ||||
<action on="SelectionColumnChange">applyFilters();</action> | <action on="SelectionColumnChange">applyFilters();</action> | ||||
<action on="mouseleftdoubleclickitem">joinButton();</action> | <action on="mouseleftdoubleclickitem">joinButton();</action> | ||||
<column id="name" color="0 60 0" width="27%"> | <column id="buddy" width="12"> | ||||
<translatableAttribute id="heading">■</translatableAttribute> | |||||
Not Done Inline Actionssame elexis: same | |||||
</column> | |||||
<column id="name" color="0 60 0" width="27%-12"> | |||||
<translatableAttribute id="heading">Name</translatableAttribute> | <translatableAttribute id="heading">Name</translatableAttribute> | ||||
</column> | </column> | ||||
<column id="mapName" color="128 128 128" width="25%"> | <column id="mapName" color="128 128 128" width="25%"> | ||||
Context not available. |
Wildfire Games · Phabricator
Don't need to translate an empty string I propose