I've been using compactMapValues() to transform values in a dictionary, resulting in a new dictionary. But it turns out I need the key as well. After some searching I found the (cryptic) solution: Dictionary.reduce(into:).
This lets one build a new dictionary from an existing dictionary with full access to the source key/value pair.
Here's my reference:
https://medium.com/@mihirr_panchaal/swift-dictionary-reduce-into-5e59de99eeba
Anyone have any idea why Xcode 27.1 only allows me to target macOS 14 Sonoma, even though Apple's documentation says macOS 12 Monterey is supposedly the minimum? I'm using Swift 5 language mode at the moment.
Maybe the real question is should I support anything older than macOS 14 Sonoma?
Here's a couple of Swift constructs I'm pondering.
Taking the scenario of having (x, y, z) co-ordinates that need to be passed into a function (in a different struct declaration), does it make a difference to put the co-ordinates in a struct versus a tuple?
struct Coords {
let x: Int; let y: Int; let z: Int
}
func doSomething(coords: Coords) {
print("\(coords)")
}
let point = Coords(x: 1, y: 2, z: 0)
doSomething(coords: point)
versus:
func doSomething(coords: (x: Int, y: Int, z: Int)) {
print("\(coords)")
}
let point = (x: 1, y: 2, z: 0)
doSomething(coords: point)
I'm sure I saw this posted, but it's not showing up anywhere so I want to make sure it's included.
Tears For Fears – Change
The new Preview app icon really is jarring. It's like skeuomorphism but for something that's not real. And it really doesn't convey any meaning, let alone something like "preview". Aren't icons supposed to represent concrete ideas? Otherwise isn't it just a texture?
Here's a really good song that does mention gems, but not in the title.
"Take your baby by the wrist
And in her mouth, an amethyst
And in her eyes, two sapphires blue
And you need her and she needs you"
Wang Chung – Dance Hall Days
Update: Media lie, no helmet storage at bike lots. Still worth biking to the Fair.
Awesome, the Minnesota State Fair is improving the bicycle parking, better racks and now helmet storage. I've been carrying my helmet with me since I started biking to the Fair:
"Folks who bike to the Fair will find new bike racks and expanded capacities at each of the Fairgrounds’ three free bike lots...Secure helmet storage is also available..."
As I gingerly head into localization for my app, I have immediately discovered two things:
1) Based on web search, localization has been consumed by "AI" which is horrifying. I would never trust a slop machine to give the correct meaning (see point #2).
2) Even seemingly simple concepts like the "quit" (as in the app) menu item engenders a lot of nuance depending on the language.
So this is neat (not really). Apple created a SwiftUI view simply called "List". Fine, but I'm trying to figure out how to make a "list" that's limited to five rows tall regardless of how much data is in the list, and because of Apple's generic name it's impossible to do a web search for "swiftui list that's a fixed number of rows".
(Not to mention I'm working on macOS and running into 90+% iOS examples, but that's a known struggle.)
Update: added an example window that shows what I'm going for, taken from macOS Finder.
I've posted the first content update since I relaunched my site.
I think I spent too much time on this, and yet not enough.
I just discovered the Fediverse (English) Wikipedia page has a huge section on AT Protocol and I question why. It seems like excessive promotion of Bluesky and its protocol that is not compatible with ActivityPub, both technically and in spirit. Illustrating bridging isn't the same as compatibility. Might as well add sections for other random network protocols like XMPP (Jabber).
Let's get right to the core of this week's theme…
The Chemical Brothers – Go (feat. Q-Tip)
Songs that mention music, musicians or bands? Okay, this is the very first one that popped into my head.
This is an epic song, and I have always wondered if this is the origin of rock music "melting faces".
"Three thousand guitars, they seem to cry
My ears will melt, and then my eyes"
Blue Öyster Cult – Cities on Flame with Rock and Roll
SAPlugin v2.0 is now available.
SAPlugin is a macOS Authorization Plug-in implementation written in 100% Swift, and can be used for customizing the authorization process in macOS, including system login.
It may be a niche project, but I'm pleased with this release. It now uses Swift 6 and concurrency (hopefully correctly) and I managed to redesign it to create a true shim in a single Swift file, isolating all of the interfacing to the OS C functions.
Is it true there's no way to get an NSImage directly from a SwiftUI Image? Seems weird since Image can be created from NSImage.
Seems the solution is to load the asset as an NSImage and go from there.
For an open source project that's meant to be integrated with other projects, once it's been updated to Swift 6 with strict concurrency is there reason to maintain a Swift 5 version?
I'm using my own NSWindowController with a SwiftUI view as the root view of an NSWindow, and I'm trying to figure out how to use @Environment (or something else) to change a value in the NSWindowController and let the SwiftUI view act accordingly.
The window does work and displays properly, but I can't figure out how to change the state from within my NSWindowController update method.
If anyone has any tips I'd be appreciative.
This Gâteau Breton (Breton butter cake) came out pretty good and has nice flavor. I've never worked with zest before but it really does add a nice dimension.
I have notes about my effort:
– My springform pan was too big (22 cm instead of 20 cm).
– I had trouble with the layers, pushing the marmalade to the edges while applying the top layer. I probably didn't freeze it long enough before adding the top layer.
– Not sure why the outside edge burned, maybe the sugar in the marmalade that got pushed out to the edges burned.
– Cake seems dry to me, even though it tastes good. Did I overbake it (because it's so much thinner in the larger pan), or is it the recipe? The only moisture in the dough was butter and egg yolks.
– I now have five eggs worth of egg whites, need to use them up on something.
If one creates an UnsafeMutableRawPointer using allocate() and then calls deallocate(), isn't the pointer pointing to now-arbitrary memory?
How does one safely "forget" the pointer? Only thing I can think of is making the UnsafeMutableRawPointer property optional so it can be set to nil after the deallocate() call.
RE: https://ieji.de/@puppethead/116019436841444082
I think I've gotten around a "race condition" error in Swift 6 Concurrency by using bitPattern initializers to convert my OpaquePointer to a Sendable UInt, and then converting the UInt back to an OpaquePointer to use.
It seems clever but is it good? I'm basically subverting the constraints of the compiler through the trickery of stripping the pointer of its type identity.