News:

Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com

Main Menu

810 alpha2 Clock not updated on LMCE menu.

Started by pigdog, April 11, 2009, 03:03:58 PM

Previous topic - Next topic

pigdog

Hi,

On Core/Hybrid the clock time is not incremented on the main menu.

It gets refreshed by closing (left click - mouse) and opening (right click - mouse) the menu.

Haven't checked MD's.

Cheers.

totallymaxed

Quote from: pigdog on April 11, 2009, 03:03:58 PM
Hi,

On Core/Hybrid the clock time is not incremented on the main menu.

It gets refreshed by closing (left click - mouse) and opening (right click - mouse) the menu.

Haven't checked MD's.

Cheers.

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.

Andrew
Andy Herron,
CHT Ltd

For Dianemo/LinuxMCE consulting advice;
@herron on Twitter, totallymaxed+inquiries@gmail.com via email or PM me here.

Get Dianemo-Rpi2 ARM Licenses [url="http://forum.linuxmce.org/index.php?topic=14026.0"]http://forum.linuxmce.org/index.php?topic=14026.0[/url]

Get RaspSqueeze-CEC or Raspbmc-CEC for Dianemo/LinuxMCE: [url="http://wp.me/P4KgIc-5P"]http://wp.me/P4KgIc-5P[/url]

Facebook: [url="https://www.facebook.com/pages/Dianemo-Home-Automation/226019387454465"]https://www.facebook.com/pages/Dianemo-Home-Automation/226019387454465[/url]

[url="http://www.dianemo.co.uk"]http://www.dianemo.co.uk[/url]

pigdog


tschak909

Totallymaxed, let me know the fix, and I'll do it here.

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?

If so, I can make that change here now.

-Thom

Kaelix

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.

tschak909

currently, the clock does not update until the screen changes. I will have to add code to orbiter's maintenance thread to take care of it.

-Thom

kyfalcon

Thom, is it possible when you do this to put the time as am/pm instead of military time?

tschak909

it's pretty low on the list....

it would be nice if someone else took on the patch...but it would be a nice feature..

-Thom

hari

am/pm? We don't use that here :-) If that will be changed I want an option..
rock your home - [url="http://www.agocontrol.com"]http://www.agocontrol.com[/url] home automation

ihaar

the clock still does not update until the screen changes.
Has this issue been fixed?

(8.10 beta2)

thnx

tschak909

This will not be fixed by us, until the orbiter is rewritten.

-Thom

los93sol

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?