Ah … okay … Jim shows that the cause was discovered a year ago … and why this happens …
( Thanks @jim_foltz )
Basically more attention to details when dealing with pathstring separator in Windows file paths is required, and extreme care in the use of double-quoted strings for paths.
In the code I write I always convert "\" to "/" immediately with Window filepaths, so that I don’t get mistaken escaped characters, in this case the "\u" for a unicode character sequence. In the past I’ve often seen errors like this but with "\n" and "\r" (newline and carriage return respectively.)
I’m disturbed to realize it has been a year since it was discovered and it is not yet fixed ?
I guess I should not be surprised as I logged a really stupid bug, that is very easily fixed for Dynamic Components TWO TEARS AND 8 MONTHS AGO ! That was back in v 1.3.2, but it still has not been fixed. See:
Anyway, Jeff, I don’t think this has anything to do specifically with Windows 10, as it was also reported on Win 7.
But I am still wondering why the DC Options dialog would have a fit over the filepath ?
Neither the model filepath nor the DC filepath should have been passed to the dialog Javascript, as there are no DC functions that can do anything with these paths.
I attempted to reproduce on SU2016 (DC v 1.5.0) and SU2014 (DC v 1.3.2) and could not get the error dialog to appear.
But still I do not see the same error you see.
@jeffgerth You said, for example: “Slide Window (Dynamic Component)”
Did you mean ? this
This is wrapped in a worthless outer component that I had to explode to get the DC Options dialog to recognize that it was a DC.