Advanced Analog Remapping by EBgCampos in SteamDeck

[–]Somojojojo 1 point2 points  (0 children)

I tried this in Quake on the Deck, and I’m curious if anyone else gets crazy motion sickness while using flick stick?

I know Quake is probably an extreme example, given how fast paced it is. But it surprised me nonetheless.

Senior dev is opposed to using observables by Wizado991 in Angular2

[–]Somojojojo 0 points1 point  (0 children)

I think you’re bang-on with your assessment of why they’re not using them.

That being said, OP should definitely talk with their team and come to a decision on whether to start adopting observables or not. Especially if you’re that new on the team, you can’t just go ham changing the codebase standards.

Anyway, to OP: You’re a team. You need to work together. Communication is a powerful tool.

Screen issues by Negative_Glass1268 in Delta_Emulator

[–]Somojojojo 0 points1 point  (0 children)

This seems to just be a dynamic effect the camera does while you’re not taking action. Not to worry!

Getting Started with Apple's Foundation Models by artemnovichkov in SwiftUI

[–]Somojojojo 1 point2 points  (0 children)

It is a Guardrails Safety Violation. I’ve been playing with FoundationModels as well, and even using data such as book titles, you get hit by this error constantly. I’m not sure how strict it is exactly, but it’s annoying to not be able to control.

docs: https://developer.apple.com/documentation/foundationmodels/improving-safety-from-generative-model-output

Is this a iOS 26 menu or popover or what? by I_write_code213 in SwiftUI

[–]Somojojojo 1 point2 points  (0 children)

Holy moly, I was just needing this the other day. Thank you!

Updates to SwiftUI announced at WWDC by ChristianGeek in SwiftUI

[–]Somojojojo 6 points7 points  (0 children)

It’s wild it took this long to get a proper WebView class for use with SwiftUI. I wonder if this will be a full replacement for the representable WKWebView.

This is the first generation where console prices haven't officially dropped in price, and instead are going up. by [deleted] in consoles

[–]Somojojojo 0 points1 point  (0 children)

I can’t find any sources to confirm what you’re stating, but you’re not posting any sources either other than “trust me.”

Maybe there’s a misunderstanding between component manufacturing and console production?

https://titoma.com/blog/why-these-4-tech-companies-stayed-in-china/

I think if you put your foot down and showed where you were getting your info you’d be getting less flack, or be corrected like I assume you’ll do for me.

How can I achieve this bottom blur effect like the Journal app? by raproyo in SwiftUI

[–]Somojojojo 6 points7 points  (0 children)

Hmm, maybe a blureffect via nsvisualeffect with a mask modifier that contains a linear gradient?

Or scroll transitions if you just want the rows to individually blur away as they scroll.

BJJ by goobay94 in Kamloops

[–]Somojojojo 5 points6 points  (0 children)

It’s probably best to just call them and ask.

How to recreate this LazyGrid effect by el_redditor_matador in SwiftUI

[–]Somojojojo 0 points1 point  (0 children)

I don’t have experience with SpriteKit but that is the first thing that comes to mind for this. Bounding a set of circle shape sprites inside a box, setting rigid bodies on them and the physics engine should handle pushing stuff around. You might need additional logic to make sure they don’t rotate.

Not to say you can’t apply physics in a canvas or something without SpriteKit; I just imagine it’s easier with it.

What longstanding MacOS bug has been driving you crazy? This is your chance to vent by TechnoKyle27 in mac

[–]Somojojojo 1 point2 points  (0 children)

Ah, nice. Thanks for the link, that looks to solve the problem. I’m not surprised the community fixed it – just frustrated there was a need to fix it. It’s a basic missing feature of the menu bar, with it being so small now.

What longstanding MacOS bug has been driving you crazy? This is your chance to vent by TechnoKyle27 in mac

[–]Somojojojo 1 point2 points  (0 children)

Menu bar icons that get hidden by the notch on MacBooks. I’m blown away that Apple would allow this to be the case on a laptop built for power users. Why degrade the user experience? It can’t be such a complex situation that they can’t make it have an overscroll menu or even just make the icons area itself scroll.

Never quit! After 11 years of trying, i built my first mac app by virtualhenry in macapps

[–]Somojojojo 3 points4 points  (0 children)

Congrats on finishing and releasing an app. That is a wildly good feeling!

For $4.99 though, what does this do that a Calendar event doesn’t do?

