Clarify grid autobreak behavior
This commit is contained in:
@@ -24,10 +24,14 @@ Creation functions are context managers and accept common options such as `tag`,
|
||||
## Layout Helpers
|
||||
|
||||
- `gauge_panel(**config)`: child-window panel for grouped gauges.
|
||||
- `gauge_grid(columns=1, min_column_width=180, fit_gauges=True, **config)`: table-backed
|
||||
wrapping gauge grid. `columns` is the maximum number of columns. If the parent is narrower than
|
||||
`columns * min_column_width`, the grid uses fewer columns and wraps gauges onto later rows to
|
||||
avoid horizontal scrolling. Gauges without an explicit positive width fill their grid cell.
|
||||
- `gauge_grid(columns=1, min_column_width=180, fit_gauges=True, cell_padding=12, **config)`:
|
||||
table-backed
|
||||
wrapping gauge grid. Pass an integer `columns` to set the maximum column count; if the parent is
|
||||
narrower than `columns * min_column_width`, the grid uses fewer columns and wraps gauges onto
|
||||
later rows to avoid horizontal scrolling. Pass `columns="auto"` for autobreak mode, where the
|
||||
column count is derived entirely from the available width and `min_column_width`. Gauges without
|
||||
an explicit positive width fill their grid cell. Increase `cell_padding` if a custom Dear PyGui
|
||||
theme uses wider table padding or borders.
|
||||
|
||||
## Runtime API
|
||||
|
||||
|
||||
Reference in New Issue
Block a user