We don't want markup in any of the other fields. I still need to find a slightly better solution for the name
field, though. We don't want users to be able to use markup unnecessairly, but we do need markup to highlight
the names of ready-to-upload addons.
This fixes warnings about unescaped ampersands in the Author field.
that commit onyl changed the resolution choosing procedure for windows
not for widgets which made that code more complicated. This commit also
addsa workaround for < 800x600 widgets to the c++ code so that we no
longer have to think about this in the .cfg files
The previous commit adding a new library to the Library tab causes a
vertical scrollbar to appear there and somehow make the tab selector
overflow and get a vertical scrollbar. Vultraz suggested this fix and
seems to be aware that it doesn't solve preexisting issues with overlong
tab labels/translations.
I'll let @vultraz pretty it up a little if he wants.
Note that old saves won't show this info; it'll only show up in new saves.
It might show up for old saves if you clear your cache, though.
This was a dialog used early in 1.13 during the SP/MP codepath unification to configure certain options.
The modification selection is now built into the Selection dialog, and we decided not to enable other options
like Era selection in SP. The only option we might look to restoring in the future is the "show_connect"
option, but that requires some additional code elsewhere and probably won't be used anyway.
In addition to an interface update, this also makes the dialog work better with the editor, with improvements
such as restoring the currently selected ToD when the dialog exits (until we implement the saving of changes
made within the dialog) and opening to the same.
The menu_button is now only a drop-down menu that supports a single selection.
A new multimenu_button widget supports a drop-down menu with multiple selections.
The new multimenu_button widget displays its current selection while not open.
although stacked_widget supports similar functionality this is currently
not easily doable from the lua gui2 api. In particular
1) stacked_widget cannot add pages dynamically
2) multi_page can only contain one type of widget.
3) a stacked_widget inside a multi_page is ineffective since it
generates many unused widgets
4) a multi_page inside a stacked_widget is just unhandy to use
