screensaver and power manager dbus interfaces
William Jon McCann
mccann at jhu.edu
Thu Jun 1 18:06:42 EEST 2006
David Zeuthen wrote:
> I think I only have one comment on the current spec:
>> Name: Inhibit
>> Args: DBUS_TYPE_STRING "application-name"
>> DBUS_TYPE_STRING "reason for inhibit"
>> Returns: INT cookie
>> This is a random number used to identify the request.
>> Description: Request that saving the screen due to system idleness
>> be blocked until UnInhibit is called or the
>> calling process exits.
> This is already very accurate, but it might be useful to clarify exactly
> what this means through a few examples.
> For example, the PowerManager SHOULD ignore applications using Inhibit()
> if e.g. the user is closing the laptop lid. The Power Manager SHOULD
> prompt the user if user is trying to suspend while an app is using
> Inhibit() and the screen is still visible.
Another example, the screensaver MUST ignore inhibitors when the Lock()
method is called. This is one reason why we chose to use the term
"inhibit" rather than block or suspend or something.
> Stuff like that; I think it might be useful with a few MUST and SHOULD
> clauses to guide implementors of these interfaces in the same direction.
Certainly a good idea.
More information about the xdg