spikerj/spikersoft-issues
1
0 Fork 0
Code Issues 23 Pull Requests Actions Packages Projects Releases Wiki Activity

# [QoL Improvement] UI Flexibility and Layout Scaling for Low-End PCs at SpikerSoft Stacker #1138

New Issue
Open
opened 2026-09-14 01:12:53 +00:00 by enjin2310 · 2 comments
enjin2310 commented 2026-09-14 01:12:53 +00:00
Copy link
Copy source

Summary

The SpikerSoft Stacker application lacks adaptive UI scaling and layout flexibility for users with low-end PCs or smaller monitors. On displays with resolutions starting from 1280×640px, interface elements — particularly buttons and panels on the left side — appear overlapped or misaligned, reducing usability.

Issue Description

The current layout design assumes medium-to-high resolution screens, causing visual overlap and accessibility issues on smaller displays. Buttons and text labels in the Frames, Stacks, and Touch up panels become partially hidden or overlap each other. This limits functionality for users on laptops or older monitors with lower resolutions.

Environment

Property Value
Application SpikerSoft Stacker
Module UI / Layout
Environment Production
Operating System Windows 11
Version v2026.09.13
Device Desktop / Laptop (low-end specs)

Preconditions

User must be running the app on a monitor with resolution ≤ 1280×640px.

Steps to Reproduce

  1. Launch SpikerSoft Stacker on a low-resolution display (1280×640px or similar).
  2. Observe the layout of panels and buttons on the left side.
  3. Attempt to interact with overlapping UI elements.

Expected Result

The application should dynamically adjust its layout and scaling to fit smaller resolutions, maintaining proper spacing and visibility for all UI components.

Actual Result

  • Buttons and panels overlap on smaller screens.
  • Some elements become partially hidden or inaccessible.
  • The layout does not adapt to available screen space.

Evidence

  • The screenshot shows overlapping buttons and compressed panels on the left side of the interface.
  • The issue persists across multiple sections (Frames, Stacks, Touch up).

Impact

  • Reduces usability for users with low-end PCs or small monitors.
  • Limits accessibility and workflow efficiency.
  • Creates a poor user experience on non-standard resolutions.

Frequency

Always

Reproducibility

100%

Severity

Medium

Suggested Improvement

Implement responsive UI scaling and layout adjustments:

  • Introduce adaptive panel resizing based on screen resolution.
  • Add scrollable containers for panels with overflow content.
  • Optimize button spacing and font scaling for resolutions starting at 1280×640px and above.
  • Consider a compact mode for low-end devices to improve visibility and interaction.
## Summary The **SpikerSoft Stacker** application lacks adaptive UI scaling and layout flexibility for users with low-end PCs or smaller monitors. On displays with resolutions starting from **1280×640px**, interface elements — particularly buttons and panels on the left side — appear overlapped or misaligned, reducing usability. ## Issue Description The current layout design assumes medium-to-high resolution screens, causing visual overlap and accessibility issues on smaller displays. Buttons and text labels in the **Frames**, **Stacks**, and **Touch up** panels become partially hidden or overlap each other. This limits functionality for users on laptops or older monitors with lower resolutions. ## Environment | Property | Value | |-----------|--------| | Application | SpikerSoft Stacker | | Module | UI / Layout | | Environment | Production | | Operating System | Windows 11 | | Version | v2026.09.13 | | Device | Desktop / Laptop (low-end specs) | ## Preconditions User must be running the app on a monitor with resolution ≤ 1280×640px. ## Steps to Reproduce 1. Launch **SpikerSoft Stacker** on a low-resolution display (1280×640px or similar). 2. Observe the layout of panels and buttons on the left side. 3. Attempt to interact with overlapping UI elements. ## Expected Result The application should dynamically adjust its layout and scaling to fit smaller resolutions, maintaining proper spacing and visibility for all UI components. ## Actual Result - Buttons and panels overlap on smaller screens. - Some elements become partially hidden or inaccessible. - The layout does not adapt to available screen space. ## Evidence - The screenshot shows overlapping buttons and compressed panels on the left side of the interface. - The issue persists across multiple sections (Frames, Stacks, Touch up). ## Impact - Reduces usability for users with low-end PCs or small monitors. - Limits accessibility and workflow efficiency. - Creates a poor user experience on non-standard resolutions. ## Frequency Always ## Reproducibility 100% ## Severity Medium ## Suggested Improvement Implement responsive UI scaling and layout adjustments: - Introduce **adaptive panel resizing** based on screen resolution. - Add **scrollable containers** for panels with overflow content. - Optimize button spacing and font scaling for resolutions starting at **1280×640px** and above. - Consider a **compact mode** for low-end devices to improve visibility and interaction.
spikerj commented 2026-09-21 08:22:44 +00:00
Owner
Copy link
Copy source

Found and fixed a real layout collapse while investigating this — but I do not think it is what you reported, so I want to be straight about that rather than let a merge look like an answer.

What was wrong

egui hands each panel whatever the previous one left, so the frame strip and the inspector took their fixed widths regardless of window size and the stage's own pane absorbed the entire shortfall. The strip never yielded a single pixel — it measured 288px even inside a 320px window.

