You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found your jsfiddle sample where you retrieve the current frame via .data("frame").
I tried the same with .data("row") but it returns decimal values between 0 and 1.
when I follow the github link to this issue
(#50), I see a completely different
post than this one. So here's the answer to the e-mail question
directly:
The "row" data is a bit different from the way values of "frame" work.
It is much more similar to "fraction" data value. Both "row" and
"fraction" have values ranging from 0.00 to 1.00 and in order to get
the actual value like frame, you need to multiply it with the total
number of frames, round the result and you get "frame". "frame" is
stored in the data, but not the "row frame", which you will need to
calculate by multiplying it with number of rows.
Hi pisi,
I found a bug in the frame calculation in jQuery Reel v1.1.3
In this jsfiddle example I set the options
{ frames: 20, frame: 15 }
.Yet when initialized it shows frame 14.
When you look at the console log you'll see that at first the correct frame is used,
and right after that it jumps to the incorrect frame.
This is happening with several frame values:
frame: 4
jumps to frame 3frame: 7
jumps to frame 6frame: 8
jumps to frame 7frame: 13
jumps to frame 12frame: 15
jumps to frame 14frame: 20
jumps to frame 19Other values show the correct frames.
I've tested in both single row and mutli row mode, but same result.
I'm getting the same result by triggering the "frameChange" event:
$("#reel").trigger('frameChange', 15);
I want to save the current frame and row, so I can later load to the state it was saved in.
Therefore I need the correct values.
Thanks in advance!
UPDATE:
This seems to be the same issue as described by Archivist. My apologies for the duplicate.
The text was updated successfully, but these errors were encountered: