ir73 / flash-tracer

Automatically exported from code.google.com/p/flash-tracer
0 stars 0 forks source link

check for debug player window #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Double-click jar file
2. application opens
3. window asking if I want to check for the debug player opens

What is the expected output? What do you see instead?
At the moment every time I open Vizzy it also opens the window to ask if I want 
to check for the debug player. I would it expect that it would remember my 
response after the first time selecting yes or no rather than pop up every time 
I open Vizzy.

What version of the product are you using? On what operating system?

Version 2.2 on Mac OS 10.6.4
Please provide any additional information below.

Original issue reported on code.google.com by derek.ni...@gmail.com on 28 Sep 2010 at 6:40

GoogleCodeExporter commented 9 years ago
This question should be asked only once when you run Vizzy for the first time. 
You response is saved in tracer.properties file in the same folder where 
vizzy.jar is located. Please check, that the file exists there. 

Maybe you delete that file after you exit Vizzy?

Original comment by sergei.l...@gmail.com on 28 Sep 2010 at 7:02

GoogleCodeExporter commented 9 years ago
So I set Finder to show invisible files and I don't see the tracer.properties 
file. It does not appear to be getting created.

Original comment by derek.ni...@gmail.com on 29 Sep 2010 at 6:21

GoogleCodeExporter commented 9 years ago
What's the Vizzy path on your hard drive? Did you extract it from .zip archive 
or you run it directly from zip?

Original comment by sergei.l...@gmail.com on 29 Sep 2010 at 6:43

GoogleCodeExporter commented 9 years ago
Also, do you quit Vizzy like a usual application (by pressing red round button 
in top left corner) or shutdown it by some other way?

Original comment by sergei.l...@gmail.com on 29 Sep 2010 at 6:45

GoogleCodeExporter commented 9 years ago
Ah, interesting. I was using the keyboard shortcut Command-Q to close the 
application. Once I used the method you asked about (closing via the red close 
button in the window chrome) it created the tracer.properties and the issue has 
been resolved. So the issue appears to be when using the keyboard shortcut.

Original comment by derek.ni...@gmail.com on 29 Sep 2010 at 8:54

GoogleCodeExporter commented 9 years ago
I will try to handle Command-Q in next release.

Original comment by sergei.l...@gmail.com on 30 Sep 2010 at 6:06

GoogleCodeExporter commented 9 years ago
Command+Q is handled in 3.0

Original comment by sergei.l...@gmail.com on 30 Nov 2010 at 12:50