OH, my bad. I didn't notice this is 5.0. Problem fixed in 5.1.
1 Like
I just put the fix back into the 5.0 code base... That will be in an upcoming release.
3 Likes
Thanks Bruce.