Considering the 255 bug was reported almost 2 years ago, and I’ve reported it also, I’m pleased to read it’s finally been replicated and a fix will be coming. True, it’s not all that a big deal of a bug, but I’m very curious how a bug from the 1.x software can find its way into the 3.x software, particularly when 3.x was supposed to be a completely new code write from somebody who had nothing to do with the first attempt.
2 Likes