This shouldn't have any external effects, since in practice a stacked_widget would always have at least
one layer visible. I just noticed this while trying to fix something else, and it seems a rather harmless
change.
Note it does change the internal policy method used for this generator.
The condition for this event wasn't working as intended before.
And since the injuried sergant is only used once and not as regular unit, he's now hidden in the help.
[ci skip]
It turned out that in AUTO_VISIBLE_FIRST_RUN mode, scrollbar_container
expects the scrollbar to be either visible or invisible. The code I added
in commit 9b1ca36b5c8ad353daf5881d65adfd8ba843381c made the scrollbar hidden instead, which
prevented a full relayout from occurring if the content grew afterwards.
Showing the scrollbar, in turn, depends on full relayout.
This issue only affected listboxes and not scroll labels,
which is why I didn't initially notice it.
The calls were there to work around automatic rewrapping of text caused by
a hack in `scroll_label::set_label()`. @Vultraz removed that hack in commit
ae76bb0efbc53f102cc772ace3941c5867e2c91c. After that, there wasn't any
reason to call `layout_initialise()` any more.
Well, other than that removal of scrollbars set as `AUTO_VISIBLE_FIRST_RUN`
relied on full layout initialization. I implemented a secondary, faster
mechanism for that.
This commit removes unnecessary code, and speeds up switching between
add-ons in the add-on manager further still.
The problem was that some widgets which wrap a grid didn't have their
cached sizes thrown away when the grid itself did. As a result, when the
parent grid of such a widget tried partial relayout, it discovered that the
widget fits just fine (according to the cached size) and attempted to lay
it out without shrinking it first. Then the grid found that it was given
much less space than it would prefer, and printed the error message.
Fixed by discarding cached sizes of such widgets.
fixup for 3d63f66dbb9e7cffec5376e044fc14b635d661c2
After this commit, all the wmlparser tests pass (including the new one) and the issue stated in #907 has also been verified to be fixed.
This fixes an issue where no click would register if using the GUI2 storyscreen dialog. Its removal doesn't seem
to have any effect on the GUI1 one either.
* add headers to "completely untranslated files" (translated files had
headers)
* added missing languages (fur/nb)
* ran a pot-update to verify everything works
I likely had this in to work around the labels not filling all available space before mordante made me realize
horizontal_grow = true was the way to go. Either way, we don't ever want a scrollable list here.
