Hi, we’re a lot to warn that this issue isn’t fixed at all contrary to what is stated in the report. And for two months we’ve been voicing our concern about that in the comments. No answer.
Anything planned on re-opening the issue?
Thanks.
If you haven’t made the origin issue report, I’d guess the most effective way would be to create a new bug report and make sure you reference the closed issue on the issue description.
Thank you for bringing this to our attention. The issue has been fixed in a local repository but hasn’t made it into 2018.3 yet. It was wrongly marked as fixed for 2018.3. Sorry for the confusion. Unfortunately I can’t give you an ETA at this point, but it will be fixed.
1 Like