SmallJoker
SmallJoker
@Zughy I would like to fully understand the issue, thus requesting clarification by OP because the issue text does use the plural form: > the indeterminate `ProgressBar`**s** in the app...
I assume you'd like to detect shift-clicked [item image] buttons. As of now, only simple clicks can be registered though formspec callbacks. `ObjectRef:get_player_control` is likely not updated in formspecs, thus...
@grorp The apparent inner container size is currently defined by `factor * scrollbar_max`. As you also mentioned, this does not make any sense. Instead, the bounding box of the children...
> I agree that manually calculating these values is unnecessarily complicated. However, "the proper way" I described (constant scroll factor, `max` value based on content size) is also the way...
@grorp Updated as of c48341a7620ffa52. `thumbsize` and `max` are now based on the same calculations. The absolute scroll container size is also impractical to use (needs a placeholder in the...
@Desour > Should we maybe support content that is above 0? Although slightly hacky, modders can achieve the same thing by setting the scrollbar to a very high value, which...
@grorp I did the calculation. With PR, settings tab "Minetest Game", **visible area**  **hidden area**  600/398×162 = 244 px. Not pixel-perfect but from what I can see it's...
The same issue was reported for ContentDB in specific: #7408. Labels and checkboxes do not have an option two wrap text. Minetest's GUI layouting system is not really made for...
Would this be an acceptable solution: downscale the font size when the window gets too small. There is no way to make the text fit either way. Perhaps the same...
Would approximating the derivatives though a linear delta calculation not be precise enough? You can already get the noise value at a given position, thus checking the neighbours (table lookup)...