2005-03-08, 14:13
it's because the buttonscroller is in it's own control group (at least in pm1).
i don't see the need for this, and removing it fixes the issue.
reason is that xbmc first loads all controls in the default control group (ie no <controlgroup> specified) then loads each of the <controlgroup> blocks in turn.
cheers,
jonathan
i don't see the need for this, and removing it fixes the issue.
reason is that xbmc first loads all controls in the default control group (ie no <controlgroup> specified) then loads each of the <controlgroup> blocks in turn.
cheers,
jonathan