Age | Commit message (Collapse) | Author | Files | Lines |
|
Proxy paths, and enumeration from the current API.
|
|
The Makefile rule was using GI_REPOSITORY_PATH instead of
GI_TYPELIB_PATH meaning that if a custom typelib path was needed
(jhbuild for example) it wouldn't be found.
|
|
|
|
When switching off Bluetooth devices, and before they timeout,
we won't be able to read the battery percentage, so don't
overwrite the previous value with "0%", but set the state to
unknown instead.
https://bugs.freedesktop.org/show_bug.cgi?id=70325
|
|
|
|
In up_device_supply_get_state()
|
|
When refreshing the state of device batteries, no need
to get data that won't be there anyway, such as voltage, temperature,
or consumption rate.
This avoids warnings about voltage being unknown for devices, and
cuts down on the properties churn.
|
|
We're going to be reusing this elsewhere.
|
|
We already have enough information on the device battery.
This avoids having a device for the wacom AC which we won't use.
|
|
Not all "UpDeviceSupply" actually supply power to the computer.
|
|
When the device was removed, we forgot to cancel sending
out changed properties, causing illegal memory accesses.
|
|
|
|
|
|
|
|
|
|
Now that we send out PropertiesChanged signals (on the daemon side)
and "notify" signals (on the client side), there's no need for the
all encompassing DeviceChanged and Changed signals.
They would have woken up any client, even if they were not interested
in receiving the signals.
|
|
This is a hack that was in gnome-settings-daemon's power plugin.
We would check whether we were on AC before saying for certain
that batteries had a low-level, and raising the warning-level.
|
|
This allows desktop front-ends to get which action will
actually be taken when we hit critical battery.
This is not a property as availability of actions might
change over the course of the run of the system, and
we didn't want to make unnecessary D-Bus calls on startup.
|
|
A simple reversed check...
|
|
So we can update the display device warning level.
|
|
The WarningLevel property just replicated the warning level
on the display device, or at least should have. So we fix the latter
to remove the former.
|
|
|
|
Those are also part of the display device properties that we
will update.
|
|
/org/freedesktop/UPower/devices/DisplayDevice is a stable
object path.
|
|
When it doesn't actually change, don't send out signals.
|
|
The interface name was missing ".Device" at the end, so wasn't
getting registered by clients.
|
|
The IconName and WarningLevel properties were not sent out through
PropertiesChanged when they changed for devices.
|
|
When none of the properties of the display device change,
do not modify it.
|
|
And export a DisplayDevice object which can be used by desktop
shells to show/hide the status icon.
|
|
When on battery only, we weren't setting the display device type
properly.
|
|
|
|
|
|
up_daemon_get_on_battery() and up_daemon_get_warning_level()
weren't defined or used anywhere.
|
|
|
|
That will make libupower-glib UpDevice work again, as the proxy
was not receiving property changes, and we kept reading old
cached values.
|
|
Add code to transform strings, doubles, uint64s, and int64s.
|
|
Instead of sending one changed signal at a time, coalesce them
together to reduce wakeups.
We also export up_daemon_emit_properties_changed() for UpDevice
to use.
|
|
By using the state of all the combined batteries, rather than
each one (eg. 2 batteries of the same type at 15% shouldn't trigger
the "low" warning level).
This introduces code to calculate the state of a "display" device,
which is either a UPS, or a combination of all batteries.
|
|
|
|
|
|
In UpDevice.
|
|
Both for the daemon and devices, so as to avoid D-Bus changes
storms on startup.
|
|
We weren't emitting GObject signals in coldplug, no need to send out
D-Bus signals either.
|
|
|
|
When UPSes are discharging, we should have a warning already, as
it means that mains power has been lost to the UPS (though not
to the computer).
|
|
There's no reason why the state check should be done in the UpDevice
implementation, and the state will be needed to add a new warning
level for UPSes.
|
|
And remove ifdef's.
|
|
Sends out icon names as defined by the Icon Naming specification.
Will save quite a bit of client side code.
|
|
Paraphrasing from the configuration option:
The action to take when "TimeAction" or "PercentageAction" above has
been reached for the batteries (UPS or laptop batteries) supplying
the computer.
This is done 20 seconds after the warning-level variable got set
to UP_DEVICE_LEVEL_ACTION has been set, to give the opportunity
to front-ends to display a (short) warning.
This is only implemented for the Linux backend, using logind.
|
|
Use raw D-Bus.
https://bugs.freedesktop.org/show_bug.cgi?id=43001
|