-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hide adaptive modes (theme, brightness/redshift) if geoclue-2.0 DBus service is not available #95
Comments
I don't think we need to do this: the indicator has a fallback longitude/latitude which can be tweaked in GSettings. |
Please hide those menu items if they cannot be used. Note that the customer's target system is an enterprise desktop. Showing features that don't exist is no option there. |
But that's exactly my point: those features do exist and can be used even without geoclue. |
So, for clarification: For the enterprise Linux, we want:
The enterprise desktop won't have geoclue running and in that case, the following menu items should be invisible/hidden:
The adaptive seems to be alluding auto-leveling those well you by some information (time of day, timezone, location, time of year). Are you saying that the auto-leveling works if we simply roll-out geo coordinates via GSettings? |
If so, we should be able to allow the user to adjust those geo-coordinates. (We must assume that they go travelling from time to time). |
However, this might be beyond the scope of a display indicator. In fact, we have white papers for a location indicator. There this would be a nice feature to land. Not sure how to handle this for now, though. |
Yes. I have written it so that it never crashes regardless of the geolocation state. It starts up with the last coordinates stored in GSettings (Greenwich by default) and updates them if geoclue becomes available. If geoclue times out, it stays as-is. |
If there is not geoclue-2.0 provider on the DBus session bus, hide the adaptive modes in display indicator.
The text was updated successfully, but these errors were encountered: