Hello all,
My first time posting here; I'm just starting to learn about TweenLite.js, and am fairly inexperienced with javascript in general. With that said...
I have a system that I am trying to debug the function of a button on. The system is a video + audio player in a web browser. There's a large-ish video pane at the top, underneath that is a scrubber/progress bar showing position in the video. To the left of the scrubber bar is a transport button (bar-left-arrow). This transport button is supposed to reset the position of the scrubber (and the video being shown as well) to the start. But sometimes this button doesn't work; I can repeatably make it stop and start working, so I'm trying to debug the scripts to see what is (or isn't) being set in a couple of states.
So, with the video paused and nothing going on (i.e. movie is not playing), I hit the 'Pause Script...' button in the Safari debugger; my intention is to then press the transport button and see what code it's running. But I can't...as soon as I hit the 'Pause' button it always stops at a function in the TweenLite.min.js file (line 137 as reported by Safari after it pretty-prints it. I think I have the hierarchy of the functions here correct...I took out snippets so might have missed something. The "function(t)" is the first function in the file, immediately following the header.
(function(t) {
"use strict";
var e = t.GreenSockGlobals || t;
if (!e.TweenLite) {
...
d("Ticker", function(t, e) {
var i,
s,
r,
o,
l,
h = this,
_ = A(),
m = e !== !1 && b,
f = function(t) {
S = A(), h.time = (S - _) / 1e3;
var e,
n = h.time - l;
(!i || n > 0 || t === !0) && (h.frame++, l += n + (n >= o ? .004 : o - n), e = !0), t !== !0 && (r = s(f)), e && h.dispatchEvent("tick")
};
So it appears to be some timer or listener code that is constantly running. But it prevents me from activating the button I'm interested in while in debug mode. Even if I press the button with the code stopped, it doesn't get added to the call stack, so I can't step into it.
I did some digging in the HTML to try and figure out what the element was; I think I did, but when I put break points on the code that appeared to be tied to that element, it never broke. So I must have tagged the wrong code.
Does anyone have some pointers to assist me?
Thanks,
Justin