-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI Redesign #81
Comments
Copied from my SwiftUI-Testing project
Manually scrolling back to the right page after rotate because I can't figure out how to get it to preserve scroll position properly
See https://github.com/Isvvc/Tickmate-PageView Make the number of days to show a static property of TickController (this will likely change in the future) Add a hex rub initializer to UIColor
Shows the first 4 tracks with accurate tick data. Ticking is not possible. Create shared instance of TrackController for UIKit views to access.
What's still left to be done in feature/#81/page-view
Edit: also changes from feature/#81/ui-rewrite-iOS-16, minus the iOS 16-only changes, and I think I've decided to revert those. |
Track fetch is performed on load and does not respond to updates using an FRC yet List of groups does not respond to FRC changes either
OK so I created feature/#81/ui-rewrite-iOS-16 which would set the minimum version to iOS 16 so I could use |
Originally the redesign was being done in SwiftUI in #79, but there are too many performance issues. I don't think SwiftUI was designed to draw this many shapes on screen at once. Unless there's something else I'm doing wrong idk.
The more days I would add the laggier it would get, even with
LazyVStacks
. The current app goes back 1 year, but I kept having to cut that number down as more features were added to the redesign.My current plan is to more-or-less start over, using the same design, but implementing it in UIKit. Doing it with a
UITableView
would allow me to reuse the rows for much better performance and allow an indeterminate number of days in the backlog.The text was updated successfully, but these errors were encountered: