Neal Wilson ✅ @neal@social.typica.us

A couple people have asked if I'm going to a trade show in a couple weeks. I'm not (unless someone else wants to sponsor the trip) but I should probably start getting out to those again. It's a good opportunity to meet up with people using my software, let them know what I've been working on, find out what's working/not working for them.

Shipping label generation was failing on me when trying to ship today's orders. According to the error messages coming back, two fields that were previously optional are apparently now required. Double checking against the API docs, these are not labeled as required for USPS. So that's a little annoying. Thankfully, I can edit database records to put in the required information and update the server side code to make sure the data gets there for future orders, but it's late and I want to go home

Lots of orders to roast today.

Apparently I'll be on television next week. Need to set an alarm to wake up for that.

Presumably there's something within Qt causing the button to lose that visual indication which isn't getting undone, leading me to think it's a Qt bug, but for my program at least the workaround is tiny and not worth trying to figure out a patch. Problem observed on Linux/X11 in Qt 6.10.

The solution is to add a changeEvent override which calls update() on an ActivationChange event.

For that last problem, I have a set of buttons that I use to note changes in machine controls where I don't have a sensor to detect that automatically. The way I use this is I tab/backtab to the next control I intend to change in advance and then it's very easy for me to hit the spacebar with one hand while making the control change with the other so that's logged accurately enough. The problem comes if I temporarily switch to another window. This causes the button to lose visual distinction.

Spent a little more time on Typica before heading into the shop this morning. Removed 4 things from my list of desired changes. 3 were things that I knew would be easy once I had the code open in front of me. The 4th is arguably a bug in Qt and I wasn't sure what the right thing to do there was, but the easiest thing I could think of to try did resolve the issue.