window stage pane before after
1440×900 800 800 (unchanged)
900×700 260 344
720×600 80 272
560×460 0 304
320×260 16 160

A content pane of zero width is a genuine defect, and spikerj/spikersoft-stacker#570 fixes it by budgeting the shell's width from the window each frame — content pane first, inspector yielding before the strip. Roomy windows are byte-for-byte unchanged.

Why this probably is not your bug

At 1280×640 the stage pane measures a healthy 640px both before and after the change. Your resolution does not reproduce the collapse. The symptom you described — controls overlapping inside the Frames / Stacks / Touch up panels — is at 1280×640 much more likely a height problem: 640px of vertical space against the menubar, toolbar and statusbar, which this change does not touch.

So #570 should not close this ticket, and I have left it open.

The one thing that would settle it

When you next see the overlap, could you tell me:

  1. Is the window maximized at 1280×640, or smaller than full screen? (If smaller, roughly how wide?)
  2. Do the controls overlap vertically — stacked on top of each other, running off the bottom — or are they squeezed side to side?

Vertical means I am looking in the wrong dimension entirely and I will go after the height budget instead. A screenshot of the whole window, rather than a photo of the screen, would answer both at once.

Also noting explicitly: compact mode, font scaling and scrollable panels are all still open parts of this request. #570 is one concrete defect found underneath it, not the whole thing.

Found and fixed a real layout collapse while investigating this — but **I do not think it is what you reported**, so I want to be straight about that rather than let a merge look like an answer. ## What was wrong egui hands each panel whatever the previous one left, so the frame strip and the inspector took their fixed widths regardless of window size and the stage's own pane absorbed the entire shortfall. The strip never yielded a single pixel — it measured 288px even inside a 320px window. | window | stage pane before | after | | --- | --- | --- | | 1440×900 | 800 | 800 (unchanged) | | 900×700 | 260 | 344 | | 720×600 | 80 | 272 | | 560×460 | **0** | 304 | | 320×260 | **16** | 160 | A content pane of zero width is a genuine defect, and spikerj/spikersoft-stacker#570 fixes it by budgeting the shell's width from the window each frame — content pane first, inspector yielding before the strip. Roomy windows are byte-for-byte unchanged. ## Why this probably is not your bug **At 1280×640 the stage pane measures a healthy 640px both before and after the change.** Your resolution does not reproduce the collapse. The symptom you described — controls overlapping inside the Frames / Stacks / Touch up panels — is at 1280×640 much more likely a *height* problem: 640px of vertical space against the menubar, toolbar and statusbar, which this change does not touch. So #570 should not close this ticket, and I have left it open. ## The one thing that would settle it When you next see the overlap, could you tell me: 1. Is the window **maximized** at 1280×640, or smaller than full screen? (If smaller, roughly how wide?) 2. Do the controls overlap **vertically** — stacked on top of each other, running off the bottom — or are they squeezed **side to side**? Vertical means I am looking in the wrong dimension entirely and I will go after the height budget instead. A screenshot of the whole window, rather than a photo of the screen, would answer both at once. Also noting explicitly: compact mode, font scaling and scrollable panels are all still open parts of this request. #570 is one concrete defect found underneath it, not the whole thing.
spikerj commented 2026-09-27 05:07:18 +00:00
Owner
Copy link
Copy source

Tracker sweep 2026-09-27 — partially done.

Landed: spikerj/spikersoft-stacker#570 (merged 09-21, a853cfd) budgets shell width so the stage pane can't collapse; #572 (merged 09-22) returns side panels to resting width. Both ship in stacker v2026.09.21d+ (latest v2026.09.26a). The maintainer's 09-21 comment says 1280x640 did NOT reproduce the width collapse and suspects a HEIGHT budget problem; asked the reporter (maximized? vertical vs horizontal overlap?) - no reply.

Remaining: Reporter (George) to retest on v2026.09.26a and answer the height-vs-width question; height budget for Frames/Stacks/Touch up panels at 640px, scrollable panels, compact mode and font scaling are all still undone.

**Tracker sweep 2026-09-27 — partially done.** Landed: spikerj/spikersoft-stacker#570 (merged 09-21, a853cfd) budgets shell width so the stage pane can't collapse; #572 (merged 09-22) returns side panels to resting width. Both ship in stacker v2026.09.21d+ (latest v2026.09.26a). The maintainer's 09-21 comment says 1280x640 did NOT reproduce the width collapse and suspects a HEIGHT budget problem; asked the reporter (maximized? vertical vs horizontal overlap?) - no reply. **Remaining:** Reporter (George) to retest on v2026.09.26a and answer the height-vs-width question; height budget for Frames/Stacks/Touch up panels at 640px, scrollable panels, compact mode and font scaling are all still undone.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
agentic
Actionable surfaced by the agentic architecture & security review
 bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 epic
Cross-repo epic — children live in per-repo trackers
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 sonarqube
Code quality issue surfaced by SonarQube (bug / code smell)
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
spikerj (Joseph Spiker)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#1138