LinuxMCE Forums

General => Developers => Topic started by: pigdog on April 11, 2009, 03:03:58 pm

Title: 810 alpha2 Clock not updated on LMCE menu.
Post by: 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.
Title: Re: 810 alpha2 Clock not updated on LinuxMCE menu.
Post by: totallymaxed on April 11, 2009, 04:39:56 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
Title: Re: 810 alpha2 Clock not updated on LinuxMCE menu.
Post by: pigdog on April 11, 2009, 05:04:39 pm
Hi,

Thanks totallymaxed.

Cheers.
Title: Re: 810 alpha2 Clock not updated on LinuxMCE menu.
Post by: tschak909 on April 11, 2009, 07:41:34 pm
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
Title: Re: 810 alpha2 Clock not updated on LinuxMCE menu.
Post by: Kaelix on August 03, 2009, 05:27:35 pm
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.
Title: Re: 810 alpha2 Clock not updated on LinuxMCE menu.
Post by: tschak909 on August 03, 2009, 06:14:06 pm
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
Title: Re: 810 alpha2 Clock not updated on LinuxMCE menu.
Post by: kyfalcon on August 05, 2009, 04:00:11 pm
Thom, is it possible when you do this to put the time as am/pm instead of military time?
Title: Re: 810 alpha2 Clock not updated on LinuxMCE menu.
Post by: tschak909 on August 05, 2009, 04:43:41 pm
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
Title: Re: 810 alpha2 Clock not updated on LinuxMCE menu.
Post by: hari on August 05, 2009, 05:59:34 pm
am/pm? We don't use that here :-) If that will be changed I want an option..
Title: Re: 810 alpha2 Clock not updated on LinuxMCE menu.
Post by: ihaar on December 23, 2009, 08:15:12 am
the clock still does not update until the screen changes.
Has this issue been fixed?

(8.10 beta2)

thnx
Title: Re: 810 alpha2 Clock not updated on LinuxMCE menu.
Post by: tschak909 on December 23, 2009, 01:11:09 pm
This will not be fixed by us, until the orbiter is rewritten.

-Thom
Title: Re: 810 alpha2 Clock not updated on LinuxMCE menu.
Post by: los93sol on December 23, 2009, 07:43:04 pm
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?