In SpikerSoft Stacker, the Start Maximized setting fails to apply correctly when launching the application. Even though the option is enabled, the app opens in windowed mode instead of full-screen. The maximize icon in the top-right corner indicates that the window is already maximized, but visually, the app remains windowed until manually toggled.
Issue Description
When the Start Maximized checkbox is selected in the Settings → General tab, the application should launch in full-screen mode. However, upon startup, the window appears in a smaller, non-maximized state. The maximize icon shows the “restore down” symbol (indicating maximized mode), but the window dimensions do not fill the screen until the user manually clicks the icon.
Environment
Property
Value
Application
SpikerSoft Stacker
Module
Settings → General
Environment
Production
Operating System
Windows 11
Version
v2026.10.10e
Device
Desktop
Preconditions
User has Start Maximized enabled in settings.
Steps to Reproduce
Open Settings → General.
Enable Start Maximized.
Close and relaunch SpikerSoft Stacker.
Observe that the app opens in windowed mode, even though the maximize icon indicates otherwise.
Expected Result
The application should launch fully maximized, filling the screen.
The maximize icon should correctly reflect the window state.
Actual Result
The app opens in windowed mode.
The maximize icon shows the “restore down” symbol, implying maximized mode.
Manual interaction is required to achieve true full-screen display.
Evidence
Screenshot shows Start Maximized enabled in settings.
Upon launch, the app remains windowed despite the icon indicating maximized mode.
Impact
Minor usability issue affecting workflow consistency.
Causes confusion for users expecting full-screen startup behavior.
Frequency
Always
Reproducibility
100%
Severity
Low
Suggested Fix
Adjust window initialization logic to apply maximized state after rendering.
Verify that the window manager correctly interprets the maximize flag on startup.
Test across different resolutions and scaling settings to ensure consistent behavior.
## Summary
In **SpikerSoft Stacker**, the **Start Maximized** setting fails to apply correctly when launching the application. Even though the option is enabled, the app opens in **windowed mode** instead of full-screen. The maximize icon in the top-right corner indicates that the window is already maximized, but visually, the app remains windowed until manually toggled.
## Issue Description
When the **Start Maximized** checkbox is selected in the **Settings → General** tab, the application should launch in full-screen mode. However, upon startup, the window appears in a smaller, non-maximized state. The maximize icon shows the “restore down” symbol (indicating maximized mode), but the window dimensions do not fill the screen until the user manually clicks the icon.
## Environment
| Property | Value |
|-----------|--------|
| Application | SpikerSoft Stacker |
| Module | Settings → General |
| Environment | Production |
| Operating System | Windows 11 |
| Version | v2026.10.10e |
| Device | Desktop |
## Preconditions
User has **Start Maximized** enabled in settings.
## Steps to Reproduce
1. Open **Settings → General**.
2. Enable **Start Maximized**.
3. Close and relaunch **SpikerSoft Stacker**.
4. Observe that the app opens in windowed mode, even though the maximize icon indicates otherwise.
## Expected Result
- The application should launch fully maximized, filling the screen.
- The maximize icon should correctly reflect the window state.
## Actual Result
- The app opens in windowed mode.
- The maximize icon shows the “restore down” symbol, implying maximized mode.
- Manual interaction is required to achieve true full-screen display.
## Evidence
- Screenshot shows **Start Maximized** enabled in settings.
- Upon launch, the app remains windowed despite the icon indicating maximized mode.
## Impact
- Minor usability issue affecting workflow consistency.
- Causes confusion for users expecting full-screen startup behavior.
## Frequency
Always
## Reproducibility
100%
## Severity
Low
## Suggested Fix
- Adjust window initialization logic to apply **maximized state** after rendering.
- Verify that the window manager correctly interprets the maximize flag on startup.
- Test across different resolutions and scaling settings to ensure consistent behavior.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
In SpikerSoft Stacker, the Start Maximized setting fails to apply correctly when launching the application. Even though the option is enabled, the app opens in windowed mode instead of full-screen. The maximize icon in the top-right corner indicates that the window is already maximized, but visually, the app remains windowed until manually toggled.
Issue Description
When the Start Maximized checkbox is selected in the Settings → General tab, the application should launch in full-screen mode. However, upon startup, the window appears in a smaller, non-maximized state. The maximize icon shows the “restore down” symbol (indicating maximized mode), but the window dimensions do not fill the screen until the user manually clicks the icon.
Environment
Preconditions
User has Start Maximized enabled in settings.
Steps to Reproduce
Expected Result
Actual Result
Evidence
Impact
Frequency
Always
Reproducibility
100%
Severity
Low
Suggested Fix