GetTextNumLines() returns nil when called with unavailable font/fontsize
Before 4.10 Beta 1 calling GetTextNumLines() with an unavailable combination of a font and a fontsize, the function would return some values regardless (if at least the fontname was correct).
However, it then calculated the returned number of lines based on a different font size (which the caller couldn't determine directly). Hence, the output for this incorrect call was kind of meaningless to the caller.
This issue was fixed, by issuing an error in this case now and returning nil. Since calling the function with an unsupported font/fontsize is quite meaningless and it's almost impossible to mods to display any text with that invalid combination, we expect that no real world example is out there which runs into the error case.
If however you spot a problem because of this change, please let us know.
See:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Reduced number of visible table rows
In order to improve the performance of the engine, we introduced a feature for the UI to share the visual table rows. While this is fully transparent to modders/scripts it impacts how many table rows can be displayed at the same time on screen.
Before 4.10 Beta 1 the limit was 50 visible table rows for each table inside a view for each of the three addon environments. Hence in a Three-table-view each of the table had a limit of maximum 50 table rows (ultimately that's max: 3 x 50 x 3 visual table rows = 450 rows).
In 4.10 Beta 1 we share the rows within an addon environment alongside the tables, now. So the new limit is to have a max of 50 rows for all used tables inside a view. In other words: If you take a three-table view, you could create a top table with 10 visible table rows, a middle talbe with 30 table rows and a bottom table with 10 table rows). Note that this is only a limit for the actually visible table rows. There is no hard limit for table rows which are currently not displayed (hence all tables can still have more or less and endless amount of rows).
In practice we believe that even the reduced limit is impossible to reach in real world examples. Please let us know if you run into the limit here, though.