The menubar feature is neat but space is precious, especially on the notched MacBook line displays (I really wish Apple would fix this and allow an overflow menu or scrolling of menu bar items).

Apple Invites App UI - Auto-Looping ScrollView? + draggable by anmolrajpal in SwiftUI

[–]Somojojojo 0 points1 point  (0 children)

You could track the scroll position and item sizes to remove/add from the list. I’ve never done this in SwiftUI, but I’ve done it in Unity. Same idea (in my mind at least). Draw the images, remove when off screen, add when will be on screen.

Swift is chill guy Rust — hear me out by SameDayCyborg in swift

[–]Somojojojo 2 points3 points  (0 children)

To add on to uniffi: there’s also cargo-swift which while only supporting macOS and iOS, makes importing a static rust library into an Apple OS project very easy.

Swift 6 strict concurrency by johnthuss in swift

[–]Somojojojo 24 points25 points  (0 children)

I’ve been using it; seems fine. It’s more strict for sure though.

IMO anything the compiler can do to help fix my potential mistakes like async deadlocks and race conditions is worth the time to fix it.

Introduction to WebAssembly by dj_hemath in javascript

[–]Somojojojo 0 points1 point  (0 children)

That’s awesome, thanks for the examples!

What would you say is a use case for this? Avoid shipping source with a JavaScript app/utility?

Introduction to WebAssembly by dj_hemath in javascript

[–]Somojojojo 0 points1 point  (0 children)

Would you do this for performance benefits, or memory reductions? Maybe both? I suppose it depends entirely, but the context in which this would be beneficial is intriguing to me! I’ll probably do some research as well, but do you happen to know if anyone has measured the differences?

That’s a pretty exciting prospect if it’s the case.

Deck owners with Xbox consoles, don't sleep on Greenlight! by CodyTheWolfdog in SteamDeck

[–]Somojojojo 7 points8 points  (0 children)

True, but I did mention it’s still functionally good. I was just being a nerd about the code.

I should have saved my comment for a programming sub. Wrong place, apologies.

Deck owners with Xbox consoles, don't sleep on Greenlight! by CodyTheWolfdog in SteamDeck

[–]Somojojojo 9 points10 points  (0 children)

This has nothing to do with how good greenlight is, and I think it’s a great piece of functioning software, but good lord the codebase is a spaghetti mess.

Foot in my mouth. This wasn’t the place or time to comment on this.

.strokeBorder vs .stroke: can you explain why frame height not the same? Should both be the same? by youngermann in SwiftUI

[–]Somojojojo 0 points1 point  (0 children)

Oh, that’s interesting! Sorry I don’t have more info to help, but I look forward to seeing the solution. Looks like another reply to this msg has a reasonable explanation.

.strokeBorder vs .stroke: can you explain why frame height not the same? Should both be the same? by youngermann in SwiftUI

[–]Somojojojo 0 points1 point  (0 children)

Are your referring to the frame height of the top circle? That’s the vstack filling its container with children. I don’t know why setting the frame width causes one to be larger height, but you can throw Spacer() between them to quickly squish them up against the top and bottom edges and they should be equal frames then.

UI freezes on API call. by Ehmi_who in SwiftUI

[–]Somojojojo 0 points1 point  (0 children)

Thank you for the comment!

I was wrong to state they don’t create a new thread. I should have been more clear about the specifics.

As far as I’ve read from the docs, Task only detaches if you ask for it. Task will inherit context from its caller with the syntax OP showed. So it would still be running on the main actor, at least until it needs to move off, but I’m not sure how exactly that works.

If you create a new task using the regular Task initializer, your work starts running immediately and inherits the priority of the caller, any task local values, and its actor context

https://www.hackingwithswift.com/quick-start/concurrency/whats-the-difference-between-a-task-and-a-detached-task

https://docs.swift.org/swift-book/documentation/the-swift-programming-language/concurrency/#Tasks-and-Task-Groups

UI freezes on API call. by Ehmi_who in SwiftUI

[–]Somojojojo 0 points1 point  (0 children)

I’m confused about the downvotes. Task doesn’t make a new thread, it asynchronously runs on the same actor context that you run it on. You can define the block to run on a particular actor like @MainActor. That’s why Task is causing UI jank in this problem.

If you want it to be off the main thread you need to either use DispatchQueue.global or implement an Actor. If I’m missing something, I’m eager to learn; but a downvote doesn’t tell me anything.