When you have a root canal coming and that's the good news, and also less expensive than the bad news, you know it's been a crappy week.
But development continues. This week I put out build 512.1464 to address a number of fixes that were queued up and ready to go, plus some more recent fixes I had gotten to. As expected there were still a couple of hiccups left in the icon editor.
For 513, I got further with Unicode stuff but also veered away from it a bit to work on some other features on the list. First off, tan() and atan() have been requested for some time, so I'm putting them in. atan() will also have a two-parameter format that works like atan2() in most languages, and will therefore supplant my own soft-code version.
Another feature I'm working on is getting the dimensions of maptext. The new measuretext() proc (I considered client.MeasureText() but this works better as a built-in call rather than an object proc, for numerous reasons) will allow you to get the width or height required for maptext, by providing a client and a string of text that will be applied to their map style, as well as an optional max width. Currently it's setup to return a string in the form of "[width]x[height]" like you'd get from winget(), but I'm actually wondering if it'd be better to return a number: width if you didn't specify width (or it was 0 or negative), or height if you did. It would be easier to work with a number, but then it's a matter of adding some logic to tell the difference.
Querying sound status on the client is also in my early to-do list for this build. People have wanted it forever, so why not do it now?
As you can see it's short and sweet this week. Big thanks again to our Members, donors, and Patrons who keep the lights on. It's all the more appreciated with a car payment now staring me and my wife in the face. (Yup, that's the kind of week it's been.)
Feb 15 2019, 10:37 am