summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 3.20.63.20.6Matthias Clasen2016-05-232-2/+15
|
* stack: Only map children when necessaryFlorian Müllner2016-05-231-2/+1
| | | | | | | | | | | gtk_widget_set_parent() will map the widget if the parent is mapped and the widget is both visible and child-visible. As we currently only set the child visibility after adding the child, we immediately map all children that are added to a mapped stack, even when they are not actually shown. Avoid this by setting the child visibility before adding the child, so widgets are only mapped when shown. https://bugzilla.gnome.org/show_bug.cgi?id=766737
* treeview: Fix a rubberbanding-related crashMatthias Clasen2016-05-231-14/+41
| | | | | | | | When starting a rubberband selection from an empty area, we could run into crashes if the selection moves over the rows and then back out to unpopulated area. Handle this case without crashing. https://bugzilla.gnome.org/show_bug.cgi?id=766336
* popover: set priv->window before setting doing add_popover() on itCarlos Garnacho2016-05-211-4/+4
| | | | | | | | | | | | If the popover's relative-to widget is unparented/reparented, we end up unparenting/reparenting the popover as well. In that case, at the moment of reparenting, the widget might have been visible (and is thus mapped again), but priv->window hasn't been set yet. We must first set priv->window, and then call gtk_window_add_popover(), that way gtk_popover_map() has its prerequisites straight. https://bugzilla.gnome.org/show_bug.cgi?id=766323
* Update Arabic translationKhaled Hosny2016-05-211-815/+977
|
* Adwaita: add vertical margins to switches on a headerbarLapo Calamandrei2016-05-203-1/+11
| | | | See https://bugzilla.gnome.org/show_bug.cgi?id=766642
* Adwaita: shave 1px from the switchLapo Calamandrei2016-05-203-6/+6
| | | | make the switch height and width 1px smaller.
* Revert "scrolledwindow: Remove child before destroying self"Matthias Clasen2016-05-201-5/+0
| | | | | | | | This reverts commit dcb4b48b29559ca632bb020a3b8eb2b9188b02e7. This was causing crashes in the filechooser in some applications. https://bugzilla.gnome.org/show_bug.cgi?id=766694
* gtktextview: fix < public > commentIgnacio Casal Quinteiro2016-05-201-1/+1
| | | | This was causing problems with the gtk# scanner
* 3.20.53.20.5Matthias Clasen2016-05-191-2/+2
|
* UpdatesMatthias Clasen2016-05-191-0/+15
|
* gtk-demo: Fix revealer demoMatthias Clasen2016-05-191-3/+6
| | | | | | | | | This only used by luck before. We are changing a property from the ::notify handler for that property. Now that GtkRevealer is notifying the property when it stops animations on unmap, we end up in a life lock situation where we never make it out of the notify queue. Fix this by not restarting the animation if the widget is unmapped.
* scale css node test: Adapt to changesMatthias Clasen2016-05-191-3/+3
| | | | The style classes are reflected in the output here.
* wayland: Survive lack of settingsMatthias Clasen2016-05-191-0/+2
| | | | | | This can be made to happen eg by setting XDG_DATA_DIRS and XDG_DATA_HOME to /. Not a useful value, but not a good reason to crash either.
* gdk/wayland: use the multi-thread safe wayland APIMatthew Waters2016-05-191-12/+44
| | | | | | | | | | | | | | | | This is required for proper integration with any other library/application that may perform wayland API calls and poll() the wayland fd from multiple threads. Using wl_display_dispatch{_queue}() is thread-safe if not mixed with custom poll() usage, which GSource/GMainContext does. Essentially, the problem is that multiple threads polling and reading the same fd is extremely racy. Use the wayland provided API for allowing concurrent access to the wayland display fd. See the wayland man pages for wl_display_prepare_read(), wl_display_cancel_read() and wl_display_read_events() for more details. https://bugzilla.gnome.org/show_bug.cgi?id=763852
* scrolledwindow: Fix typo in get_preferred_height calculationDebarshi Ray2016-05-191-3/+3
| | | | | | | | | | | | | | | | | When we are beginning to calculate the height, if the vscrollbar_policy is not GTK_POLICY_NEVER, and there is no min-content-height, then we need some small non-zero value to get started. The idea is to always ask for at least enough to fit the horizontal scrollbar. Simply put, this should be the mirror image of the corresponding width calculation code. Those who got used to the buggy behaviour might notice that their GtkScrolledWindows are not as tall as they used to be. Fall out from 55196a705f00564a44647bfc97981db0a783369a https://bugzilla.gnome.org/show_bug.cgi?id=766530
* icon theme: Add a warningMatthias Clasen2016-05-191-1/+24
| | | | | | | Warn about the situation when we've found a resource or file path, but gdk-pixbuf fails to give us a pixbuf. This generally means that either pixbuf loaders are not found or the shared-mime database is missing.
* stack: Don't underallocate the last_childTimm Bäder2016-05-191-4/+9
|
* stack: Remove some code duplicationTimm Bäder2016-05-191-6/+2
|
* places sidebar: Avoid markup confusion in tooltipsMatthias Clasen2016-05-191-4/+1
| | | | | | | | At one point, the sidebar was using gtk_treeview_set_tooltip_column, which expects tooltips to be markup. With the listbox-based sidebar, we don't do that anymore. So don't escape the tooltip text. https://bugzilla.gnome.org/show_bug.cgi?id=766175
* x11: Trap possible X errorMatthias Clasen2016-05-191-3/+7
| | | | | | | XIGetClientPointer can generate X errors (e.g. when the X server does not support XI2. Trap them and carry on. https://bugzilla.gnome.org/show_bug.cgi?id=766233
* scale: Remove double nullable annotationTimm Bäder2016-05-191-1/+1
| | | | | Being both (allow-none) and (nullable) at the same time is a bit much. Was from 591e7f5ef8538982e227b2c2cefc536a33cafa6c.
* widget: Add Since annotation to gtk_widget_queue_allocateTimm Bäder2016-05-191-0/+2
|
* scrolledwindow: Remove child before destroying selfBenjamin Otte2016-05-191-0/+5
| | | | | | Children tend to call back into the scrolled window while being removed and that doesn't work too well if the scrolled window is destroyed already as Christian Hergert found out.
* cssimage: Make it possible to shrink builtin check/optionmarksBenjamin Otte2016-05-191-30/+10
| | | | ... below 7px of size.
* gtk3-demo: Add a close button to the markup windowMatthias Clasen2016-05-191-0/+1
|
* gtk-demo: Don't duplicate text in markup exampleMatthias Clasen2016-05-191-1/+2
| | | | I forgot to clear the buffer before inserting the new markup. Oops.
* revealer: emit notify::child-revealed when animation stopsMatthieu Gautier2016-05-191-2/+5
| | | | | | | | | | | | Depending of float rounding during target calculation, the size of the GtkRevealer can be set to zero will the animation is not finished. If the GtkRevealer is in a GtkPaned, it will be hidden and so the animation will be stopped before it is finished. In this case, force the emission of the child-revealed signal to let client code know the animation is finished. https://bugzilla.gnome.org/show_bug.cgi?id=765973
* infobar: Fix typoTimm Bäder2016-05-191-1/+1
| | | | Style class names are prefixed with a '.'
* Adwaita: fix scale themingLapo Calamandrei2016-05-193-176/+132
| | | | | | rely on toplevel styleclass for scale with marks. See https://bugzilla.gnome.org/show_bug.cgi?id=766440
* color scale: Really sync style classes with GtkScaleLapo Calamandrei2016-05-191-1/+1
| | | | sync the alpha scale styleclass too.
* color scale: Sync style classes with GtkScaleMatthias Clasen2016-05-191-2/+2
| | | | | We should use the same style classes here, to avoid theme confusion.
* gtkselectionprivate: minor style fixIgnacio Casal Quinteiro2016-05-191-1/+1
| | | | This seems to make some issue with the gtk# scanner.
* scale: Use more succinct names for style classesMatthias Clasen2016-05-191-7/+7
| | | | | | | | | Use .marks-before/after to indicate the presence of marks. As Lapo points out, compatibility with the previous names is not really that important, since everything else changed around it. https://bugzilla.gnome.org/show_bug.cgi?id=766440
* scale: Bring back marks-related style classesMatthias Clasen2016-05-181-1/+20
| | | | | | | | | | It turns out that it is too hard (and in some cases, impossible) to get this information from node positioning, so bring back the .scale-has-marks-above/below style classes on the main node. This should allow us to fix the 'pointy sliders'. https://bugzilla.gnome.org/show_bug.cgi?id=766440
* x11/dnd: Ignore grab broken events from other devices than our DnD device.Carlos Garnacho2016-05-181-0/+4
| | | | | | | | | The GdkDragContext should only listen to GDK_GRAB_BROKEN events sent to its own pointer device. It turns out that the passive key grabs mistake GDK into sending a GdkEventGrabBroken on the master keyboard, which the DnD machinery mistakes as a signal to cancel the operation. https://bugzilla.gnome.org/show_bug.cgi?id=766442
* Updated Kazakh translationBaurzhan Muftakhidinov2016-05-171-285/+291
|
* Docs: Clarify life cycle issueMatthias Clasen2016-05-171-0/+4
| | | | | | | gtk_gesture_get_last_event() wasn't very clear about how long it is safe to use the returned pointer. (cherry picked from commit c891ceb31df1fb16c7727be46cee4d8a9fc0b447)
* DND: Avoid a use-after-freeMatthias Clasen2016-05-171-3/+7
| | | | | | | | Cancelling the gesture causes the last_event pointer to become invalid. Make a copy of the event so we can keep using it regardless of the gesture state. (cherry picked from commit 358eec297204b438809692a24cc3649658dbab5a)
* Updated Portuguese translationTiago Santos2016-05-151-924/+1041
|
* Updated Portuguese translationTiago Santos2016-05-151-1411/+1458
|
* Visual Studio builds: Refine "installation" processChun-wei Fan2016-05-104-50/+46
| | | | | | Split out the part where we generate/update the caches for the GSchemas and the icons, so that it is easier to ensure that things continue to function correctly when we have GlibEtcInstallRoot != CopyDir.
* 3.20.43.20.4Matthias Clasen2016-05-092-2/+52
|
* Update css node tests for removal of .slider from GtkSwitchMatthias Clasen2016-05-091-2/+2
|
* docs: Update examples of matching key bindingsEmmanuele Bassi2016-05-091-6/+9
| | | | | | The selector for matching GtkEntry has changed to `entry` after 3.20. https://bugzilla.gnome.org/show_bug.cgi?id=766166
* Updated Brazilian Portuguese translationRafael Fontenelle2016-05-081-279/+275
|
* Adwaita: relocate a selectorLapo Calamandrei2016-05-063-10/+6
| | | | | relocate treview acceleditor > label in the treeview section and add a comment for a testcase.
* Adwaita: tidy treeview style properties...Lapo Calamandrei2016-05-063-23/+23
| | | | ...removing a double definition in the process.
* scale: Fix mark positioning at the left/top edgeMatthias Clasen2016-05-051-1/+5
| | | | | | | We were failing to take the widget allocation.x/y into account when deciding whether we need to push in the mark. https://bugzilla.gnome.org/show_bug.cgi?id=765922
* x11: Rely on passive keyboard grabs with XI2 for DnDCarlos Garnacho2016-05-051-1/+9
| | | | | | The active keyboard grab can be spared then. This way the passive key grabs allow other key combinations (eg. alt-tab) that are not mandatory to grab here.
View Lorry Controller Status