[MeeGo-touch-dev] sysuid: context Alarm.Present
aki.koskinen at nokia.com
Thu Aug 19 23:52:35 PDT 2010
On 08/19/2010 05:23 PM, ext Patrick Ohly wrote:
> Is this list also the right place to ask questions about MeeGo Touch
> Framework components like sysuid?
Suits fine for me.
> I saw in the source that it watches the ContextKit Alarm.Present
> property. I've written an experimental provider for that, something
> which is currently missing in MeeGo.
> context-listen confirms that Alarm.Present is indeed provided and
> reports the value that my daemon sets, so that part seems to be working.
> But I don't see any changes in the top bar of my screen. At the top
> right I see a white (or greyish) Bluetooth icon, then some black space,
> then the current time. Should there be an icon for "alarm present" or
> "not present"? That's kind of what I expected.
> If that depends on theming, can you give some hints what the theme must
> provide to have such an "alarm present" indicator?
That does depend on theming. When an alarm is present (the context
property Alarm.Present returns true) the object name of the status
indicator changes from AlarmStatusIndicator to AlarmStatusIndicatorSet.
So in the stylesheet there must be something like this (this is directly
from sysuid's style):
If you have sysuid running, with style sheets in correct place and all,
then you should see the alarm indicator just fine.
> Now, one more question about Alarm.Present. The ContextKit spec
> (context-properties.html) describes it as:
> Alarm.Present (bool)
Make sure your property type really is bool and not something else.
> Indicates whether there is an upcoming alarm set by the user.
> Can be true even if alarms are disabled.
> My interpretation is that this relates to alarms set by the user via a
> dedicated alarm application ("remind me at 12:00"), but not to alarms
> set for calendar events.
I would interpret that the same way. Alarm here means what is also known
as "clock alarm".
Senior SW Engineer
Itämerenkatu 11-13, Helsinki, Finland
More information about the MeeGo-touch-dev