.org
> Subject: Re: Chrome for debugging
>
> |Since a recent update you won't be able to see your npapi plugin in
> chrome://plugins unless you navigate to the following
>
> chrome://flags/#enable-npapi
>
> This workaround will not be available starting November 2015.
date.
The following article explains it.
https://www.chromium.org/developers/npapi-deprecation
--
View this message in context:
http://apache-flex-users.246.n4.nabble.com/Chrome-for-debugging-tp10001p10138.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
it doesn't allow you either to pass arguments,
> that's why.
>
> Frédéric THOMAS
>
> > Date: Tue, 7 Apr 2015 08:55:46 -0500
> > Subject: Re: Re : Re: Chrome for debugging
> > From: markzolo...@gmail.com
> > To: users@flex.apache.org
> >
> > Sh
I guess FB doesn't allow you to choose which chrome you want to use and stick
on the default one, it doesn't allow you either to pass arguments, that's why.
Frédéric THOMAS
> Date: Tue, 7 Apr 2015 08:55:46 -0500
> Subject: Re: Re : Re: Chrome for debugging
> From: ma
>
> > Date: Tue, 7 Apr 2015 08:09:32 -0500
> > Subject: Re: Re : Re: Chrome for debugging
> > From: markzolo...@gmail.com
> > To: users@flex.apache.org
> >
> > Thanks for the info. Can you please explain what would
> profile-directory="Dev"
>
THOMAS
> Date: Tue, 7 Apr 2015 08:09:32 -0500
> Subject: Re: Re : Re: Chrome for debugging
> From: markzolo...@gmail.com
> To: users@flex.apache.org
>
> Thanks for the info. Can you please explain what would profile-directory="Dev"
> do?
>
>
> On Tue,
ot;
> --disable-hang-monitor
>
> And for Linux:
>
> google-chrome --profile-directory="Dev" --disable-hang-monitor
>
> HTH,
> Frédéric THOMAS
>
> > Date: Mon, 6 Apr 2015 06:15:38 -0500
> > Subject: Re: Re : Re: Chrome for debugging
> > From: mar
:
open -a "Google Chrome" --args --profile-directory="Dev" --disable-hang-monitor
And for Linux:
google-chrome --profile-directory="Dev" --disable-hang-monitor
HTH,
Frédéric THOMAS
> Date: Mon, 6 Apr 2015 06:15:38 -0500
> Subject: Re: Re : Re: Chrome for debugg
And I unprotected my tweets.
--- Message initial ---
De : "Frédéric THOMAS"
Envoyé : 6 avril 2015 13:33
A : users@flex.apache.org
Objet : Re : Re: Re : Re: Chrome for debugging
Im not in front of my computer but feel free to share, I added you.
--- Message initial ---
De : &quo
Im not in front of my computer but feel free to share, I added you.
--- Message initial ---
De : "Paul Hastings"
Envoyé : 6 avril 2015 13:30
A : users@flex.apache.org
Objet : Re: Re : Re: Chrome for debugging
Unfortunately your tweets are protected. Can you copy/paste to the list?
Unfortunately your tweets are protected. Can you copy/paste to the list?
> A : users@flex.apache.org
> Objet : Re: Chrome for debugging
>
> Don't think you can turn it off in chrome. In Firefox you can turn the time
> out off.
>
> I tend to use FF for dev (debug player) and keep chrome with the pepper
> player for normal use
> On 5 Apr 2015
Try this guys https://twitter.com/webDoubleFx/status/584413022350876672?s=09
HTH,
Fred.
--- Message initial ---
De : "Mark Line"
Envoyé : 5 avril 2015 17:32
A : users@flex.apache.org
Objet : Re: Chrome for debugging
Don't think you can turn it off in chrome. In Firefox you ca
On 4/5/2015 11:31 PM, Mark Line wrote:
I tend to use FF for dev (debug player) and keep chrome with the pepper
player for normal use
i've had to do that as well. the latest versions of the pepper debugger hang
constantly at breakpoints & after loading a module. its kind of a heart breaker.
Don't think you can turn it off in chrome. In Firefox you can turn the time
out off.
I tend to use FF for dev (debug player) and keep chrome with the pepper
player for normal use
On 5 Apr 2015 11:46 am, "mark goldin" wrote:
> Exactly what I did. Everything is working fine except when I am in
> d
Exactly what I did. Everything is working fine except when I am in
debugging mode sitting on a break point I am getting a message from Chrome
that plug-in is unresponsive and if I want to continue waiting. Is there
something can be done about it?
Thanks
On Sat, Apr 4, 2015 at 1:53 PM, Evyatar Ben
Download the Firefox NPAPI debugger version and use that instead of the
PPAPI versions.
Good luck,
Evyatar
בתאריך 3 באפר 2015 19:29, "mark goldin" כתב:
> I am trying to follow Adobe instructions how configure Chrome for Flash
> debugging but it is still not working for me. I have downloaded the
I am trying to follow Adobe instructions how configure Chrome for Flash
debugging but it is still not working for me. I have downloaded the
debugging version ver. 17 for Oepra and Chromium applications). Then
disabled the stock one and enabled the debugging version. Still no luck.
Any idea?
Thanks
18 matches
Mail list logo
