Age | Commit message (Collapse) | Author |
|
|
|
closures (#8282)
|
|
(#8320)
|
|
Some places in the codebase misspell 'Viewport' as 'ViewPort' or 'view_port'.
This patch makes everything consistent.
|
|
|
|
|
|
This is to avoid needing to expensively regenerate name strings on
every comparison when sorting by name in the town/station/industry
list windows.
|
|
|
|
In the case where multiple industries have the same name, sorting
in the industry directory window is non-deterministic.
This results in the order changing on each re-sort, and is noticeable
when the industries have different production or transported values.
|
|
it temporarily does not accept the cargo selected by the acceptance cargo filter.
|
|
window's cargo lists
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
AutoDeleteSmallVector obsolete.
DropDownListItem are strongly managed using std::unique_ptr to ensure leak-free handling. Appropriate use
of move-semantics make intent a lot clearer than parameter comments and allows the compiler to generate
copy-free code for most situations.
|
|
|
|
|
|
std::vector::[push|emplace]_back()
|
|
|
|
|
|
|
|
|
|
This is fixed by handling the new Window::OnTooltip() event instead of OnHover()
|
|
Change the window to use a dynamically generated string of cargoes,
instead of one of a few fixed-length lists. With up to 16 cargoes
on each list, having 16 with the only difference how many are listed
seems like a bad maintenance idea.
|
|
|
|
timers to work with milliseconds instead of ticks.
|
|
number of cargoes in/out isn't large either
|
|
|
|
|
|
|
|
|
|
|
|
|
|
view based on cb37 result type.
Industry-sets that have no stockpiling get better control over the displayed accepted cargo information.
- result 0401 only prints the accepted cargo
- results 0800-0BFF prints the accepted cargo and a string (but not the amount)
|
|
|
|
|
|
|
|
buttons with non-static width.
|
|
|
|
active in multiplayer for desync reasons, even when activated in singleplayer previously
|
|
|
|
"unsafe" functions to prevent them from being used, and thus having to care about certain aspects of their return values
|
|
in the TextRefStack.
|