Show newer

If you use a Repeater against a QAbstractItemModel and then remove data from the model, the delegate for that item automatically gets its index set to -1 and the item bindings get re-evaluated with that immediately before the delegate gets deleted. That's not the nicest design decision on the part of Repeater, but my code should have had the bounds check and there are workarounds for the other consequences.

Show thread

Today's code edits involved adding a bunch of tiny little functions to support new features and adding a bounds check to a function that I'm amazed I wrote without one. Stuff mostly worked on the first try with the exception of the feature that exposed the lack of a bounds check (which worked once I fixed that). I also cleaned up some superfluous conditionals and did some other minor organizational tweaks.

Employee: <thing> isn't working.
Me: *goes over to thing, looks at it, moves the power switch to the on position*

Anyway please look at this logo for an entomological conference in 1968

Went back to playing Gundemoniums and somehow I got better at it?

@debugninja@banana.dog Happened here too, but that's normal for this date around here.

@chillallmen@witches.live Pretty sure this was a scene in The Prince of Tennis.

Bottles arrived today, but no lids. Called back the place I get my bottles from and they're going to send lids. Fortunately, the three bottle sizes I buy all use the same lids so this isn't going to cause any production delays.

I've done enough test batches on the new sample roaster at this point that it's become clear that I want to adapt a program that I've been working on to do some of the work involved in designing roasting plans outside of their app and then get the data I need to efficiently copy in what I want.

I wasn't really looking for new features to add to that program, but I guess another use case that it covers at launch might be good for getting people to try it out.

@mwlucas I always felt like this adequately described the difference beginners and experts. We all make mistakes and achieve the same outcome; The difference is the tricks you've learned along the way. :flan_thumbs:

nerd shit; self-hosting source control 

@gcupc@glitch.social Another haven't used SourceHut but have found Gitea very easy both on the initial setup and to upgrade to new releases (upgrading is literally just replace one file). Not in docker in my case.

Depending on your feature needs (as in, if you don't need features) you could also just do straight up git without any web stuff around it, in which case your distro probably handles the updates with the rest of the system.

I have projects set up both ways.

Show older
Typica Social

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!