[Portland] command line interface inconsistancies

[Bastian, Waldo]

>> >> I'm
>> >> also inclined to remove "restore" since I don't think it's really
>> needed
>> >> if the screensaver gets re-enabled after 5 min. anyway.
>> >
>> >Actually, I would discourage removing that.  It is actually one of
the
>> >most useful functions in the package, because it is guaranteed to
>> >"reset" the system to the starting state.  In other words, this is
the
>> >command applications will call when they terminate normally, in
order
>> to
>> >put everything back the way before they started.
>>
>> Is that really needed if the screensaver is delayed for at most 5
>> minutes?
>
>Since you can't count on the suspend functionality recently implemented
>in Xorg to be there all the time, yeah this is definitely appropriate
to
>include in this package, regardless of how long the screensaver is
>delayed.
>
>Also, why would anyone bother to delay a screensaver for only 5
minutes?
>Most presentations where screensavers become an issue last at least 30
>minutes...

The application would delay the screensaver for 5 minutes every 5
minutes for the duration of the presentation.

>> >Also note that restore involves restoring several settings, not just
>> >whether or not the screensaver is currently on or off.
>>
>> What other settings does it control then?
>
>It controls the timeout and cycle values, whether the screensaver is on
>or off, whether or not the screensaver is enabled or disabled, and the
>power management state/settings too.

I think it should only reset those settings that have been changed with
a prior call to xdg-screensaver. Be symmetrical with xdg-screensaver
suspend.

Cheers,
Waldo