Bugzilla – Bug 475
Use of uninitialized value in repeat (x) at Slim/Display/Graphics.pm line 56.
Last modified: 2008-12-18 11:51:25 UTC
Use of uninitialized value in repeat (x) at Slim/Display/Graphics.pm line 56. It appears that $cursorend is not always set to a defined value and generates a warning (only verified under --d_plugins).
I saw this too, while working on INPUT:Text. This might be fixed becuase I haven't seen it since cleaning it up. If you have a repeatable case where this would occur, please test it again after trying the Aug 6 build. Let us now if this issue has been resolved.
Appears to be fixed. Reopen if it's still a problem.
still occurs in certain cases then exiting INPUT.Text using SavePlaylist or Live365 Plugins. The string is split on null so it seems odd that $char would be undefined. However, forcing $cursorend to be simply 0 if not previously defined.
Created attachment 105 [details] initialise $cursorend to avoid a warnign msg This defines $cursorend so that the value is never undefined. The later test can still use !$cursorend instead of !defined with the same results.
looks like Dean commited this fix a day or two ago. Jim, if you can confirm that this also works for you, please feel free to mark this one as closed.
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.