summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* display: Implement major/minor axis snapping and infinit for edgeswip/benzea/displayBenjamin Berg2018-05-171-31/+68
| | | | | | | | This improves the snapping behaviour in a number of ways. It allows increasing the snapping distance while still helping the user to align monitors by snapping a different distance for the minor axis. The patch also allows setting this distance to infinity so that we get the correct behaviour in the case of two monitors for the corners.
* display: Enable infinit snapping when arranging two monitorsBenjamin Berg2018-05-171-1/+35
| | | | | | | Two monitors are a special case where it is easy to ensure that the monitors are always adjacent to each other by special casing the snapping code. Do so by increasing the snapping distance to infinity and adding extra snapping points so that corner cases are covered.
* display: Move output utility functions into CcDisplayMonitorBenjamin Berg2018-05-174-184/+256
| | | | | | | | | | | | | | | | | | This adds the following API: * cc_display_config_get_ui_sorted_monitors Returns the monitors in UI order * cc_display_config_count_useful_monitors Counts the useful monitors (active and usable) * cc_display_monitor_is_useful Checks if a monitor is active and usable * cc_display_monitor_is_useable Check if a monitor is marked as useable * cc_display_monitor_set_usable Used to mark builtin monitors as unusable if the lid is closed * cc_display_monitor_get_ui_* Get the UI number and strings for display https://bugzilla.gnome.org/show_bug.cgi?id=786971
* display: Remove incorrect commentBenjamin Berg2018-05-171-6/+0
| | | | | | The comment was not updated when the workaround in the code was removed. https://bugzilla.gnome.org/show_bug.cgi?id=786971
* display: Remove unused old display arrangement codeBenjamin Berg2018-05-174-2479/+1
| | | | | | | | | Remove the code that has become unused with the new arrangement widget. There are more possible cleanups as there is some code duplication between cc-display-panel.c and cc-display-arrangment.c at this point. https://bugzilla.gnome.org/show_bug.cgi?id=786971
* display: Add new arrangement widget and hook it upBenjamin Berg2018-05-176-12/+987
| | | | | | | | | | This commits adds a new arrangement widget, refactoring the existing code and addressing a number of issues: * Forced snapping made laying out more than 2 monitors hard * Random gaps would be shown between monitors * The scaling was fixed and usually tiny https://bugzilla.gnome.org/show_bug.cgi?id=786971
* display: Add signal to monitor notifying about position changesBenjamin Berg2018-05-172-0/+14
| | | | | | This is in preparation to a new arrangement widget. https://bugzilla.gnome.org/show_bug.cgi?id=786971
* display: Re-indent cc-display-config.hBenjamin Berg2018-05-171-90/+117
| | | | This commit has no functional changes.
* docs: update the "report bugs" linkClaudio André2018-05-161-1/+1
| | | | [skip ci]
* CI: handle patches while creating a flatpakClaudio André2018-05-161-0/+1
| | | | Make the flatpak routine able to deal with patches (if needed).
* ci: Reorganize filesGeorges Basile Stavracas Neto2018-05-162-8/+8
|
* thunderbolt: Fix buildMichael Catanzaro2018-05-161-0/+2
| | | | | Providing autocleanups for types you don't own is not a good idea, since it breaks when upstream adds those autocleanups.
* CI: create a flatpakClaudio André2018-05-151-0/+51
| | | | | The goal is dogfooding. Allow interested people to try, safely, the bleeding GNOME Control Center.
* project: add the renames required by flatpakClaudio André2018-05-151-1/+3
| | | | | The names of files that are exported by a Flatpak must prefixed using the application ID.
* Update Galician translationFran Dieguez2018-05-151-184/+221
|
* Update Galician translationMarcos Lans2018-05-151-544/+782
|
* Updated Slovenian translationMatej Urbančič2018-05-151-52/+65
|
* Merge branch 'master' of gitlab.gnome.org:GNOME/gnome-control-centerMatej Urbančič2018-05-15179-4715/+18883
|\
| * CI: print some info about the build envClaudio André2018-05-142-1/+79
| | | | | | | | | | It is not possible to debug if the developer knows nothing about the CI running environment.
| * CI: add status information to the buildClaudio André2018-05-141-1/+3
| |
| * window: Warn about development buildsGeorges Basile Stavracas Neto2018-05-145-2/+96
| | | | | | | | | | | | | | | | | | | | | | | | With this commit, a message dialog pops up whenever a development build runs. This is meant to actually annoy, so that we're always reminded that things may not work as expected. Since the dialog can be dismissed with a single button press, it is not the end of the world. But people still should be aware that Settings is ~not~ meant to run with Flatpak, and that this is a development tool only.
| * project: Add a development flatpak manifestGeorges Basile Stavracas Neto2018-05-141-0/+446
| | | | | | | | | | | | | | | | | | The development flatpak is meant to be used exactly that: development. It isn't and won't ever be released as a regular Flatpak application. GNOME Setting is still supposed to run as a host system tool.
| * project: Move build files to build-auxGeorges Basile Stavracas Neto2018-05-146-9/+6
| | | | | | | | | | | | An attempt to make the root folder slightly less cluttered and more organized. No functional changes whatsoever.
| * CI: use an updated Docker imageClaudio André2018-05-131-1/+1
| | | | | | | | | | We value repeatability and reproducibility; that said, we need to use a fresh Fedora. So, pick an image that is updated every week.
| * CI: pass build artifacts to another stageClaudio André2018-05-131-2/+8
| | | | | | | | | | | | Avoid to redo some tasks (save git untracked files e use them). See #46.
| * docs: Fix code blockGeorges Basile Stavracas Neto2018-05-131-0/+1
| |
| * docs: Document style of commentsGeorges Basile Stavracas Neto2018-05-121-0/+12
| |
| * project: Update gitignoreGeorges Basile Stavracas Neto2018-05-121-0/+2
| |
| * CI: add build status badgeClaudio André2018-05-121-1/+4
| | | | | | | | [skip ci]
| * user-accounts: Fix hint for wrong enterprise user/passwordOndrej Holy2018-05-122-2/+3
| | | | | | | | | | | | | | A variable of label widget, used for a hint when wrong enterprise user/password is used, is not properly initialized and thus criticals are shown instead of the hint when user/password is wrong. Let's bind the variable properly.
| * tests/network: Disable on non-Linux systemsTing-Wei Lan2018-05-121-1/+3
| | | | | | | | | | NetworkManager is only available on Linux, so we cannot build or run the network test on non-Linux systems.
| * CI: shrink the test processClaudio André2018-05-121-36/+10
| | | | | | | | See #46
| * night-light-dialog: Ignore G_IO_ERROR_CANCELLED errorsAndrea Azzarone2018-05-121-7/+9
| | | | | | | | | | | | | | We should ignore G_IO_ERROR_CANCELLED errors and avoid displaying useless warnings. Also use g_clear_object instead of g_object_unref. Fixes: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/87
| * printers: Focus search entry in new printer dialogadd-printers-dialog-entry-grab-focusMarek Kasik2018-05-102-0/+17
| | | | | | | | | | | | | | Focus search entry in the new printer dialog once user starts to type so he does not need to click on it. Closes #41
| * night-ligth-dialog: Avoid dereferencing invalid pointerAndrea Azzarone2018-05-101-4/+13
| | | | | | | | | | | | | | | | dialog_got_proxy_cb and dialog_got_proxy_props_cb may be called after the instance of CcNightLightDialog has been disposed. Make sure 'self' pointer is not dereferenced if not valid. Fixes: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/86
| * object-storage: Avoid double free when propagating errorAndrea Azzarone2018-05-101-2/+2
| | | | | | | | | | | | | | | | In cc_object_storage_create_dbus_proxy_sync and cc_object_storage_create_dbus_proxy_finish we need to use g_steal_pointer to make sure local_error is not double freed. Fixes: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/86
| * tests: Run each datetime test under XvfbGeorges Basile Stavracas Neto2018-05-092-2/+62
| | | | | | | | That way, gtk_init() cannot fail.
| * tests: Make logging verboseGeorges Basile Stavracas Neto2018-05-091-1/+4
| |
| * tests: Rework test-timezone-gfxGeorges Basile Stavracas Neto2018-05-091-41/+51
| |
| * tests: Rely only on zone.tabGeorges Basile Stavracas Neto2018-05-091-90/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | First of all, this is a complete rewrite of the timezone tests. Everything was revisited, starting from code style, to concepts, etc. The problem with the previous timezone test was that is was relying on listing the /usr/share/zoneinfo directory, and assuming that those entries would be always present. Turns out, some of them are extensions, some of them are undocumented files, etc. A huge mess. I could've blacklisted the undesired files and folders, but that would still be insufficient for other OSes like *BSDs and Sun. The final solution was pretty straightforward: only use the information from zone.tab to run the tests.
| * datetime: Update backwards fileGeorges Basile Stavracas Neto2018-05-091-12/+22
| | | | | | | | | | This is just a plain copy of the most recent (2017-10) backwards file from tzinfo.
| * Update Turkish translationEmin Tufan Çetin2018-05-061-339/+540
| |
| * Update Hungarian translationGábor Kelemen2018-05-051-322/+539
| |
| * Update Friulian translationFabio Tomat2018-05-051-29/+25
| |
| * Updated Czech translationMarek Cernocky2018-05-041-294/+516
| |
| * Update Friulian translationFabio Tomat2018-05-041-314/+523
| |
| * project: Update meson filesGeorges Basile Stavracas Neto2018-05-0311-130/+129
| | | | | | | | | | | | I probably have OCD. Seeing these files with this poor alignment gives me physical pain.
| * shell-model: Remove boilerplate and update code styleGeorges Basile Stavracas Neto2018-05-022-73/+34
| |
| * project: Update DOAP fileGeorges Basile Stavracas Neto2018-05-021-23/+2
| | | | | | | | | | | | The maintainers listed there aren't maintaining it anymore, and shouldn't be pinged about Settings. Please let me know if any of you want your maintainership status back again.
| * project: Add coding style and contribution guidelinesGeorges Basile Stavracas Neto2018-05-023-23/+281
| | | | | | | | And also update the README file.
View Lorry Controller Status