mikeyenco.bsky.social
Designer of macOS, iOS, and iPadOS apps. Composer of songs.
http://www.yenco.com
312 posts
648 followers
655 following
Regular Contributor
Active Commenter
comment in response to
post
This is awesome and I'm excited to go through it 🙂👍. Thank you so much… but I wish it was a video because I miss watching the dogs come in looking for treats at just the right time to prevent info overload. 🙁 (they are so very clever).
comment in response to
post
I'm still disappointed that with all of the talk of bringing consistency across OS 26 the macOS 26 graphical DatePicker still looks as vomit-inducing as ever (don't think this could even pass Apple HIGs). Sad when compared to the awesome one in iOS/iPadOS.
comment in response to
post
Built some custom SF Symbols in Sketch for one of my Xcode projects with the export template (right before Apple simplified things to auto-generate between weights 😫). Haven't had a chance to play with the newer layering stuff for animation, color, etc. or trying to put them in the app.
comment in response to
post
Here's how the icon for my test project turned out:
comment in response to
post
… or tryi ng to be con sist ent ac ross pla tfor ms w ith OS2 6 rel ea ses. 🤔
comment in response to
post
Y eah who ca res abo ut ho w it l oo ks as lon g as it w orks. It is n't lik e Ap pl e is kn own f or att enti on to de tai l or go od desi g n. 😏
comment in response to
post
View (2/2)
.buttonStyle(.borderless)
.popover(isPresented: $showDatePop, attachmentAnchor: .point(.trailing),arrowEdge: .trailing) {
DatePicker("Date", selection: $selectedDate, displayedComponents: .date)
.datePickerStyle(.graphical)
.labelsHidden()
.padding()
}
}
comment in response to
post
Then a view (1 of 2):
@State private var showDatePop = false
@State private var selectedDate: Date = Date()
var body: some View {
Button(action: {
showDatePop.toggle()
}) {
Text(selectedDate.formatted(date: .numeric, time: .omitted))
Image(systemName: "calendar")
.imageScale(.large)
}
comment in response to
post
Here's how I did this for anyone interested:
First I created an extension for the NSDatePicker:
extension NSDatePicker {
open override var frame: CGRect {
didSet {
isBezeled = false
isBordered = false
drawsBackground = false
focusRingType = .none
}
}
}
comment in response to
post
Or at this point (well, when I get around to upgrading macOS and Xcode), maybe I'll just throw a screenshot of the iPadOS date picker at AI in Xcode and see if it can generate a fully functioning workaround that provides consistency for macOS.
comment in response to
post
Ugh, think I'm going to be sick 🤢, but thanks for the confirmation on that. Guess I'll be keeping my code around to make the presentation more tolerable on macOS 26 in my apps. So much for the Apple promise of consistency throughout the OS 26 platforms.
comment in response to
post
Paul, this is awesome. I know there is a lot of overlap but would it be possible at some point to get something similar for macOS-specific SwiftUI changes?
comment in response to
post
Please just tell me that the consistent updated design and behavior across OS 26 finally extends to removing the vomit-inducing macOS graphical date picker 🤢 (seriously - THIS in 2025?!?) in favor of the great iOS/iPadOS graphical date picker (presumably updated to look even better in liquid glass)
comment in response to
post
I'm digging around to see if I can find any tutorial or video that might focus on Core Data and sidebars and placeholders to see if I can figure out what I have so fundamentally messed up.
comment in response to
post
3. If I delete a section from my sidebar the content area doesn't realize there is no selection anymore in the sidebar and happily tries to act like there is (dangerous as now the selection is actually nil)
comment in response to
post
If only it were that simple. I've just plain messed up the sidebar in iPadOS. Three issues. 1. When I delete an item I show an alert, the item disappears, reappears and then the alert shows (Visually weird). 2. The selection visually disappears as I interact with the content/detail area…
comment in response to
post
In my apps I like to think of a lack of data to display as an opportunity to help guide users. Sidebar empty / no selection? Detail area can inform how to add to sidebar & encourage selection. No content within the selected sidebar item? Detail can inform how to add a record vs. an empty list. etc.
comment in response to
post
The check for the "should I display more tips or a list" is:
if filteredRecords.count > 0 { … } else { … }
and with a single view managing all 3 options that is nested in a check to see if there is a selectedSection.
comment in response to
post
I suppose I could split up the detail view that sort of manages this. Say - ok, if a section is not selected show the tips about that, but if there is a section selected - shoot it out to another view with non-optional section that will decide if it needs to display the further tips or a list view
comment in response to
post
Because there is a case where there is no section selected (in the sidebar) regarding the 3 possible detail views and the fetch request runs regardless of that, I set it up so I could make sure it was safe before force unwrapping it. Not sure if there is any other way around that.
comment in response to
post
The fetch request is dynamically getting any changes (added record, deleted record) and updating the detail area appropriately. The code works great, it just seems a bit bulky to me so I was thinking maybe there was a more concise way to write it to do what it is doing.
comment in response to
post
I guess I should explain better. There is a NavigationSplitView with a sidebar and detail area. If no selection in sidebar, then detail area displays tips to get started. If section is selected in sidebar, detail area displays more tips if no records, or list with records.