Hypergrid v2.1.10
Please refer primarily to the Release Notes: v2.1.0 wiki page as well as the notes in the v2.1.2, v2.1.3, v2.1.4, v2.1.5, v2.1.6, v2.1.7, and v2.1.8 patches.
NOTE: There was no v2.1.9 release.
Patch release v2.1.10 reflects PR #718.
Bug fixes
- When the paint loop is not running (rarely used debug feature; not issues when paint loop is running normally):
behaviorShapeChangedandbehaviorStateChangedwere causing recursionreindex,behaviorShapeChanged,behaviorStateChangedwere not being called
- Remove defunct row and tree column elements when clearing
grid.renderer.visibleColumnsarray
New features
Added new boolean grid props to more finely control where grid lines are rendered (all true by default):
gridLinesColumnHeader— Whether vertical grid lines are drawn between column headers (pergridLinesV).gridLinesRowHeader— Whether horizontal grid lines are drawn between row headers (pergridLinesH).gridLinesUserDataArea— Whether vertical and/or horizontal grid lines are drawn between column headers (pergridLinesHandgridLinesV).
Column header grid lines
The lines drawn between column headers are now also subject to additional logic dictated by the top and bottom properties of the each column's element in grid.renderer.visibleColumns as follows:
- Respect new
.topprop when defined.
This is always set by thefin-hypergrid-grouped-header-pluginto prevent lines from being drawn over group labels. - Respect new
.bottomprop when defined.
Could be set to prevent lines from being drawn between column headers (i.e., the bottom row of a grouped header, below the hierarchy of group labels). When not set, a single grid line can be drawn for both the header and the user data area (pergridLinesUserDataArea); but when set (andgridLinesUserDataAreaset) two lines need to be drawn: one for the header, then the gap, then another line for the user data area. Although this feature was implemented,fin-hypergrid-grouped-header-plugin@1.1.2does not currently set.bottombecause the resulting visual effect was decidedly unpleasing. Nevertheless, the implementation remains in place and an option to set it could be added to the plug-in in a future version.
Published to npm
This release has been published as a module to the npm registry.
Pre-bundled build file
A bundled build of this release is available on the CDN.