Skip to content

Fix AppKitProgressView auto-layout constraint warning#152

Merged
altic-dev merged 3 commits intoaltic-dev:mainfrom
veged:fix/progressview-autolayout-warning
Mar 15, 2026
Merged

Fix AppKitProgressView auto-layout constraint warning#152
altic-dev merged 3 commits intoaltic-dev:mainfrom
veged:fix/progressview-autolayout-warning

Conversation

@veged
Copy link
Copy Markdown
Contributor

@veged veged commented Feb 11, 2026

Description

Add .fixedSize() to all indeterminate ProgressView instances that lack an explicit frame. This resolves the SwiftUI/AppKit layout warning where floating-point precision causes min == max constraint to falsely fail:

has a maximum length (32.021493) that doesn't satisfy min (32.021493) <= max (32.021493)

Type of Change

  • 🐞 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📝 Documentation update

Related Issues

N/A — console warning only, no associated issue.

Testing

  • Tested on Intel/Apple Silicon Mac
  • Tested on Apple Silicon Mac
  • Tested on macOS [version]
  • Ran linter locally: brew install swiftlint && swiftlint --strict --confint.yml
  • Ran formatter locally: brew install swiftformat && swiftformat --config .swiftformat Sources

Screenshots / Video

N/A — this is a console warning fix with no visual changes. All ProgressView spinners render identically with .fixedSize().

@altic-dev
Copy link
Copy Markdown
Owner

would you able to fix the conflict ? happy to merge it :)

Add .fixedSize() to all indeterminate ProgressView instances that lack
an explicit frame. This resolves the SwiftUI/AppKit layout warning where
floating-point precision causes min == max constraint to falsely fail:

"has a maximum length (32.021493) that doesn't satisfy min (32.021493) <= max (32.021493)"

Co-authored-by: Cursor <cursoragent@cursor.com>
@veged veged force-pushed the fix/progressview-autolayout-warning branch from 52451c3 to eeca1a6 Compare February 12, 2026 13:52
@veged
Copy link
Copy Markdown
Contributor Author

veged commented Feb 12, 2026

would you able to fix the conflict ? happy to merge it :)

fixed

@altic-dev altic-dev merged commit af82b77 into altic-dev:main Mar 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants