It was fixed last year in version 2017.11.09. Are you sure you are encountering the *same* issue as described in this posting? I just tested 2018.10.4.13.0 and it works properly, so I suspect if you are encountering an issue, it’s not the issue that is described in this posting. Please be as descriptive as possible when explaining the issue that you are encountering.