brl/gnome-shell
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove left-over comment

Browse Source 
Remove comment in frame-ticker code about dynamically adjusting
FRAME_RATE - we no longer do that.

svn path=/trunk/; revision=178
This commit is contained in:
Owen Taylor 2009-02-03 21:25:27 +00:00
parent 4117739abb
commit 5f5a41b54e
1 changed files with 0 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
js/ui/main.js
View File

@ -56,16 +56,6 @@ ClutterFrameTicker.prototype = {
}, },
_onNewFrame : function(frame) { _onNewFrame : function(frame) {
// Unfortunately the interface to to send a new frame to tweener
// is a simple "next frame" and there is no provision for signaling
// that frames have been skipped or just telling it the new time.
// But what it actually does internally is just:
//
// _currentTime += 1000/_ticker.FRAME_RATE;
//
// So by dynamically adjusting the value of FRAME_RATE we can trick
// it into dealing with dropped frames.
// If there is a lot of setup to start the animation, then // If there is a lot of setup to start the animation, then
// first frame number we get from clutter might be a long ways // first frame number we get from clutter might be a long ways
// into the animation (or the animation might even be done). // into the animation (or the animation might even be done).