summaryrefslogtreecommitdiff
path: root/gtk
Commit message (Collapse)AuthorAgeFilesLines
* Formatting fixesMatthias Clasen2014-12-231-45/+19
|
* GtkRecentManager: Formatting fixesMatthias Clasen2014-12-231-358/+365
|
* window: Use subsurfaces for popovers on waylandCarlos Garnacho2014-12-232-5/+51
| | | | | | | | | On the wayland backend, set up GDK_WINDOW_SUBSURFACE windows for popovers. In the popover code, the popover-relative-to-parent calculation had to be tweaked, and it's been made to always prefer the given popover position, since there's no sizing limitations. https://bugzilla.gnome.org/show_bug.cgi?id=738891
* GtkApplicationWindow: Documentation fixPatrick Welche2014-12-231-3/+3
| | | | | | gtk_builder_add_from_string takes more than 2 parameters. https://bugzilla.gnome.org/show_bug.cgi?id=741897
* Adwaita: Special-case server-side window decorationsFlorian Müllner2014-12-223-0/+8
| | | | | The WM already adds the window shadow in that case, so just use the box-shadow to add the border here.
* GtkNotebook: Be a bit more safe against cur_page being NULLMatthias Clasen2014-12-221-4/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=477454
* GtkRecentManager: Survive without a filenameMatthias Clasen2014-12-221-68/+69
| | | | | | | | | | We were asserting priv->filename != NULL in various places, which leads to apps refusing to work when HOME is set to a nonexisting or nonwritable value. Since it isn't hard, just make GtkRecentManager survive without a filename. We won't save or read any recently used files in this state, but thats ok. https://bugzilla.gnome.org/show_bug.cgi?id=739038
* GtkMenuTracker: add hidden-when='macos-menubar'Ryan Lortie2014-12-227-9/+29
| | | | | | | | | | | | | | | | Provide a mechanism for hiding the "Quit", "About" and "Preferences" menu items from the normal places in a traditional menubar layout (in the File and Edit menus) when the menu is being rendered in the Mac OS menubar. These items can already be found in the application menu. With this feature, applications can now define a single menu to use in all 'traditional' scenarios. Use this new attribute in Bloatpad. https://bugzilla.gnome.org/show_bug.cgi?id=741610
* GtkRecentManager: Allow instantiating with gtk_initMatthias Clasen2014-12-211-8/+16
| | | | | | This apparently used to work, and it doesn't do harm to allow it. https://bugzilla.gnome.org/show_bug.cgi?id=705582
* Some formatting cleanupsMatthias Clasen2014-12-211-8/+8
|
* GtkMenuTracker: add missing documentation fragmentRyan Lortie2014-12-201-0/+3
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=741610
* inspector: Remove an errant shadowMatthias Clasen2014-12-201-1/+0
|
* inspector: Add a magnifierMatthias Clasen2014-12-209-1/+155
| | | | | Add a magnifier that shows the selected widget up to 5 times enlarged.
* GtkTextView: disconnect the magifier on destroyMatthias Clasen2014-12-201-0/+3
| | | | | This prevents warnings that would otherwise happen when the magifier is finalized.
* GtkMagnifier: Add a resizing modeMatthias Clasen2014-12-202-1/+197
| | | | | | | | | In addition to the fixed-size mode that is used by the text view, add a mode in which the magnifier requests enough size to render the entire inspected widget at the current magnification. In this mode, the magnifier will update its size when the size of the inspected widget changes. Also, make the magnifier redraw on its own whenever the inspected widget draws.
* widget: Set the allocation via gtk_widget_set_allocation()Benjamin Otte2014-12-201-1/+1
| | | | | | | | There is no good reason to assign the value directly. Also, this fixes d23f3254b7fcef0fc57739ce5cd548742870b119 where widgets that chained up instead of calling gtk_widget_set_allocation() would not draw becaues of empty clip.
* csstransform: Fix comparisons crashingBenjamin Otte2014-12-191-0/+3
| | | | Transforms of different type are not equal.
* widget: Handle setting clip differentlyBenjamin Otte2014-12-191-45/+10
| | | | | | | | | | | | | | | | | | | (1) Get rid of supports_clip flag. All widgets (implicitly) support clip. (2) Don't reset the clip to { 0, 0, 0, 0 } before the "size-allocate" signal. (3) Make gtk_widget_set_allocation() set the clip (to the allocation). This ensures that eveyr widget has a clip set. Note: It overrides previous calls to gtk_widget_set_clip(), while in 3.14 this didn't happen. (4) As the clip is set by gtk_widget_set_allocation() now, don't set it after the "size-allocate" signal anymore. This fixes calls to gtk_widget_queue_draw() from inside the size_allocate vfunc.
* GtkApplication: Try to cope with ssh situations betterMatthias Clasen2014-12-181-5/+54
| | | | | | | | | | | | | | | | Override the gtk-shell-shows-app-menu and gtk-shell-shows-menubar settings to FALSE, if we can detect that we are not on the same session bus as the xsettings provider that we got these settings from. We determine this by comparing the bus ID of 'our' session bus with the one reported in the Gtk/SessionBusId xsetting. If they are different, then it very likely that we are in an ssh situation where we see the forwarded X display, but not the session bus. The D-Bus based menu exporting will not work in this situation. https://bugzilla.gnome.org/show_bug.cgi?id=671802
* textview: make magnifier size dependent on text sizeCarlos Garnacho2014-12-181-9/+21
| | | | | | The magnifier is now set enough height to show the line being currently manipulated, which makes it just big enough to show the layout height at that size and magnification.
* Adwaita: Make text handles a bit largerCarlos Garnacho2014-12-183-0/+7
| | | | | This improves visibility, and interaction, as the invisible rect around is dependent on the visible handle size
* textview: Implement friendlier touch selectionCarlos Garnacho2014-12-181-31/+64
| | | | | | | | | | - It is not possible anymore to trigger text DnD through touch, pressing and dragging from within the selection will instead extend it. Text shrinking is still available through the handles - The selection mode for touch is per-word, char-level manipulation is still available through the handles. - Tapping within the selection will bring in text handles, and toggle text selection popover.
* textview: Make "extend selection" only extendCarlos Garnacho2014-12-181-8/+12
| | | | | | | | | | This mode could also shrink the selection, plus the starting point would seem somewhat arbitrary (actually dependent on the dragging direction of the last selection). Made this mode more consistent by only allowing it to extend the selection, only in one direction for each operation, and so it keeps the current selection as a minimum.
* textview: Pass a boolean telling whether a selection drag should extendCarlos Garnacho2014-12-181-13/+15
| | | | | | Instead of passing a GdkEvent and let the function figure out whether the selection should be extended, let that to the caller and just pass a boolean here.
* textview: Show magnifier on top of current lineCarlos Garnacho2014-12-181-14/+18
| | | | The X coordinate is dependent on touch position, but Y is stepped.
* texthandle: Use active state when handles are being draggedCarlos Garnacho2014-12-181-0/+21
| | | | The active state flags is set on both handles when this happens.
* texthandle: Use the handle widget style context for renderingCarlos Garnacho2014-12-181-1/+10
| | | | | | | Using the parent widget context is a leftover of the pre-popover implementation, which used GdkWindows directly. This will make the context reflect widget state, at the expense of changing the selector paths that used to match the handles.
* gesturesingle: check for the sequence being handled, not just the eventCarlos Garnacho2014-12-181-1/+2
| | | | | | | | | | | | Checking the return value was valid for most gestures, but GtkGestureLongPress, where the first press triggers internally an action, but does nothing for the sequence to be claimed/denied, FALSE was eventually returned, and the button/sequence functions would be incorrect when ::pressed is emitted. So check that the sequence is being handled by the gesture, this is more desirable than the return value as it's independent of sequence state, and still will be FALSE for the cases we want to catch here.
* gtktextlayout: fix to quiet a warningSebastien Lafargue2014-12-181-1/+1
| | | | | | | Gcc complains about a possible use of a not initialised widget ref ( which can't happen in reality ) https://bugzilla.gnome.org/show_bug.cgi?id=741702
* gtktextlayout: fix for right margin with RTL textSebastien Lafargue2014-12-181-2/+4
| | | | | | | | | When a RTL paragraph is not set to wrap, the right margin is not respected because of the margins counted twice so we replace display->width by PIXEL_BOUND (extents.width), the same quantity without the margins. https://bugzilla.gnome.org/show_bug.cgi?id=741702
* Minor documentation fixErick Pérez Castellanos2014-12-181-1/+1
|
* printing: Translate context to correct positionMarek Kasik2014-12-181-5/+23
| | | | | | | Use correct margins of given page setup when translating context to imageable area. https://bugzilla.gnome.org/show_bug.cgi?id=671895
* printing: Return correct width and height of page setupMarek Kasik2014-12-181-6/+14
| | | | | | | | Use correct margins when computing width and height returned by gtk_page_setup_get_page_width() and gtk_page_setup_get_page_height(). https://bugzilla.gnome.org/show_bug.cgi?id=671895
* GtkMenuButton: Don't leak popoversMatthias Clasen2014-12-171-0/+2
| | | | | | | Detach the previous popover from the toplevel when a new one is set. This should fix https://bugzilla.gnome.org/show_bug.cgi?id=741652
* Adwaita: another stab at the undershootLapo Calamandrei2014-12-174-210/+250
|
* Adwaita: fix treeview progressbar issueLapo Calamandrei2014-12-173-482/+637
| | | | See https://bugzilla.gnome.org/show_bug.cgi?id=741569
* Menu items: force loading 16x16 iconsLars Uebernickel2014-12-172-0/+2
| | | | | | | | | | | GtkIconTheme doesn't scale icons beyond the size specified in the theme anymore. This can result in arbitrarily large menu items when a theme only provides large icons. Force icons to always be 16x16 to ensure that menu items always have the same height. https://bugzilla.gnome.org/show_bug.cgi?id=741259
* textview: add extend-selection signalSébastien Wilmet2014-12-172-26/+133
| | | | | | | To be able to customize the double-click and triple-click behaviors, to provide custom selection boundaries. https://bugzilla.gnome.org/show_bug.cgi?id=111503
* menubutton: Fix double freeze_notifyTimm Bäder2014-12-161-2/+2
|
* GtkGLArea: Handle window scale factor changesAlexander Larsson2014-12-161-0/+17
| | | | We need to re-allocate the buffers for the new gl size.
* GtkGLArea: Only re-allocate buffers during paintAlexander Larsson2014-12-161-40/+55
| | | | | | | | | | | | | This drops the maybe_allocate_buffers that re-allocates buffers at any point. Instead we just set have_buffers to FALSE and have the buffers re-created when needed. This also makes the buffer creation code imdeponent and makes it clean up no longer needed buffers in order to handle being called multiple times due to the above. We also ensure we re-allocate the buffers when we're resizing and the buffers are already created.
* GtkMenuTracker: one more visibility tweakRyan Lortie2014-12-141-2/+1
| | | | | | | | | | | | | | | On creation, we call action_removed() in case the action was missing from the start. Because we just created the action, 'can_activate' will always be FALSE here and this function will therefore always do nothing. We do want the visibility state to be updated though, for the case where the action is missing but the item should still be visible from the start. Update the visibility directly instead of trying to call action_removed(). https://bugzilla.gnome.org/show_bug.cgi?id=735122
* GtkMenuTrackerItem: fix submenu visibility flagRyan Lortie2014-12-141-1/+4
| | | | | | | | | | | | | | | | | We were only properly setting the "is-visible" flag to TRUE for menu items with associated actions and not (for example) on submenus. This was fine because the code for building GtkMenus from models (correctly) assumed that submenus should always be visible and never checked the property. This is not true for the Mac OS code, which actually checked the property and found it to be false for submenus. Initialise the property to TRUE so that we get the correct value reported for items that don't have actions. https://bugzilla.gnome.org/show_bug.cgi?id=735122
* quartz menu: update visibility property nameRyan Lortie2014-12-141-1/+1
| | | | | | This property is called "is-visible" now, not "visible". https://bugzilla.gnome.org/show_bug.cgi?id=735122
* popover: Clamp tail gap limits by the tail height on that sideCarlos Garnacho2014-12-131-8/+8
| | | | | | | | | All popover sides have extra margins to possibly hold the tail, this is accounted for in gtk_popover_get_rect_coords(), and should be accounted for too in the tail position calculation. This fixes the gtk_render_frame_gap() warnings seen when a popover is pushed far too close to window sides.
* popover: Ensure there is a child before focusing itCarlos Garnacho2014-12-131-2/+6
| | | | Fixes a warning in empty popovers being shown.
* inspector: Fix capitalizationMatthias Clasen2014-12-122-2/+2
|
* inspector: Add a cursor theme controlMatthias Clasen2014-12-123-2/+185
|
* Adwaita: Fix sidebar undershootMatthias Clasen2014-12-123-287/+135
| | | | | The undershoot rendering in the gtk-demo sidebar was inheriting unwanted background. Prevent that.
* stylecontext: Make sure we always clear the cache when the CSS changesBenjamin Otte2014-12-131-0/+2
| | | | | | | | After b49c7c34214da2d8d5e6dae2e8d0b0fe1b23f68e we were no longer doing a full revalidate after GTK_CSS_CHANGE_SOURCE changes. This fixes spurious failures of widgets not properly updating when changing the theme.
View Lorry Controller Status