Here’s a quirky and not too serious problem for a Friday afternoon. I have a database that tracks Covid cases in our locality (Massachusetts), and reports them with an old and now deprecated color scheme. I have a form that uses an if else query to set the color based on the contents of a field called “Color”. containing just gray, green, yellow or red. The query in the formula box of the image display object is:
?(Color contains "Gray", "%%B0B0B0",?(Color contains "Green","%%40F040", ?(Color contains "Yellow","%%F0F040","%%F03030")))
Starting with the last version (10.2.0.b26 on Mojave), the color stopped displaying correctly in the view-as-list form I use to report. Interestingly, it prints fine (colors intact) and displays ok when I change the form to individual pages. In view-as-list, it only displays the first choice possible (gray here, but whatever color value I enter), as though it was evaluating the first choice as always true. Making the choice simple and non-nested doesn’t help. I removed all objects other than image display, and the behavior persists. “ifelse(” behaves just as “?(” does.
This doesn’t bother me, as I need the pdf ultimately, but someone might be startled to see this.
Other than this little quirk, I’ve been enjoying the new build. For whatever reason, it seems quite a bit faster, even on my system (2017 MBPro). Thanks for the huge effort to get here.