summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 2.18.22.18.2Matthias Clasen2009-10-05203-4211/+4219
|
* UpdatesMatthias Clasen2009-10-051-0/+17
|
* Don't request window sizes with zero width or heightAlexander Larsson2009-10-051-0/+7
| | | | | | | | | | | | | | | | | | Zero width/height is unsupported and will magically be turned into one. For instance, gtk_widget_size_allocate() will eventually do this magic on the value stored in widget->allocation. However, if we don't do this magic conversion early, then the value returned from gtk_window_compute_configure_request() will not be comparable with whats stored in widget->allocation. (I.E. they will differ if width or height are zero). This is dangerous, as we do such a comparison in gtk_window_move_resize(). Currently a change from e.g. 10x1 (current allocation) to 10x0 (new size) will be expected to produce a ConfigureNotify, when it actually won't, thus never thawing the frozen toplevel. Fixes bug #588059
* Fix up _gdk_windowing_window_at_pointer coordinate reportingAlexander Larsson2009-10-051-8/+11
| | | | | | | | | We need to do a final XQueryWindow to get the coordinates inside the windows rather than in the parent window. This fixes bug #597386, "Cannot click buttons more than once...", which failed due to the grab tracking stuff getting the wrong coordinates as per the above.
* Plug a memory leakMatthias Clasen2009-10-041-0/+2
| | | | Valgrind reported a leak of regions from gdk_window_process_updates_internal.
* Updated Japanese translationTakayuki KUSANO2009-10-031-20/+18
|
* Updated Italian translationLuca Ferretti2009-10-031-1118/+1106
|
* Bug 596959 - DirectFB backend compilation broken with changes from 2.18.0 ↵Sebastian Dröge2009-10-021-2/+4
| | | | | | to 2.18.1 Fix compilation of the DirectFB backend after internal API changes of GDK.
* Call XReconfigureWMWindow with proper screenPascal Terjan2009-10-011-1/+1
| | | | | | | | | | | Thanks gcc : gdkwindow-x11.c:1731: warning: passing argument 3 of 'XReconfigureWMWindow' makes integer from pointer without a cast /usr/include/X11/Xlib.h:1871: note: expected 'int' but argument is of type 'struct GdkScreen *' Signed-off-by: Pascal Terjan <pterjan@mandriva.com>
* Move SIGPIPE suppression to gtk_init and document itMatthias Clasen2009-10-013-2/+16
| | | | | | Some people were unhappy with doing it deep inside the lpr print backend at an unpredictable time, and SIGPIPE is almost never wanted anyway.
* Updated Serbian translationMiloš Popović2009-10-012-2264/+2259
|
* Bump versionMatthias Clasen2009-09-301-2/+2
|
* 2.18.12.18.1Matthias Clasen2009-09-30202-26871/+30924
|
* UpdatesMatthias Clasen2009-09-301-2/+46
|
* Updated Czech translationPetr Kovar2009-09-301-1091/+1125
|
* Correct the orientation of landscape pagesAdrian Johnson2009-09-301-8/+8
| | | | | | The convention for landscape pages, and required by PostScript Language Reference Manual, is for landscape printing to rotate user space 90 degrees counterclockwise. Part of bug 596423
* Emit PageOrientation DSC comment into PostScript print outputAdrian Johnson2009-09-301-2/+19
| | | | | The PageOrientation DSC comment tells PostScript viewers such as gv or evince the orientation to use when displaying the page. Part of bug 596423
* Speed up printer listing in the print dialogMarek Kasik2009-09-303-8/+45
| | | | | Use shorter timeout for connection testing to avoid A 3-6 second delay before the printers appear. Bug 594643
* Updated Hungarian translationGabor Kelemen2009-09-301-87/+108
|
* Bug 588449 - DnD doesn't work on GDK/QuartzKristian Rietveld2009-09-303-38/+132
| | | | | Patch from Paul Davis. This gets the basics of drag and drop properly working on Mac OS X.
* Add a note about tooltip themingChristian Dywan2009-09-301-0/+3
| | | | | This should help to reduce the amount of confusion about how to make a tooltip window appear like a tooltip. Bug 596080.
* Fix compile warning in defaultvalue testKristian Rietveld2009-09-301-2/+2
|
* Ignore certain GtkSettings in defaultvalues unit testKristian Rietveld2009-09-301-1/+4
| | | | | | Like the other GtkSettings already registered, these are influenced from the outside and cannot be properly tested. The defaultvalues test passes again now.
* Use boxed accessors for setting and retrieving cursor propertyKristian Rietveld2009-09-301-2/+2
|
* Bug 596580 - Blank rows in entry autocompletionKristian Rietveld2009-09-302-21/+261
| | | | | | | | | | | | | | | | | | | | | gtk_tree_model_build_level() always needs to emit row-inserted when requested, this should not depend on whether the level has a parent level or a virtual root, which is a check whether or not we need to reference the node in the child model. Furthermore, we also need to emit row-has-child-toggled after row-inserted when appropriate. When gtk_tree_model_filter_row_changed() pulls in the root level, it must request build_level() to emit signals for this. The refilter function uses row_changed to process the changes, so build_level() in the first call to row_changed() might pull in multiple new nodes in this scenario, for all of these signals need to be emitted. Of course, build_level() will then also emit the signals for the node row_changed() is processing, we should not emit a duplicate signal, this is now accounted for. Add a unit test for this. For this small functionality to block the row-changed signal has been implemented, so that we can simulate calls to the refilter function using the current visible column setup.
* Pretty print non-matching signals in filter model test suiteKristian Rietveld2009-09-301-6/+58
|
* Updated Swedish translationDaniel Nylander2009-09-301-87/+108
|
* Interpret min_value == max_value correctlyThomas Jaeger2009-09-301-5/+22
| | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=588649 Signed-off-by: Thomas Jaeger <ThJaeger@gmail.com>
* Select for DeviceStateNotifyThomas Jaeger2009-09-302-1/+22
| | | | | | Signed-off-by: Thomas Jaeger <ThJaeger@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=588649
* Keep track of axis valuesThomas Jaeger2009-09-303-2/+26
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=588649
* Support tracker 0.7Jürg Billeter2009-09-301-28/+67
| | | | | Make GtkSearchEngineTracker work with libtracker 0.6 and 0.7. See bug 596081.
* Update last_window only when neededXan Lopez2009-09-291-0/+3
| | | | | | | | _gtk_tooltip_handle_event, which is called for many events in the GTK+ main loop, calls gtk_tooltip_set_last_window, which keeps a weak reference to the last window we passed through. If the window being set is the same than the last one there's really no need to update our weak reference, so add a check for that and exit early.
* Filter out events that the current window didn't select forThomas Jaeger2009-09-293-1/+53
| | | | | | Signed-off-by: Thomas Jaeger <ThJaeger@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=588649
* Always select all XInput motion eventsThomas Jaeger2009-09-291-40/+4
| | | | | | Signed-off-by: Thomas Jaeger <ThJaeger@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=588649
* Report XInput button motion events until all buttons are released.Thomas Jaeger2009-09-291-1/+1
| | | | | | Signed-off-by: Thomas Jaeger <ThJaeger@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=588649
* XInput allows up to 255 buttonsThomas Jaeger2009-09-293-6/+18
| | | | | | Signed-off-by: Thomas Jaeger <ThJaeger@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=588649
* Refactor _gdk_input_other_eventThomas Jaeger2009-09-291-6/+6
| | | | | | Signed-off-by: Thomas Jaeger <ThJaeger@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=588649
* Use strstr instead of g_strrstr.Thomas Jaeger2009-09-291-4/+4
| | | | Signed-off-by: Thomas Jaeger <ThJaeger@gmail.com>
* Only select for button and pointer event on toplevelsAlexander Larsson2009-09-291-17/+36
| | | | | | | These event types propagate up the hierarchy anyway, so this means we avoid setting it unnecessarily. This is especially important for button press event, since only one client can select for this on each window, causing X errors if two clients do it.
* Updated French translationClaude Paroz2009-09-291-87/+109
|
* Updating corrected Assamese translations.Amitakhya Phukan2009-09-291-54/+43
|
* Always initialize out paramsMatthias Clasen2009-09-281-7/+7
| | | | | This was causing a crash in the appearance capplet, reported in bug 596345.
* Improve detection of input device source typeThomas Jaeger2009-09-281-8/+6
| | | | | | | | | | This detection code is not 100% reliable, but it should fare much better than the current code, which just compares the device name to a fixed set of strings. Many applications depend on erasers being recognized reliably, so we start by checking for a device name containing the substring 'eraser'. Signed-off-by: Thomas Jaeger <ThJaeger@gmail.com>
* Sent button events don't cause passive grabsAlexander Larsson2009-09-281-2/+6
| | | | | Don't track sent button events as causing or removing passive grabs.
* Remove unused grab_one_pointer_release_event varAlexander Larsson2009-09-282-4/+1
| | | | We don't use this anymore, so just remove.
* Extend _gdk_windowing_window_at_pointer to be able to get toplevels onlyAlexander Larsson2009-09-286-21/+64
| | | | | | | | | | | | | This has two advantages: 1) In many backends, this is faster as we can terminate the window hierarchy traversal earlier 2) When used in gdkdisplay.c::get_current_toplevel() to get the current toplevel that has the pointer we now correctly return a toplevel with the pointer in it where the pointer is inside some foreign subwindow of a toplevel window. The second advantage fixes some bugs in client side event generation when the pointer is inside such a foreign child window.
* Bug 596494 - New property "cursor" in 2.18's GdkWindow with wrong type?Cody Russell2009-09-271-4/+5
| | | | Use a boxed paramspec with GDK_TYPE_CURSOR instead of a pointer paramspec.
* Remove unused variableKristian Rietveld2009-09-271-1/+0
|
* Bug 596012 - popup menu position is horribly off on gdk quartz with ...Kristian Rietveld2009-09-272-3/+40
| | | | | | | | | | | | | | Based on first patches by Christian Hergert. Change screen_get_monitor_geometry() so that it translates the layout of the screens from Cocoa layout to GDK layout. In Cocoa, the screen locations are specified in Cocoa geometry, as well as that GDK uses a different way to place individual monitors in the root window. For now only monitors that are laid out horizontally are supported (see the FIXMEs in the source), in bug 596238 we will track future work to get things fully right. Modify _gdk_quartz_window_get_inverted_screen_y() to take the differences in screen layout between Cocoa and GDK into account. Also this function is subject to future work.
* Handle child widgets correctly with multiple viewsMatthias Clasen2009-09-271-30/+33
| | | | This was broken by an RTL fix in April.
View Lorry Controller Status