MP3Car.com - View Single Post

hari-bhari · 11-01-2007, 01:48 AM

Quote: Originally Posted by guino

The ilist has a feature which detects how far it has to scroll to center to an item. In which case, if it's over 50 items, it first does a direct jump to 50 items away from the desired location, THEN scrolls it to the location (giving the impression of scrolling through it real fast). If the list is scrolling for over 3 seconds then there's definitely a bug in the code, and I'd like you to post your IL definition so I can test it myself.

In another note, if you don't wish the ilist to center on the new song when it changes, simply set "listfollowssong=false" in RR.INI

where would i find the IL definition you refer to exactly? and when you refer to the list recentering in the new song, let me just clarify that what i mean by that is that if im on track 14 in a 25 track playlist, and then jump to track 16 by clicking it, it cycles all the way down to 25 and then starts over at 1 and recenters on 16. is this intended behavior?

11-01-2007, 01:48 AM	#124
hari-bhari Maximum Bitrate Join Date: Jul 2006 Posts: 616	Quote: Originally Posted by guino The ilist has a feature which detects how far it has to scroll to center to an item. In which case, if it's over 50 items, it first does a direct jump to 50 items away from the desired location, THEN scrolls it to the location (giving the impression of scrolling through it real fast). If the list is scrolling for over 3 seconds then there's definitely a bug in the code, and I'd like you to post your IL definition so I can test it myself. In another note, if you don't wish the ilist to center on the new song when it changes, simply set "listfollowssong=false" in RR.INI where would i find the IL definition you refer to exactly? and when you refer to the list recentering in the new song, let me just clarify that what i mean by that is that if im on track 14 in a 25 track playlist, and then jump to track 16 by clicking it, it cycles all the way down to 25 and then starts over at 1 and recenters on 16. is this intended behavior?