summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Add items to the shortcuts bar's popup menu to configure the startup ↵bgo658280-filechooser-recently-used-2-24Federico Mena Quintero2012-12-032-61/+0
| | | | | | | | | mode" Per the gtk-devel meeting on 2012/11/29, we'll not have a UI in the file chooser dialog to select between those modes. Instead, we'll show that key in gtweaktool. This reverts commit 7860500bc69da242992705995c32940ad84e066c.
* Add items to the shortcuts bar's popup menu to configure the startup modeFederico Mena Quintero2012-11-262-0/+61
| | | | Signed-off-by: Federico Mena Quintero <federico@gnome.org>
* Switch to Recent Files or $CWD at startupFederico Mena Quintero2012-11-261-3/+40
| | | | Signed-off-by: Federico Mena Quintero <federico@gnome.org>
* New settings key for the startup modeFederico Mena Quintero2012-11-264-0/+71
| | | | Signed-off-by: Federico Mena Quintero <federico@gnome.org>
* New way to show $CWD in the shortcutsFederico Mena Quintero2012-11-242-2/+54
| | | | Signed-off-by: Federico Mena Quintero <federico@gnome.org>
* quartz: move SPLASHSCREEN-hinted windows to NSStatusWindowLevelMichael Natterer2012-11-131-4/+4
| | | | | | which does not really have a different effect than the previously used NSPopUpMenuWindowLevel, but is what all code examples I found are using, and it does make more sense.
* Remove bookmark duplicate of shortcutTimothy Arceri2012-11-131-0/+3
| | | | | | | | Application code can set shortcut folders that are already bookmarks. This code causes the bookmarks to be refreshed after the shortcut is added removing any possible bookmark duplicates https://bugzilla.gnome.org/show_bug.cgi?id=577806
* quartz: _gdk_quartz_gc_update_cg_context(): the minimum line width is 1.0Michael Natterer2012-11-081-1/+1
| | | | not G_MINFLOAT. Patch from Kristian Rietveld.
* gtk: clean up properly in GtkFileChooserEntry's dispose() to fix crashesMichael Natterer2012-11-051-16/+12
| | | | | | | Don't just unref the completion_store, call discard_completion_store() instead which also unsets it as the GtkEntryCompletion's model. Fixes bug 681845 and probably some others, because the situation in this bug is completely common.
* gail: use connect_object() for connecting to GtkTextBuffer signalsMichael Natterer2012-11-051-8/+12
| | | | | | because the user_data is the GtkTextView. This used to crash when the text view got destroyed, and the buffer was used for another view. Fixes bug #652204.
* Use bookmarks file from gtk-3.0 XDG config dir if presentCosimo Cecchi2012-10-291-23/+46
| | | | | | | | | Will read from old location if new location isn't found, and will always write back to the original location the file was read from. Adapted from commit ceb3fecd117293387547c284e8294e4cddaa8f17 on the master branch, based on a patch from William Jon McCann <jmccann@redhat.com>
* win32: Don't leak the pixmap cairo_surfaceAlexander Larsson2012-10-241-2/+12
| | | | | | | | | | | GdkPixmapWin32 allocates a cairo_surface manually for non-foreign pixmaps, instead of letting GdkDrawableWin32 create on on-demand. However, the pixmap created surface is a strong ref, rather than the weak ref created by gdk_win32_ref_cairo_surface() so we can't rely on _gdk_win32_drawable_finish to actually free it. So, we have to manually free it when we finalize or we leak it. https://bugzilla.gnome.org/show_bug.cgi?id=685959
* Updated German translationHendrik Knackstedt2012-10-191-429/+494
|
* quartz: Actually use the window background PATTERN colorKristian Rietveld2012-10-091-1/+1
| | | | | | Before we used a window's background color, which resulted in corrupted display in some cases, presumably because we didn't reset the active pattern. This patch seems to eliminate the observed corruption.
* gtk+.props: (VS2010) Update include pathsChun-wei Fan2012-10-071-1/+1
| | | | | | | Correct the include paths for GDK-Pixbuf, as that update was somehow forgotten :| Thanks to Berke Viktor for pointing this out.
* Fix garbage content when windows are initially mappedKristian Rietveld2012-09-281-0/+19
| | | | | The garbage would be visible if any widget enabled the toplevel NSView's CALayer in order to do custom native rendering.
* Really move the docs to a new locationMatthias Clasen2012-09-276-2/+2
| | | | | | It turns out that library.gnome.org is looking for DOC_MODULE when deciding how to name the directory. So, we have to change that to gtk2/.
* Update Visual C++ property sheetsChun-wei Fan2012-09-262-16/+16
| | | | | "Install" the gtk-demo program and data files more like the way done by the autotools build.
* 2.24.132.24.13Matthias Clasen2012-09-231-2/+2
|
* UpdatesMatthias Clasen2012-09-231-0/+16
|
* Change the location of the online docsMatthias Clasen2012-09-232-2/+2
| | | | | | It is better to install these under gdk2/ and gtk2/, to make it explicit what version they are about. Doing this will eventually let us move the gtk3 docs to gtk/.
* Visual C++ support: Add projeccts to build gailutilChun-wei Fan2012-09-1810-20/+451
| | | | | This adds Visual C++ 2008/2010 projects to build the gailutil DLL, like the 3.x releases.
* quartz: Bug 674108 - Hard crash due to wrong NSAutoreleasePool stackingMichael Natterer2012-09-141-16/+29
| | | | | | | | | Apply patch from Kristian Rietveld which addresses two issues in gdkeventloop-quartz.c: This patch moves the autorelease pool drain and introduces protection against the invalidated ufds. Basically, when we suspect ufds has been invalidated by a recursive main loop instance, we refrain from calling the collect function.
* immulticontext: Always check if the global context id changedMatthias Clasen2012-09-091-13/+10
| | | | | | | | | | | | This makes sure that if the gtk-im-module setting changes we update our internal state immediately on the next event whichever it is. In particular this fixes the case of the gtk-im-module setting changing while the user is typing and the slave context remaining the same, effectively ignoring the setting change. Backport of a0f155e83938f6c3e63c312107dee2a970c2eb15. https://bugzilla.gnome.org/show_bug.cgi?id=675365
* Try harder to discriminate Shift-F10 and F10Matthias Clasen2012-09-091-9/+18
| | | | | | | | | | | | | | | | | | | | | | A change in xkeyboard-config 2.4.1 made it so that function keys now have a shift level which has the same symbol, but 'eats' the shift modifier. This would ordinarily make it impossible for us to discriminate between these key combinations. This commit tries harder to discriminate in 2 ways: - XKB has a mechanism to tell us when a modifier should not be consumed even though it was used in determining the level. We now respect such 'preserved' modifiers. This does not fix the Shift-F10 vs F10 problem yet, since xkeyboard-config does not currently mark Shift as preserved for function keys. - Don't consume modifiers that do not change the symbol. For the function keys, the symbol on the shift level is the same as the base level, so we don't consider Shift consumed. For more background on the xkeyboard-config change, see https://bugs.freedesktop.org/show_bug.cgi?id=45008 https://bugzilla.gnome.org/show_bug.cgi?id=661973
* Implement gtk-primary-button-warps-slider GtkSettingKristian Rietveld2012-09-073-10/+88
| | | | | | | It replaces the recently added GtkRange:primary-button-warps-slider style property. Implement the setting in the quartz backend, it proxies the "click in the scroll bar to" property from the OS X PrefPane.
* range: make condition consistent with GTK3Cosimo Cecchi2012-09-061-1/+1
| | | | | | | | | | | cc7abf6a1cccd66a802c5272cd2ac6c944962c78 introduced the primary-button-warps-slider style property, but with a different condition check than the GTK3 counterpart. It turns out we really need to check for the mouse click location here, or we'll warp the slider to pointer also in case we clicked on the slider itself. https://bugzilla.gnome.org/show_bug.cgi?id=683512
* Updated Polish translationPiotr Drąg2012-09-041-18/+27
|
* 2.24.122.24.12Matthias Clasen2012-09-031-0/+19
|
* recent-manager: Coalesce multiple changesEmmanuele Bassi2012-09-032-42/+143
| | | | | | | | | | | | | | | | | | | | | | | | | Since the ::changed implementation of GtkRecentManager implies a synchronous write operation, when we receive multiple requests to emit a ::changed signal we might end up blocking. This change coalesces multiple ::changed emission requests using the following sequence: • the first request will install a timeout in 250 ms, which will emit the ::changed signal • each further request while the timeout has not been emitted will increase a counter ‣ if the counter reaches 250 before the timeout has been emitted, then the RecentManager will remove the timeout source and force a signal emission and reset the counter This sequence should guarantee that frequent ::changed emission requests are coalesced, and also guarantee that we don't let them dangle for too long. https://bugzilla.gnome.org/show_bug.cgi?id=616997
* range: add a primary-button-warps-slider style propertyCosimo Cecchi2012-09-031-8/+29
| | | | | | | Setting this to TRUE (it's FALSE by default) enables the behavior we have in GTK3 for scrollbars. https://bugzilla.gnome.org/show_bug.cgi?id=683279
* Updated Polish translationPiotr Drąg2012-08-312-563/+578
|
* tooltip: add tooltip-radius and tooltip-alpha style propertiesCosimo Cecchi2012-08-302-10/+226
| | | | | | | This allows themes to change the tooltip opacity and radius. Based on a downstream Fedora patch by Matthias Clasen. https://bugzilla.gnome.org/show_bug.cgi?id=683070
* quartz: fix corruption during scrolling in some casesKristian Rietveld2012-08-261-2/+9
| | | | | | | A call to scrollRect must be followed by a call to set that the offset rect needs display for the changes to "take effect". This was not done prior to this patch which, in some cases, caused corruption during scrolling.
* quartz: add evil casting to make sure time wraps correctly on 32bit machinesMichael Natterer2012-08-231-2/+5
| | | | | | | get_time_from_ns_event(): apply patch from Michael Hutchinson which makes sure the returned guint32 wraps correctly on 32 bit machines when the uptime exceeds 2^32 ms. (cherry picked from commit 78506bd604099161819ffdd0fdef98967f8980de)
* Bug 681784 Colorspaces used in gtk+ and cairo quartz backends do notJohn Ralls2012-08-214-6/+6
| | | | | | | match Changes inspired by parafin <help@imtrappedininternet.com> Replace colorspace creation calls to match those used by Cairo.
* fix an typo in zh_CN translationYunQiang Su2012-08-181-1/+1
|
* gtk: ref the action around gtk_action_emit_activate()Michael Natterer2012-08-031-3/+5
| | | | for the same reason we already ref the action's group in the function.
* Allow building with automake 1.12Matthias Clasen2012-08-011-1/+5
|
* fix bug#680901: translations of "even sheet" and "odd sheet" are wrongFunda Wang2012-07-311-409/+437
|
* demos/gtk-demo/rotated_text.c: Remove C99ismChun-wei Fan2012-07-261-4/+5
|
* Fix a case of 'stuck grab'Matthias Clasen2012-07-201-9/+8
| | | | | | | | | | | | | This was showing up when using a combo box in list mode. After popping up the list, the keyboard grab appeared stuck. What was stuck here is only the client-side grab, since we forgot to clean up our grabs when receiving an UnmapNotify. This bug was introduced in 3f6592f60fd15fb353fc84600caefba3054dc892. [ Alexandre Rostovtsev <tetromino@gentoo.org>: backport to 2.24 ] https://bugzilla.gnome.org/show_bug.cgi?id=680346
* Bump versionMatthias Clasen2012-07-151-2/+2
|
* Updates2.24.11Matthias Clasen2012-07-151-0/+35
|
* pixbuf-engine: add a GtkRC option for widget directionCosimo Cecchi2012-07-053-4/+54
| | | | | | | Add a GtkRC option to select for an LTR/RTL widget direction in the pixbuf engine; this will allow the engine to apply different theming assets according to the text direction, which is useful when theming e.g. a spinbutton or a combobox entry.
* [Bug 676362] _gdk_quartz_image_copy_to_image always returns black forDaniel Sabo2012-06-131-4/+3
| | | | | | | the root window Revised patch which doesn't depend upon NSRect being typdeffed from CGRect (64-bit only).
* Bug 676362 - _gdk_quartz_image_copy_to_image always returns black...Daniel Sabo2012-06-111-22/+47
| | | | | | | Implement a special case for the root window, which has to be handled differently on OS X. Contains some bit fiddling corrections by Kristian Rietveld.
* quartz: delay emission of EnterNotify until window position is knownKristian Rietveld2012-06-113-9/+23
| | | | | | | Beforehand, the check whether or not emission is necessary was done based on the "uninitialized" window position in the top left corner. We now wait until the window size is set for the first time, to avoid emitting EnterNotify when it is not necessary.
* Allow fallback for input method modulesMatthias Clasen2012-06-053-15/+38
| | | | | | | | | | | | Accept a :-separated list of module names in GTK_IM_MODULE and the corresponding setting, to deal a bit better with broken situations. https://bugzilla.gnome.org/show_bug.cgi?id=603559 Patch by Akira Tagoh, backported from GTK+ 3. The backport is required because GTK+ 2 and 3 are listening to the same env vars and settings for immodules.
* GtkTreeView: make tree expanding/collapsing more robustMichael Natterer2012-05-311-1/+2
| | | | | gtk_grab_remove() *after* we did the expanding/collapsing, otherwise grab_notify() might kick in and mess with our state. Fixes bug #675835.
View Lorry Controller Status