Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In this case it’s Chrome. I’ve had a look at Chrome’s command line switches and the one I’d need Flash Builder/eclipse to fire is –new-window. Makes sense of course.
So I go into Flash builder, go to the browser preferences and set the parameters for the Chrome bin app, like so:
So that, to me seems right, but it doesn’t do what it says on the tin. So what am I doing wrong and how can I get it to launch in a new window?
On MacOS X, Chrome only starts once. So, with your startup options, you get this error:
The origin of this error is explained here.
A solution is to use a different data dir for your debugging sessions:
For example in your home directory (something like /Users/username/chrome-debug-datadir). That solved the problem here.
You need to configure Chrome once in the new data dir. It also gives a clean separation between developing / debugging sessions and regular Chrome sessions.