We've fixed this in our Dianemo releases. The fix is in Designer and will work fine in LinuxMCE-0810. I thought we had already committed that fix to the svn...but it obviously dell through 'the cracks' somewhere...I'll chase it up next week.

Now, I do know that the <%=CLOCK=%> replacement is something of an oddity, there is no explicit runloop to increment that text object in orbiter itself, so are you taking care of this somewhere else? are you utilizing the screen Timeout?

I just started using Linuxmce about 2 weeks ago, I've run into some roadblocks but I've managed to work through them using the forums and the wiki. However I'm at a loss on this one. I have alpha2.26 and the clock is still hanging, has this issue been fixed? I haven't been able to find a solution or another mention other than this post.

Also it seems 'Seconds before screen saver' in the on-screen orbiter settings is controlling when my system turns off instead of 'Seconds before power off' (I have 'Leave monitor on for OSD checked' and a webdt366 orbiter). I wouldn't mind leaving the on-screen orbiter up and setting it to the same value as 'power off' but I would like the time to be updated.

Hasn't this issue been there forever? IE. Having to change screens to refresh the displayed items? Perhaps a workaround for this would be to send a goto screen message to refresh the screen whenever a button is pressed on any screen. Another place I've seen this happen is with the Climate floorplan when changing temperatures on a thermostat. Would the goto screen fix work in the meantime until Orbiter can be rewritten to properly fix the issue? As I understand it the problem is because of how orbiter pre-renders everything so what you see on the orbiter was rendered before you went to view the screen which makes it static until a refresh occurs. Is that correct?