I stand corrected... fix is in v3.6, issue originally based on a v3.5 user. Apologies...
The user likes what he has at v3.5, will wait for v4 Public Release before upgrading (why? I have no idea
).
The user likes what he has at v3.5, will wait for v4 Public Release before upgrading (why? I have no idea
).
