summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* wip: external path bar for file chooserwip/matthiasc/pathbar-in-headerMatthias Clasen2015-06-173-53/+175
|
* Cosmetic changeMatthias Clasen2015-06-171-1/+1
|
* GtkPlacesSidebar: Fix rtl appearanceMatthias Clasen2015-06-173-839/+667
| | | | | | | Apply the necessary directional variants for asymmetric css padding. https://bugzilla.gnome.org/show_bug.cgi?id=751084
* overlay: remove gtk_overlay_add_pass_through_overlay()Cosimo Cecchi2015-06-174-48/+2
| | | | | | | The API to access this functionality will be the setter we just added in the previous commit. https://bugzilla.gnome.org/show_bug.cgi?id=750568
* overlay: add setters and getters for pass-through child propertyCosimo Cecchi2015-06-173-1/+61
| | | | | | This will make the API easier to use from bindings too. https://bugzilla.gnome.org/show_bug.cgi?id=750568
* docs: add new GtkOverlay methods to gtk3-sections.txtCosimo Cecchi2015-06-171-0/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=750568
* configure: test have_docbook_style != yes, not have_docbook_dtdAlexander Larsson2015-06-171-1/+1
|
* file chooser: Drop unused variablesMatthias Clasen2015-06-172-12/+3
|
* file chooser: Use a revealerMatthias Clasen2015-06-172-83/+86
| | | | | | Use a revealer to manage the visibility of the header area where we show the pathbar, the location entry or search. This is a bit smoother, and makes search more similar to a search bar.
* texthandle: Avoid double rendering of background/frameCarlos Garnacho2015-06-171-2/+0
| | | | | gtk_render_handle() already renders background/frame itself, avoid doing this twice.
* gtkmain: Ignore grab for events in child popoversCarlos Garnacho2015-06-171-0/+56
| | | | | | | | | | | | | | Popovers may be spawn when there's GTK+ grabs somewhere else (eg. text selection popover/handles in an entry in a modal popover). When this happens, events go to the grab widget (in this case the modal popover) and are effectively ignored by the event widget, even though it's can be conceptually a child of the grab widget. To get away with this, tweak a bit gtk_main_do_event(), so events going to popovers that are related to grab_widget or a child of it are received, as it would happen with regular children of grab_widget. https://bugzilla.gnome.org/show_bug.cgi?id=750993
* window: Add concept of popover "parent"Carlos Garnacho2015-06-174-5/+62
| | | | | | | | | | | This will be the widget that the popover relates to (::pointing-to in GtkPopover, ::parent in GtkTextHandle). Additional API to check the popover/parent relationship between widgets has been added, which will be useful wherever this is necessary in a generic manner. https://bugzilla.gnome.org/show_bug.cgi?id=750993
* Fix return value error in gdk_window_set_pass_throughTing-Wei Lan2015-06-171-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=751099
* wayland: Always request transient commit when mapping subsurfaceJonas Ã…dahl2015-06-171-0/+3
| | | | | | | | | | | | | A subsurface positioning operation only takes effect when the parent surfaces state is applied. If a subsurface is mapped and positioned, but the parent surface state is not immediately committed, the relative position of the subsurface is undefined and may be placed incorrectly. To avoid this undefined state, always request that the parent surface should be committed after mapping a subsurface so that the position operation will take effect. https://bugzilla.gnome.org/show_bug.cgi?id=751098
* treeview: always pixelcache widget contentsChristian Hergert2015-06-161-0/+2
| | | | | | | | | GtkTreeView has a particularly expensive drawing path. This can cause issues when part of animated widget sequences. Caching the content while a model is attached helps reduce the number of full redraws during exposure greatly. https://bugzilla.gnome.org/show_bug.cgi?id=751082
* pixelcache: allow widgets to always require cached contentChristian Hergert2015-06-162-24/+44
| | | | | | | | | | Some widgets have very expensive drawing paths. So caching the content can be useful even when not scrolling. This can help speed up widgets that are part of animation sequences and thereby go through spurious expose events. https://bugzilla.gnome.org/show_bug.cgi?id=751082
* Updated Hebrew translationYosef Or Boczko2015-06-171-181/+195
|
* gdkwindow: avoid updating background pattern if it matches previousChristian Hergert2015-06-161-0/+15
| | | | | | Background patterns are often updated when style changes. In many cases, the new pattern will match the previous. We can optimize out the invalidation that will occur upon resetting the same pattern.
* gtkplacessidebar: improve variable nameCarlos Soriano2015-06-161-8/+8
|
* gtkplacessidebar: Remove some old commentsCarlos Soriano2015-06-161-26/+2
| | | | | | We didn't made up our minds until now from some of them, and for the others no progress has been made or bugs reported, so probably they are fine.
* gtkplacesidebar: use GtkListBoxCarlos Soriano2015-06-1610-2081/+2283
| | | | | | | | | | | | We were using GTkTreeView in a simple list. Also, as we know, GtkCellRenderers are not the best way to theme and manipulate widgets. So instead use a GtkListBox to modernize the GtkPlacesSidebar, and in the way clean up some parts of the code (like headings) which were not used anymore. Also we don't use a model anymore, since the data is simple enough to manage it in a subclass of the row itself.
* theme: decrease list row transitionCarlos Soriano2015-06-163-528/+528
| | | | | It was somewhat annoying given the "trace" of it. Decrease the time to avoid too much "trace"
* gtkfilechooserwidget: show drop hints on gtkplacessidebarCarlos Soriano2015-06-162-0/+27
| | | | | | | Now with the API addition on gtkplacessidebar, we can show some hints for the drop targets. https://bugzilla.gnome.org/show_bug.cgi?id=747793
* gtkplacessidebar: make insensitive invalid drop targetsCarlos Soriano2015-06-161-1/+54
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=747793
* gtkplacessidebar: add new bookmark iconCarlos Soriano2015-06-161-0/+4
| | | | | | Following design mockups https://bugzilla.gnome.org/show_bug.cgi?id=747793
* gtkplacesidebar: remove obsolete drop stateCarlos Soriano2015-06-161-13/+5
| | | | We didn't use those for some time now.
* gtkplacessidebar: add API for show drop hintsCarlos Soriano2015-06-163-22/+105
| | | | | | | | | | | | | | | | | | | It is convenient to allow applications to show all the drop targets at once. This improves the user experience with drag an drop. The new API allows the application to set the gtkplacessidebar in a mode where invalid drop targets are insensitive and it adds a "new bookmark" row. This mode is intended to be set when the application is aware of a dnd operation and needs to be stopped kwhen the application is aware that dnd operation was cancelled or ended in a different part than gtkplacesisdebar. The context parameter is unused in this patch, but will be used in next patches when the sidebar will use a GtkListBox. The reason of being unused now is just convenience. https://bugzilla.gnome.org/show_bug.cgi?id=747793
* gtkplacessidebar: new bookmark row only at first positionCarlos Soriano2015-06-161-67/+74
| | | | | | | Following the new mockups, put the new bookmark row always in the first position, so it's easier to drop an item. https://bugzilla.gnome.org/show_bug.cgi?id=747793
* Deal with events from wrong displayMatthias Clasen2015-06-152-3/+8
| | | | | | GtkInspector is opening a separate display connection, which makes it more likely that gtk_get_current_event() returns an event from the "wrong" display.
* GtkMenuButton: Make programmatic toggling work againMatthias Clasen2015-06-151-13/+23
| | | | | | This was broken in 0796d7b6ff9393746d. https://bugzilla.gnome.org/show_bug.cgi?id=751018
* GtkMenuButton: Avoid direct button accessMatthias Clasen2015-06-151-8/+22
| | | | | | | | | We were getting ourselves in trouble by casting touch events to GdkEventButton and poking directly at their internals. Instead, use GdkEvent API to get what we need. This fixes a crash when using the gear menu in epiphany with touch. The same crash also occurred in testmenubutton.
* gtkoverlay: Fix issues with removeAlexander Larsson2015-06-151-3/+5
| | | | | The iteration now progresses past a delete, so make sure we iterate safely. Also, don't chain up if we removed a child.
* testoverlay: Fix indentationAlexander Larsson2015-06-151-5/+5
|
* testoverlay: Add test for overlay z orderingAlexander Larsson2015-06-151-0/+67
| | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=750568 https://bugs.freedesktop.org/show_bug.cgi?id=90917
* testoverlay: Fix test by using add_pass_through_overlayAlexander Larsson2015-06-151-1/+1
| | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=750568 https://bugs.freedesktop.org/show_bug.cgi?id=90917
* GtkOverlay: Add support for input pass-through overlaysAlexander Larsson2015-06-152-0/+73
| | | | | | | | | | For these widgets we set pass-through on the child window so that input over these widgets (that are not on a child input window) goes to the window below the overlay. https://bugzilla.gnome.org/show_bug.cgi?id=750568 https://bugs.freedesktop.org/show_bug.cgi?id=90917
* overlay: Add reorder_overlay()Alexander Larsson2015-06-152-1/+203
| | | | | | | | This allows you to control the z-ordering of overlay children https://bugzilla.gnome.org/show_bug.cgi?id=750568 https://bugs.freedesktop.org/show_bug.cgi?id=90917
* gdk: Add gdk_window_set_pass_throughAlexander Larsson2015-06-153-4/+128
| | | | | | | | | | | | | | | | | | | | | An pass_through window is something you can draw in but does not affect event handling. Normally if a window has with no event mask set for a particular event then input events in it go to its parent window (X11 semantics), whereas if pass_through is enabled the window below the window will get the event. The later mode is useful when the window is partially transparent. Note that an pass-through windows can have child windows that are not pass-through so they can still get events on some parts. Semantically, this behaves the same as an regular window with gdk_window_set_child_input_shapes() called on it (and re-called any time a child is changed), but its far more efficient and easy to use. This allows us to fix the testoverlay input stacking test. https://bugzilla.gnome.org/show_bug.cgi?id=750568 https://bugs.freedesktop.org/show_bug.cgi?id=90917
* testoverlay: Add new input stacking testAlexander Larsson2015-06-151-0/+53
| | | | | | | | | | | | | | In this case we have a bunch of interactive main children of the overlay, and then a centered overlay that contains both non-interactive (labels) and interactive (entry) widgets. This shows off a problem where the non-interactive parts (the labels) steals input from the overlay main children (breaks button click and hover effects). https://bugzilla.gnome.org/show_bug.cgi?id=750568 https://bugs.freedesktop.org/show_bug.cgi?id=90917
* Updated Spanish translationDaniel Mustieles2015-06-151-314/+329
|
* Updated Greek translationDimitris Spingos2015-06-152-1312/+1475
|
* stylecontext: Change fallback behavior on state mismatchBenjamin Otte2015-06-151-24/+36
| | | | | | | | | | | | | | | | | | | For functions that take state flags as an argument we need to special case the situation where the passed in flags don't match the current state. Previously we would create a copy of the style info, change its state and do the lookup from there. Now that GtkCssNode has replaced style infos, this doesn't work as well anymore as copying a GtkCssNode is not possible. However, unike style infos, GtkCssNodes are instant-apply, so we don't need to copy anymore, we can just change the state of the node. This causes some invalidations to be queued, but we can take that performance hit as this is fallback code. https://bugzilla.redhat.com/show_bug.cgi?id=1228852
* widget-factory: Make the circular button do somethingMatthias Clasen2015-06-142-1/+3
|
* testassistant: Remove padding from the filechooser pageMatthias Clasen2015-06-141-0/+1
| | | | | This tests the new assistant api to remove padding from pages.
* GtkAssistant: Add a way to have pages without paddingMatthias Clasen2015-06-143-1/+95
| | | | | | | This can be useful when embedding complex widgets like a file chooser as a page. https://bugzilla.gnome.org/show_bug.cgi?id=750631
* Add a filechooser-in-assistant exampleMatthias Clasen2015-06-141-0/+6
| | | | | This is one of the cases where one wants a page without any padding.
* GtkAssistant: Redo page marginsMatthias Clasen2015-06-141-5/+22
| | | | | | | Instead of having padding outside the notebook containing all pages, put each page in an extra box and add the padding there. This is in preparation for allowing pages without padding.
* assistant: Drop hardcoded paddingMatthias Clasen2015-06-141-3/+3
| | | | | | | This means the pages themselves will be responsible for setting suitable padding. https://bugzilla.gnome.org/show_bug.cgi?id=750631
* Fixes to Catalan translationJordi Mas2015-06-142-12/+12
|
* Only build testfontchooserdialog on linuxMatthias Clasen2015-06-131-1/+5
| | | | | | | | We are using this to test pango functionality that uses fontconfig apis, so this doesn't build on OS X or Windows anymore. https://bugzilla.gnome.org/show_bug.cgi?id=750892