winTerm 1.1.2

winTerm 1.1.2

winTerm 1.1.2 fixes the ghost pane-divider lines visible in 1.1.1 while
preserving the complete border-drag pane-resize feature set.

Fixed

• In 1.1.1 the visible pane divider could render away from the actual split
  boundary — for example a full-height vertical line inside the larger pane
  while the real vertical split sat farther left. The visible line used a
  primary-axis Center alignment combined with a leading-edge margin, so XAML
  re-centered it in the space remaining after the margin while the drag hit
  target stayed on the real boundary.
• The visible divider, the pointer target, and the logical split position now
  share one owner-local, leading-edge coordinate system: vertical dividers
  align Left and horizontal dividers align Top, offset by the split position
  minus half the line's own thickness.
• Exactly one divider line renders at each logical split boundary, and a
  nested divider stays visually confined to its owning split node instead of
  crossing unrelated sibling panes.

Preserved behavior

• One logical-pixel idle divider with a centered 12-logical-pixel pointer
  target and east-west / north-south resize cursors.
• Continuous live resize with minimum-size clamping and snapping at 25%,
  33.333%, 50%, 66.667%, and 75%; holding Alt bypasses snapping.
• Escape and pointer-cancellation rollback, one history record per committed
  drag, Undo, Redo, and Balance Panes.
• High Contrast divider brushes, hover and active-resize feedback, and compact
  pane headers.

Compatibility

Workspace schema remains version 2, the docking model remains version 1, the
shell protocol remains version 1, and the theme schema remains version 1.
Existing settings and workspaces load unchanged, and no pane session restarts
during a resize. Package identity, the winterm.exe alias, privacy
boundaries, and Microsoft Terminal coexistence are unchanged.

Distribution

Primary x64 assets:

• winTerm-1.1.2-setup-x64.exe
• winTerm-1.1.2-portable-x64.zip

Publisher: helloThisWorld. Tag: v1.1.2.

Signing

Unless a trusted Authenticode certificate is configured in the release
workflow at publication time, the v1.1.2 Setup EXE is not code-signed. Windows
may display a SmartScreen warning; verify the downloaded file against
SHA256SUMS.txt before running it.