Well the application is pretty complex. It consists of a loader application (Causes no trace output besides the normal "loading ..." traces) After logging in a whole set of modules are loaded. Some of these again load further modules. To me it looks as if for every module while initializing two of these "[trace] null" are output.
I guess that the trace is called by the Flexicious Ultimate Data Grid (The only component used in all of these modules) ... I had a look at the source (gladly purchased that with the component). There are one or two places where trace is called. I just wanted to avoid doing a custom build with debug-information just to check if it's one of these modules (Unfortunately IntelliJ doesn't seem to like the "include "../../SomeOtherCode.as" concept which is used quite a lot in the Flexicious code). That's why I was hoping to be able to track down the call somehow first and to fix whatever code is causing it. Currently it's just annoying in the debugger ... I guess no customer will ever notice this, but I just wanted to have my console clean ;-) Chris -----Ursprüngliche Nachricht----- Von: haseeb ahmed [mailto:[email protected]] Gesendet: Mittwoch, 23. Januar 2013 10:47 An: [email protected] Betreff: Re: tracking down where "[trace] null" statements are comming from? is it application startup or loadingcomplete or some mouseevent.... i think, another way is, simply insert breakpoint on first line, then keep pressing step in , step over carefully... lala On Wed, Jan 23, 2013 at 1:30 PM, [email protected] < [email protected]> wrote: > Well the problem is that no event is thrown ... it's a simple call to > "trace" that probably a third party library is doing and I don't have > an Idea how to track this down :-( > > Chris > > -----Ursprüngliche Nachricht----- > Von: haseeb ahmed [mailto:[email protected]] > Gesendet: Mittwoch, 23. Januar 2013 09:23 > An: [email protected] > Betreff: Re: tracking down where "[trace] null" statements are comming > from? > > in such situations, i try breakdown like this try to get event first, > which is fired. > then search for event listeners (handlers) in different views. > once you know event name string, you can search via right click and > who is referencing to this event. > > interested in hearing other pov > regards,lala > > > On Wed, Jan 23, 2013 at 1:13 PM, [email protected] < > [email protected]> wrote: > > > unction ... perhaps it would > > > > > > -- > regards, > lala > -- regards, lala
