Sorry guys.
There are two options you can specify for UI tabs, I forget off the
top of my head what they are (there's an example of it's usage in the
docs for UI tabs). One is for a function to be run when a tab is
clicked, the other for after the tab is loaded. So all I had to do
was set the t
Leanan wrote:
Thanks for the assistance, guys. All is well now.
Can you let us know what the fix was so that another person with the
same issue might have an easier time?
-- Scott
Thanks for the assistance, guys. All is well now.
Michael Geary wrote:
It's funny, my guess is the opposite of Scott's. I'm also not familiar with
the flot code, but it sounds like something that may run *synchronously* and
therefore locks up the browser until it is completed. Any changes you make
to the DOM will not show up on the display unti
It's funny, my guess is the opposite of Scott's. I'm also not familiar with
the flot code, but it sounds like something that may run *synchronously* and
therefore locks up the browser until it is completed. Any changes you make
to the DOM will not show up on the display until this finishes.
If th
I hadn't thought about that... I'll look into it.
Leanan wrote:
Does anyone know how I can get the following to work and actually
display the results of the .text() calls inside the click() instead of
after the .click() has processed? Thanks in advance
I don't know anything about flot, but my guess is that it's processing
asynchronously, so
7 matches
Mail list logo
