I think core.swc is supposed to contain stuff you can use in AS3 projects
w/o pulling in all of the other Flex stuff. Maybe it can go there?
On 4/30/14 1:08 PM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:
>Alex,
>
>Too much time on it, the reason why it didn't stop in the worker is
>because the compiled worker didn't included the base worker class, better
>that than what I thought :P
>
>Also, it's going to work for Flex projects but not for pure AS3 projects
>if I put that base class in the existing libs, should we create an other
>lib that pure AS3 project could reference ? how do you see it could be
>better ?
>
>Is it a good solution for IDEs ?
>
>Frédéric THOMAS
>
>> From: webdoubl...@hotmail.com
>> To: dev@flex.apache.org
>> Subject: RE: [FDB] Integration
>> Date: Wed, 30 Apr 2014 20:17:29 +0100
>>
>> It is not even that, even if I stop in the main thread, switch to the
>>worker and try to stop it, it doesn't want, digging into....
>>
>> Frédéric THOMAS
>>
>> > From: webdoubl...@hotmail.com
>> > To: dev@flex.apache.org
>> > Subject: RE: [FDB] Integration
>> > Date: Wed, 30 Apr 2014 19:47:33 +0100
>> >
>> > What I did and 1st surprised I thought it was the "halt" command to
>>debug, not even, it was in the main loop and the trick is, I had to code
>>to stop only on the main thread, it doesn't work with the current
>>implementation, well, not so but at the end, given once it is halted we
>>can switch to another one, halt it and so on.
>> >
>> > So, at the IDE point of view, I'm scared that the users can only halt
>>in the main thread even using a base Worker and the fix I found, now I
>>wonder if we need to raise a bug in the FlashPlayer ?
>> > It doesn't answer to the requested message sent to a worker:
>>simpleRequestResponseMessageIsolate(DMessage.OutStopDebug,
>>DMessage.InBreakAtExt, every, isolateId);
>> >
>> > Frédéric THOMAS
>> >
>> > > From: aha...@adobe.com
>> > > To: dev@flex.apache.org
>> > > Subject: Re: [FDB] Integration
>> > > Date: Wed, 30 Apr 2014 17:02:01 +0000
>> > >
>> > > Looks right. Maybe capabilities.isDebugger isn't true or
>>setInterval
>> > > doesn't work?
>> > >
>> > > You've got a new debugger, step through it. ;-)
>> > >
>> > > -Alex
>> > >
>> > > On 4/30/14 9:58 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com>
>>wrote:
>> > >
>> > > >I created a base class that the workers extend but doesn't seem to
>>work,
>> > > >did I miss something ?
>> > > >
>> > > >/**
>> > > > * User: DoubleFx Date: 30/04/2014 Time: 17:34
>> > > > */
>> > > >package {
>> > > >import flash.display.Sprite;
>> > > >import flash.system.Capabilities;
>> > > >import flash.utils.setInterval;
>> > > >
>> > > >public class DebugWorker extends Sprite {
>> > > >
>> > > > public function DebugWorker() {
>> > > >
>> > > > // Stick a timer here so that we will execute script every
>>1.5s
>> > > > // no matter what.
>> > > > // This is strictly for the debugger to be able to halt.
>> > > > // Note: isDebugger is true only with a Debugger Player.
>> > > > if (Capabilities.isDebugger == true) {
>> > > > setInterval(debugTickler, 1500);
>> > > > }
>> > > > }
>> > > >
>> > > > /**
>> > > > * @private
>> > > > * This is here so we get the this pointer set to Application.
>> > > > */
>> > > > private function debugTickler():void {
>> > > > // We need some bytes of code in order to have a place to
>>break.
>> > > > var i:int = 0;
>> > > > }
>> > > >}
>> > > >}
>> > > >
>> > > >
>> > > >Frédéric THOMAS
>> > > >
>> > > >> From: aha...@adobe.com
>> > > >> To: dev@flex.apache.org
>> > > >> Subject: Re: [FDB] Integration
>> > > >> Date: Wed, 30 Apr 2014 16:18:04 +0000
>> > > >>
>> > > >>
>> > > >>
>> > > >> On 4/30/14 8:49 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com>
>>wrote:
>> > > >>
>> > > >> >Could be a solution, you meant like the idleTimer in
>>SystemManager ?
>> > > >> Actually, I was referring to debugTickler in Application.as
>>(both mx and
>> > > >> spark).
>> > > >>
>> > > >> -Alex
>> > > >>
>> > > >
>> > >
>> >
>>
>
