I'll take a look! Assuming that source maps broke in an emitter, I can easily add more tests to help us avoid future regressions.
- Josh On 2019/02/06 19:33:26, 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 > http://about.me/carlosrovira >
