Notices by Adrian Cochrane (alcinnz@floss.social), page 59

So perhaps this is happening:

show_toast() is being called to show a toast, then very soon after hide_current_toast() is called to hide that same toast.

Occasionally, the hide_done_cb() callback is called *before* show_done_cb(), when usually it should only come after.

That makes me curious as to how glib iterates through the list of callbacks.

The bug appears when quickly creating and dismissing toasts.

By compiling a debug build of libadwaita, I get a better backtrace for where the "free" is:

g_signal_emit_valist -> hide_done_cb -> free_toast_info -> g_free

Trying to add a feature to Gnome Crosswords, which uses GTK4.

This experience is making me think that Tk was a well designed GUI toolkit after all...

Already I've found a use-after-free in the toast code, which is not a good look for libadwaita. But the real question is how long it takes for me to debug it.

The support for toasts does seem quite badly designed though... or maybe that's just the bug.

@lauren I'm happy to pay to pay for individual shows, but I want DRM-free downloads! If these "streaming services" don't want to give me that, I'll see what other options are out there.

So far I'm loving most of what I'm finding!

vastly underappreciated tech:
mustache templating
oEmbed
mime/multipart
maildir

oembed is neat

@lanodan Either that, or a screenful of customization toggles putting the UX design off onto the user!

UX is on my mind, since somehow it has become an argument I'm in.

Put a developer in charge of UX & you'll probably get something ugly.
Put a visual designer in charge of UX & you'll probably get something overly flashy.
Put the customer in charge of UX & you'd you won't get anything innovative. Unless they're in the other camps they don't know what's possible.
Put a businessman or marketter in charge & users will not get anything done.

We play our vital roles, but UX is it's own specialty.

@lightweight I suggest that what you're objecting is more mis-education rather than lack of education...

@lightweight I guess what I'm arguing here is for nuance regarding objecting to people for not using certain software because it's "not user friendly enough". I'd rather ask for better UIs to be developed then risk demeaning people a lack of interest in computing. For wanting to spend their time learning other things.

There are definitely things to critique here, but the topic can easily head into territory I strongly disagree with.

In Fallout 3 the Trains are actually a character wearing a train model as a hat. Engine didn't allow for vehicles, so this way they could reuse NPC movement code. #gamedev

@lightweight I will also add that good UI design doesn't *necessarily* involve more code. It involves empathy & attention to detail.

In fact excess code can suggest that you might be overcomplicating the UI!

@dn @lightweight Yup, UI is documentation! Documentation I find easier to write as an engineer, & documentation which is more likely to be paid attention to!

@lightweight There's a lot of nuance in UX, & I'm not entirely convinced that it's impossible to communicate these issues in a UI. And if we can do so, that helps people not forget.

However I will say that the more people are planning to use a power-tool the happier they'll be to spend time learning it.

@lightweight Yeah, I'd consider that a UI design failure. Albeit one which is easily weaponized by capitalists & get mistaken at the behest of marketters as good design!

@didek @jikodesu Nice!

@divVerent @lightweight And I'm using SourceHut Todo rather than SourceHut Lists for exactly this reason! I'm essentially using email as an authenticated comment box in an issue tracker, so contributors don't have to sign up for my codeforge.

@divVerent I can understand that certain projects have set a bad impression of email-based git. But listening to the objections I don't believe my system shares them, you are working on presumptions.

I even have shortterm & longterm solutions for those who don't want to interact with it via email!

@lightweight

@divVerent @lightweight I'm not even talking about git send-email (though it should work in my setup)!

I'll accept links to your fork elsewhere, or there's git format-patch!

@BeckyDouglas I once had such a cat-shaped shadow!