Are you debugging js-debug or js-release?
On 2/6/19, 11:33 AM, "Carlos Rovira" <[email protected]> wrote:
Hi
I have an issue with yesterday changes that are causing some regressions in
debugger, but don't know what could be the problem.
Taking tour de Jewel :
I put a break point in ButtonPlayGround.mxml line 29:
private function clickHandler(event:MouseEvent):void {
button.emphasis = (button.emphasis == Button.PRIMARY) ? "" : Button.PRIMARY;
<-- break point here
}
(very simple right? ;))
but...break point appears when Tour de Jewel is launched and stops in
ButtonPlayGround.js... that's no right ok?
This is a regression, since that was not happening before.
I assume that is caused for changes in compiler, but can ensure what
changes and when happened.
I'd like to ask for some caution when doing changes in compiler, since we
had a debugger working in a decent % of cases, maybe 90-95% of the code I
test was working. I invested money to make it work for all, to use in my
project and to help the community. But seems some changes are making
debugger be working less and less each time. I see the same problem in some
parts of my own code that before was not happening. I was thinking in
invest more money in other things in Royale, but is hard to me to explain
in my team this when things where we invested about 1-2 months ago seems to
be now breaking.
We all now Apache Royale is evolving each day, but I think changing
compiler should be do with changing debugger rules to avoid more breaks of
things that was already working.
So please, take into account that changes done should be done with
debugging capabilities in mind, or we'll always breaking debugger.
Hope this make sense to all of you
Thanks in advance
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C507054f63ae442d790f208d68c6a0092%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850784263050163&sdata=fNThclAdG0YrfOmXkq%2FuzFhCi8yKaHypf24RFEAi8DU%3D&reserved=0
