screenfloat

One of these days, I’d like to put some of the still-in-development ScreenFloat 2’s features through its paces (for instance, and most importantly, the migration of a ScreenFloat 1 library into the new format).

So I’m starting to put together a list of heavy-duty ScreenFloat users now, so that, once I’m ready, I can send out TestFlight invitations and get some feedback and insights right away.

If you consider yourself a heavy-duty ScreenFloat user, and/or have a large-ish library of shots and collections in ScreenFloat 1, please do reach out, I’d appreciate your help.

It’s still going to be a little while as I think about what I want to test exactly, and how, but I’ll be in touch nonetheless, you can be sure of that.

Thank you!

Read more

Our partners at Setapp have a deal we can’t let you miss!
For a limited time, you can get Setapp, 1Password and MasterClass at up to 40% off 🤯

Hurry to grab the tools you need in 2023 with this unmissable offer 👉 LINK

✅Setapp is a place to get 230+ apps for tasks on your Mac (yes, that includes our app 😊)
✅1Password is a password manager for safekeeping of all your passwords
✅MasterClass is a platform to watch video lessons by industry icons

Make 2023 your year with tools for true pros!
Terms apply

Read more

Just a quick note that since the betas (!) of macOS Ventura 13.0, configuration of 3rd-party widgets is broken, which, of course, means that Yoink’s widget’s configuration does currently not work, and I cannot do anything about it. Let’s hope Apple fixes it soon, macOS 13.0.1 didn’t bring any improvement in this regard.

Here’s a quick video of what I mean:

Again, in my testing, this not only was the case for Yoink’s widget, but a widespread issue over all sorts of 3rd-party widgets, although I do believe that dynamically app-supplied values work. It might only be static values that are affected by this.

At some point in iPadOS 16’s beta, this same bug occurred, but that was fixed before release. I guess the fix didn’t make it into macOS.
Maybe it’s time for another “Back to the Mac” event.

UPDATE (Dec 14th, 2022)

This is still an issue on macOS 13.1 (22C65). Quite embarrassing for Apple.

UPDATE (Jan 24th, 2023)

macOS 13.2 (22D49) seems to have finally fixed the issue – although it *did* take an initial

killall Notification\ Centre

to kickstart the widgets after adding and configuring them. But after that, it seems to work reliably.

Read more