| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
As pointed out in bug 754143, this reveals a crash in the Wayland
backend.
|
| |
|
| |
|
|
|
|
| |
Thats a more typical affirmative action in save mode.
|
|
|
|
|
| |
The display is getting overwritten immediately. Pointed out by
coverity.
|
|
|
|
|
| |
Coverity complained about us ignoring the return value
here, and it is nicer to get an error message about this.
|
|
|
|
|
|
|
|
| |
We need to check on realize if we have access to a GL context, before
calling GL functions. We use gtk_gl_area_get_error() for that.
We also need to tear down the resources during unrealization, instead
of leaking them.
|
|
|
|
|
| |
The GtkPlacesView widget was made private, so we can't create it in a
testcase.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Places sidebar shows XDG directories, mounted and unmounted devices,
connected networks, bookmarks and actions like 'Connect to server'
and 'Insert location', which causes the sidebar to grow very quickly
and look cluttered. Because of that, new mockups for the sidebar try
to simplify it.
To make the sidebar simpler, the new mockups propose that it should
only handle connected networks and removable devices such as flash
drives and USB devices, and delegates other devices for external
widgets through the 'Other Locations' item.
To handle fixed devices and manage network connections, add a new
widget named GtkPlacesView, based on Nautilus mockups to keep
consistency between GNOME file management tools - in this case,
between Nautilus and the bundled Gtk's file chooser.
https://bugzilla.gnome.org/show_bug.cgi?id=752034
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The menu tracker does a better job of this than we can, so move over to
using it instead.
This fixes issues with './testgmenu --import' not properly displaying
the language submenu.
https://bugzilla.gnome.org/show_bug.cgi?id=752016
|
|
|
|
| |
This allows for easier testing of !local-only mode.
|
|
|
|
| |
It makes testing the intended user experience harder.
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=750568
https://bugs.freedesktop.org/show_bug.cgi?id=90917
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=750568
https://bugs.freedesktop.org/show_bug.cgi?id=90917
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
This tests the new assistant api to remove padding from
pages.
|
|
|
|
|
| |
This is one of the cases where one wants a page without
any padding.
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
This shows a minimal setup for enabling non-row DND from a treeview.
|
| |
|
|
|
|
|
|
|
| |
This lets applications show their own fonts instead of
or in addition to system fonts.
https://bugzilla.gnome.org/show_bug.cgi?id=748771
|
|
|
|
|
| |
Instead of hardcoding 64, ask the display about the
maximal supported cursor size.
|
|
|
|
|
|
| |
It is not ideal when the default filter filters away
all files, so change things to select the 'all files'
filter by default.
|
|
|
|
|
| |
Arrange for the entry and the cursor area to both start out
with the arrow cursor.
|
|
|
|
|
|
| |
Use cursor names instead of font cursors, so we can also show
cursors that are not represented in the X cursor font and thus
don't have a value in the GdkCursorType enumeration.
|
|
|
|
|
| |
We were connecting to the wrong signal, so we were not picking
up all changes to the spin button value.
|
| |
|
|
|
|
|
|
|
|
| |
There is no need to e.g. blur in the x-direction for the top part
of a box shadow. Also, there is no need to extend the mask in the
non-blurred direction.
https://bugzilla.gnome.org/show_bug.cgi?id=746468
|
|
|
|
|
|
|
| |
This just creates a large cairo surface and times bluring it
at various values of radius.
https://bugzilla.gnome.org/show_bug.cgi?id=746468
|
|
|
|
|
|
|
|
|
| |
This is somewhat tricky to work out, so put some example
code here for future reference. The tricky part is that
GtkAccelLabel tries to be smart about hiding the accel
if there's not enough space, so we have to make sure to
pack the label with expand=TRUE and set align=GTK_ALIGN_FILL,
or things won't work.
|
|
|
|
|
|
|
|
| |
Make sure that variables are declared at the top of the block.
Break up one of the sincos() calls into individual calls to sin() and cos()
so that we do not have to complicate the initialization of the following
GLfloat array.
|
|
|
|
|
|
| |
It apparently doesn't exist everywhere.
https://bugzilla.gnome.org/show_bug.cgi?id=745578
|
|
|
|
|
|
| |
Instead of using glxgears, which still uses OpenGL 2.1 and the fixed
pipeline, we use a slightly modified es2gears, OpenGL 3.2, and the
programmable pipeline.
|
|
|
|
|
|
| |
GtkSidebar is too generic and doesn't fully convey what the widget does.
https://bugzilla.gnome.org/show_bug.cgi?id=744094
|
|
|
|
|
|
|
|
| |
Since we dropped the legacy OpenGL compatibility profile, we need to use
recent OpenGL APi and concepts. This also means that the example code
gets a tad more complicated.
https://bugzilla.gnome.org/show_bug.cgi?id=741946
|
|
|
|
|
|
|
|
| |
This will be used to just detect when an edge of the scrollable area is
reached - as opposed to the edge-overshot signal that is emitted when
the user scrolls past the edge.
https://bugzilla.gnome.org/show_bug.cgi?id=742848
|
|
|
|
|
|
|
|
|
|
|
|
| |
The code here was always a bit buggy: We removed the tab from
the notebook in a ::drag-data-received handler. But with
GTK_DEST_DEFAULT_DROP, that signal is emitted before we inform
the source side that the drag is finished. With its improved drag
handling, GtkNotebook now interprets this as a 'spontaneous'
removal of the tab being dragged, and cancels the drag, leading
to an unwanted cancel animation.
The easiest fix is to just defer the tab removal to an idle.
|
|
|
|
|
|
| |
When changing between months, we can get into a situation like
'February 30", which GDate doesn't accept. Don't crash in that
case.
|
|
|
|
| |
Pointed out in https://bugzilla.gnome.org/show_bug.cgi?id=741252
|
|
|
|
|
|
|
| |
Use G_PI in place of M_PI to fix the build on compilers that do not have
M_PI defined.
https://bugzilla.gnome.org/show_bug.cgi?id=740795
|
|
|
|
|
| |
It's the last test still spewing these and I'm too lazy to do a proper
fix.
|
|
|
|
| |
Demonsttrate that this is flexible enough for the intended uses.
|
|
|
|
|
| |
Add the required boxes for each submenu. We now need to specify the
submenu name only once per submenu.
|
|
|
|
| |
Drop all all explicit role setting from the testpopover example.
|
| |
|