I hate to say this y.fujisawa your script is working exactly like its supposed to on my machine. Sorry its not on yours.
There are differences between 2014 and 2015. The new Mondo framework was introduced in 2015, and there are some issues with it. However, your script worked on my computer also.
Thank you for the replies!
Now I have 3 computers.
1.Windows8.1(CC2015 Japanse Edition in Japanese OS)
2.Windwos7(CC2015 English Edition in English OS)
3.Mac10.9(CC2015 Japanese Edition in Japanese OS)
I found the same issue on every three computers.
Is there something that is considered to be the cause of that?
Interesting. I got your result if I ran the script through Photoshop's script menu, but did not get it if I ran the script using the Extendscript Tool Kit. This was a bug that was suppose to have been fixed. I'll see if I can alert someone about this.
Thank you for your checking behavior of script.
I also run through IndesignCC2015, the result is the same as PhotoshopCC2015.
>This was a bug that was suppose to have been fixed.
I really hope to fix.
For sure, this issue is not fixed. I have a script that was doing the exact same thing. However, in my case it would always end with a delayed PS crash as well.
I had windows 1/2/3. Window 1 is the main dialog. Window 2 was another dialog that opens from window 1. Window 3 was a dialog launched from window 2. Window 2 should close when window 3 is launched from window 2 (works with CS3-CC2014 just fine). For CC2015, windows 2 and 3 will stay open until window 3 is closed. All would seem fine after windows 2 and 3 are closed until window 1 is eventually closed. When window 1 is eventually closed, PS then crashes.
The work around that I came up with was both windows 2 and 3 now launch directly from a different button on window 1. The user needs to close window 2 or 3 before they can access the other. Now everything works fine, although it is not the layout that I want.
I didn't submit the bug reports because I saw it was already submitted. If it doesn't get resolved then I'll submit a redundant ticket.
>The work around that I came up with was both windows 2 and 3 now launch directly from a different button on window 1. The user needs to close window 2 or 3 before they can access the other. Now everything works fine,
I see, I think that's the best way now we can do.