If people would use the debugger's formatted output capabilities, they might
not get so faked out. The culprit are these lines in eventtester:
if ($debug) {
if (this.verbose) {
Debug.debug(this.label, d);
}
}
this.setAttribute('value', d);
this.txt.setAttribute('text', this.label + ': '+ d);
This last line is converting the event target to a string and jamming it into
the txt field. Guess what happens when the event target is the debugger's
output <text> pane?
I suggest changing them to:
if ($debug) {
if (this.verbose) {
Debug.debug("%s: %0.32w", this.label, d);
}
}
this.setAttribute('value', d);
this.txt.format("%s: %0.32w", this.label, d);
Which will print a nice, pretty, abbreviated description of the event target
(and make it inspectable, if you really need to know more).
Sorry for not responding to Daniel earlier, I'm all tied up with this "shadow"
bug.
On 2011-04-08, at 08:38, Henry Minsky wrote:
> I am seeing a bug I don't recall ever seeing before, in the test case
> http://localhost:8080/trunk2/test/lfc/legals/keyboardandmouse.lzx
>
>
> When running in debug mode in swf10, you will see a debug info message
> printed for every mouseover
> event. If you roll the mouse over the debugger a few times, the second
> column view labeled 'global mouse events'
> suddenly grows very high, and inside of it you will see a copy of the
> debugger's content pane!
>
> Does this happen for you? What could be going on?
>
>
> --
> Henry Minsky
> Software Architect
> [email protected]
> <screenshot_01.png>
