On Nov 7, 1:47 am, woomla <[EMAIL PROTECTED]> wrote:
> On Nov 7, 12:14 am, John J Barton <[EMAIL PROTECTED]> wrote:
>
> > But most important, I have green executable lines and can set
> > breakpoints where you can't. So let's figure that part out first.
>
> Updated to rev 1320
> Started from the command line
> Selecting scope panel.html
> Selecting script firebug.js from a very very very very long list (it
> looks like all events/seg/000 to 999 are listed)
I guess you have something else loaded in your FF that generates a lot
of events.
Did you know you can filter the list just by typing a character or
two?
> And voila, there the green executable lines are :-)
>
> This will speed things up a lot.
> And the first thing I've noticed is this (because it also effects
> chromebug)
>
> As soon as you click on the button (bottom right) to open firebug,
> buildViewAround is called *but the window is not open yet*.
? How can you click on the bottom right of a window that is not open?
> viewableLines is undefined, so setViewableLines is called.
> Because the window is not open, this.panelNode.clientHeight == 0.
> Therefore, viewableLines will be 0 and only the first line in the
> scripts tabs is visible.
I've been working on this problem a lot, obviously not successful yet.
The basic problem is:
1) I can't know the size of the lines until I have a line to
measure.
2) I don't have a line to measure until I render the lines
3) I can't render the lines until I know the size of the lines.
4) See #1.
So I'd like to figure out how buildViewAround is getting called.
>
> The next time the firebug window is opened, sourceBox.viewableLines is
> set to the correct value for that panels size.
>
> If you enlarge the script panel and scroll, viewableLines is already
> set and not updated so the viewport remains the same height although
> it is displayed in a larger part of the screen (or smaller), leaving
> whitespace above and below.
Thanks I'll check the resize.
>
> So my quick solution for now is to always call setViewableLines. Then
> when I scroll the window, the viewport is adjusted to the correct
> size.
I'm trying to avoid any "always call" if I can avoid it, the viewport
code needs to be as snappy as possible.
>
> (During my research, I've noticed that sometimes the panel.html scope
> is not available making me need to restart several times before it is.
Restart chromebug? I've not seen this.
> Also you need to start from the commandline otherwise there will be no
> executable lines marked in the script tab)
Right, that's why I asked if that is how you started.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
