summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* More hackslapo-overlayMatthias Clasen2014-11-041-3/+0
| | | | | | Somewhat mysteriously, the overlayed scrollbars don't work as scrollbars when faded in beforehand, so let Lapo wiggle his mouse to make them appear.
* Temporary hack to avoid fading overlay scrollbarsMatthias Clasen2014-10-271-1/+5
| | | | | | Temporarily allow disabling the fade out of overlay scrollbars by setting GTK_OVERLAY_SCROLLING_NO_FADE=1. This is meant to facilitate theming the overlay scrollbars.
* Updates for 3.15.1Matthias Clasen2014-10-272-1/+33
|
* gtk3-demo: Add a frame to the sidebarMatthias Clasen2014-10-271-24/+29
| | | | | With overlay scrollbars, there's no visible separation between the sidebar and the content otherwise.
* opengl: Use GL_TEXTURE_2D rather than GL_TEXTURE_RECTANGLE_ARB when possibleAlexander Larsson2014-10-272-46/+132
| | | | | This is more standard, and most driver support non-power-of-2 TEXTURE_2D these days. We fall back for ancient drivers.
* opengl: Use proper blend function for premultiplied alphaAlexander Larsson2014-10-271-1/+2
|
* gdkglcontext: Track whether to use GL_TEXTURE_2D or GL_TEXTURE_RECTANGL_ARBAlexander Larsson2014-10-273-0/+40
|
* cairoblur: Fix the blur again once moreJasper St. Pierre2014-10-271-5/+20
| | | | | | | | The differences between the mutter and GTK+ code are subtle, but it turns out that _gtk_cairo_blur_compute_pixels actually returns the shadow *spread*. Since we use a triple box blur, the constant was multiplied by 1.5 to approximate three chained box blurs. Split this out and use the correct value for the lobe width.
* cairoblur: Fix the blur codeJasper St. Pierre2014-10-271-2/+3
| | | | | | | | We weren't passing in the right "d" value, which was causing the blur to behave incorrectly, especially in the case of 1px blurs, which would cause no blurs at all. The blur should now match the web.
* Rename gdk_gl_context_flush_buffer to gdk_gl_context_end_frameAlexander Larsson2014-10-275-24/+24
| | | | This makes a lot more sense.
* Indentation fixMatthias Clasen2014-10-271-1/+1
|
* popover menus: Take iconic into accountSebastien Lafargue2014-10-271-25/+50
| | | | | | | | | | We don't want separators in both side of an iconic section and use a 10px margin to separate two iconic sections. Separators are also updated in case of dynamic insertion ( often used with menu items for plugins ) https://bugzilla.gnome.org/show_bug.cgi?id=738650
* Ignore gdk-pixbuf deprecationsMatthias Clasen2014-10-272-0/+6
|
* testlevelbar: fix CSS to be aligned with documentationCosimo Cecchi2014-10-271-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=707695
* levelbar: don't use the current value style class for empty blocksCosimo Cecchi2014-10-271-2/+15
| | | | | | | | We want to be able to style the empty blocks independently of all the offset styles, so remove the current style class when painting an empty block. https://bugzilla.gnome.org/show_bug.cgi?id=707695
* testlevelbar: don't segfault when quitting testlevelbarCosimo Cecchi2014-10-271-0/+12
| | | | | | Quit the mainloop when the window is closed. https://bugzilla.gnome.org/show_bug.cgi?id=707695
* quartz: Move the FullscreenSavedGeometry definition earlierMatthias Clasen2014-10-271-6/+6
| | | | | | | Move the FullscreenSavedGeometry before the first (conditional) use, to fix the build on OS X 10.6. https://bugzilla.gnome.org/show_bug.cgi?id=737561
* quartz: fix build on 10.6 and belowMarcus Karlsson2014-10-272-0/+7
| | | | | | | | | It is not possible to successfully build GTK+ on OS X 10.6 and below since NSFullScreenWindowMask is only available starting with 10.7. Add ifdef guards around setStyleMask: in order to allow it to build on earlier OS X releases. https://bugzilla.gnome.org/show_bug.cgi?id=737561
* Return correct font from gtk_font_chooser_widget_find_fontChristophe Fergeau2014-10-261-8/+10
| | | | | | | | | | | | | | | | Commit 30a1c4ab fixed several memleaks including one in gtk_font_chooser_widget_find_font. However, the fix causes one extra call to gtk_tree_model_iter_next() after finding the font we look for (ie pango_font_description_equal returns TRUE): the 'increment' part of the for loop (gtk_tree_model_iter_next) is run before the 'exit condition' of the for loop is evaluated. This commit reverts this part of commit 30a1c4ab and adds an extra call to pango_font_description_free in order to fix the leak. https://bugzilla.gnome.org/show_bug.cgi?id=739111
* fontchooserwidget: Don't invalidate priv->font_iter in load_fontsChristophe Fergeau2014-10-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When using GtkFontChooserButton, the same GtkFontChooserWidget can be hidden and shown multiple times. When doing that, the font that was chosen the previous time should be the selected one in the GtkFontChooserWidget, however this does not work as expected and a somehow 'random' font gets selected (or none) instead. Every time the font chooser widget is shown, its style will be updated, causing gtk_font_chooser_widget_style_updated and then gtk_font_chooser_widget_load_fonts to be called. gtk_font_chooser_widget_load_fonts starts by clearing the GtkListStore listing the available fonts, repopulates it, and then makes sure the current font is selected. However, this does not work as expected, as during the call to gtk_list_store_clear, the cursor_changed_cb will be invoked multiple times when the GtkTreeView cursor gets moved when the line where the cursor currently is gets removed. This will cause the 'current font' state (priv->font_desc) to be unexpectedly modified, and when gtk_font_chooser_widget_load_fonts tries to reposition the cursor to the 'current font', we won't get the expect result. This commit avoids that by making sure cursor_changed_cb does not get called when we call gtk_list_store_clear in gtk_font_chooser_widget_load_fonts. https://bugzilla.gnome.org/show_bug.cgi?id=739111
* Fix an out-of-bounds access in MyEnhancedXkbTranslateKeyCodeMatthias Clasen2014-10-261-4/+5
| | | | | | | | | | | Commits 314b6abbe8d8daae and eb9223c008ccf1c2faab were ignoring the fact that the code where found is set to 1 was modifying col - which was an ok thing to do when that part of the code was still breaking out of the loop, but it is no longer doing that (since 2003 !). Fix things up by storing the final col value in a separate variable and using that after the loop. https://bugzilla.gnome.org/show_bug.cgi?id=738886
* Test h/vhomogenenous in teststackMatthias Clasen2014-10-261-4/+17
| | | | Add separate checkboxes for hhomogeneous and vhomogeneous.
* Use GtkStack:vhomogeneous for popover menusMatthias Clasen2014-10-262-13/+1
| | | | This allows us to get rid of a size group.
* GtkStack: split homogeneousMatthias Clasen2014-10-263-18/+195
| | | | | Split homogeneous into separate hhomogeneous and vhomogeneous properties. vhomogeneous is what we want for popover menus.
* popover: Use the right area for drawing the backgroundTimm Bäder2014-10-261-3/+3
| | | | The border shouldn't be subtracted.
* GtkBox: Fix self-assignment for center widgetMatthias Clasen2014-10-251-0/+5
| | | | | This is happening when glade is loading ui files containing center widgets.
* Updated Czech translationMarek Černocký2014-10-261-476/+571
|
* Updated Czech translationMarek Černocký2014-10-261-424/+731
|
* GtkPlacesSidebar: Don't crash on dndMatthias Clasen2014-10-251-4/+6
| | | | | | gtk_get_current_event() can return NULL. Don't crash if it does. https://bugzilla.gnome.org/show_bug.cgi?id=739150
* Revert "Inspector backend hack"Matthias Clasen2014-10-251-6/+0
| | | | | | This reverts commit f88a5dc8c78e6530baeebb6cba75fe3061926052. Didn't mean to push this.
* GtkSpinButton: Set the screen on the panel contextsMatthias Clasen2014-10-251-1/+2
| | | | | | | Failure to do so results in custom styling leaking through in the inspector. This is pretty obvious, now that the inspector is using a separate display connection and is generally isolated from style changes.
* Inspector backend hackMatthias Clasen2014-10-251-0/+6
|
* Broadway: Remove display assumptionsMatthias Clasen2014-10-253-5/+47
| | | | | | | | | In various places, the broadway backend was just using the default display and assumed that it is the broadway display. That may not be the case in a multi-backend world, so instead iterate over all displays and use the first broadway display - still not perfect, but enough to survive for now.
* inspector: Plug a memory leakMatthias Clasen2014-10-251-0/+3
|
* inspector: Add style classes to the object listMatthias Clasen2014-10-253-12/+28
| | | | | We have a lot of space here now, so show some useful information.
* Fix a mixup in popover realizationMatthias Clasen2014-10-241-1/+1
| | | | | | | When the window is on a non-default screen, popover_realize ended up passing a visual and a parent_window from different screens into gdk_window_new, which doesn't work. Fix it by using the visual of the parent window.
* inspector: Improve details buttonsMatthias Clasen2014-10-246-3/+41
| | | | | Ensure that the details buttons are only sensitive when we actually have details to show.
* inspector: Improve tab switchingMatthias Clasen2014-10-2410-60/+188
| | | | | Switch the object and resource trees away from activate-on-single-click and add a 'view details' button.
* X11: Don't assume all displays are X11 displaysMatthias Clasen2014-10-242-3/+8
| | | | | | When iterating over the list of displays gotten from the display manager, we have to check if what we got is actually an X11 display.
* Properly update the style cascade on screen changeMatthias Clasen2014-10-241-1/+3
| | | | | | | GtkStyleContext was not properly handling the style cascade when setting a screen, causing the inspector global CSS to affect the inspector window, even though the inspector is using a different screen now.
* Fix the buildMatthias Clasen2014-10-243-3/+3
| | | | Some forgotten include path adjustments.
* inspector: Use a separate display connectionMatthias Clasen2014-10-246-14/+73
| | | | | | | | This helps isolate the inspector from some of the changes that it can trigger. To specify a different display, set GTK_INSPECTOR_DISPLAY to the name of the display to use for the inspector window. If no display is specified, GTK+ will use a separate connection to the default display.
* Fix a problem with screen changes and csdMatthias Clasen2014-10-241-0/+16
| | | | | | | | | | | | When a new screen is set on a window, we unrealize it, to recreate all the resources. But we don't reset the client_decorated flag, so realize() doesn't call create_decoration() - which makes sense, since the decoration already exists. But the side-effect of create_decoration() is to select the rgba visual, and visuals are per-screen. Fix this by looking for the rgba visual in set_screen(), and replacing it with the rgba visual for the new screen, if necessary.
* styleproperties: Move into deprecated directoryBenjamin Otte2014-10-249-8/+8
|
* styleproperties: DeprecateBenjamin Otte2014-10-244-29/+45
|
* styleproperties: Remove header where it's not usedBenjamin Otte2014-10-247-7/+1
|
* styleproperties: Remove unused functionBenjamin Otte2014-10-242-25/+7
|
* css: Disallow bypassing value computationBenjamin Otte2014-10-245-87/+25
| | | | | | | | This special code was added back in the days when computation wasn't idemptotent. These days it is. Also, the bypass code path is only used in fallback code that is pretty much unused.
* css: Remove unneeded headerBenjamin Otte2014-10-241-1/+0
|
* Updated Spanish translationDaniel Mustieles2014-10-241-131/+43
|
View Lorry Controller Status