This content has been marked as final. Show 4 replies
Do you have any code in there to prevent it from shutting down? Like
or something similar? If so, then you are specifically telling it not
to allow the X to shutdown the app.
This setting can also be set in the Publish Settings dialog, on the
Nothing explicitly blocking it from quitting, and nothing telling it not to block. I believe the exit-lock is set to false by default.
I added a keyPressed handler to watch for the "q" key to call the _player.quit() event. That works fine. I've never had this problem in the past. Could be something with any one of the hundreds of Windows security patches... Usually, using the CNTL-Q or CNTL-. will quit the projector player.
Does it happen only on this one particular file? Or does the same thing
happen if you create a brand new .dir file and publish it? There may be
something corrupted in the file. I seriously doubt it is a windows
update that caused this issue. I have all the most recent updates and
have never seen this problem. Unless the exitlock is turned on of course.
You can check in authoring mode by entering this in the message window:
put the exitLock
See if it is turned on... and if so, then find out where it is and turn
it off. If it is not on, then it is likely that your dir file has
become corrupted somehow.
Good call trying a new file. Quitting the player worked correctly.
Thanks for the reply.