A few months ago, my (free) web host outgrew their servers and moved to bigger and better servers, resulting in a few weeks of downtime. Everything seemed to be going fine until one of the new servers showed signs of hard-disk failure. Naturally, my site was on said server, so my site suffered another week of downtime. A week ago, my host was having trouble with cPanel and discovered an undocumented (and unchangeable) connection limit hidden within it. The cPanel team said they couldn’t fix it quickly, so my site was down for a few more days while my host reconfigured things to work around the problem.
Everything looks to be stable now, but I predict that in about a week, a series of tornadoes will strike the building housing the servers, and the following week, x10hosting headquarters will be attacked by a giant robotic space eel.
GlassCalc 1.28
On a more serious note, I’ve uploaded version 1.28 of GlassCalc which should fix the bottoms of letters getting cut off in the menu bar. I’ve also reorganized the settings window and added a couple features to help set up unit conversions. Last but not least, I’ve added support for something I’m calling “Scale Factors”. These are suffixes you stick on the end of numbers to multiply them by some number. If you define a scale factor of K = 1000, you can write 1K for 1000. These have a higher priority than other operators, so 1/1K would be 1/1000, not 1/1*1000.
There are no scale factors defined by default, but you can define your own by editing your extensions.ini file (open More Settings->Extensions). Add a [ScaleFactors] section and add one suffix per line under it. The format is Suffix = Scale where Suffix is a string and Scale is a number. Put a /i at the end of a suffix to make it case-insensitive. You can also use exponential notation when setting the scale. Here is an example ScaleFactors section which defines m (milli), c (centi), K (kilo), and M (mega) suffixes:
[ScaleFactors] m = 1e-3 c = 1e-2 K/i = 1e3 M = 1e6
Suffixes do not have to be a single character. They can be of any length. You can also use regular expression syntax, but I don’t recommend it. Using square brackets or equals will probably confuse the ini parser, starting with digits (and various other patterns) will confuse the math parser, and everything after the first forward slash is treated as modifier flags. If anyone wants more in-depth support for regular expressions here, ask and I’ll find a way to make it work.