summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* update morph to yaml, and require loader cachebaserock/gnomePaul Sherwood2014-07-241-11/+12
|
* Add gtk+.morphSam Thursfield2014-07-241-0/+11
| | | | | Need to ensure gdk-pixbuf loaders cache is created before running build.
* GtkButton: do not prelight in touchscreen modeAndreas Müller2014-07-201-2/+6
| | | | | | | | Code was copied from GtkToggleButton. Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> https://bugzilla.gnome.org/show_bug.cgi?id=689138
* Updated Hungarian translationBalázs Úr2014-07-081-115/+120
|
* Build: Provide Simple Support for MSVC 2012/2013Chun-wei Fan2014-07-015-3/+108
| | | | | | | | | | | | | As the Visual Studio 2012/2013 are only slightly different from the Visual Studio 2010 projects, we can provide support for them by using scripts to copy the Visual Studio 2010 projects, and update the specific parts as necessary. This is being provided to help people still needing GTK+-2.x and also to help them to transition to GTK+-3.x easier. Thus, there would be little maintenance overhead for these as only the 2010 projects need to be kept up-to-date as a result. This might change when we do get the stack working with WinRT/Metro, but that's going to be another totally different issue.
* Fix "Installation" for Visual Studio 2010+Chun-wei Fan2014-07-011-5/+5
| | | | | | We need to enclose paths containing $(BinDir) with double quotes as it points to something like c:\foo\gtk+-x.yy.zz, which the copy command on Windows does not like "+" in paths unless enclosed in quotes.
* 2.24.242.24.24Matthias Clasen2014-06-232-2/+26
|
* Include image data in the builtin icon cacheMatthias Clasen2014-06-231-0/+1
|
* Fix a pixmap leak in the ms-windows engineMatthias Clasen2014-06-221-0/+2
| | | | This was pointed out in https://bugzilla.gnome.org/show_bug.cgi?id=731967.
* Updated Hebrew translationYosef Or Boczko2014-06-181-460/+490
|
* Updated Polish translationPiotr Drąg2014-06-171-115/+119
|
* gtk-update-icon-cache: Add an --include-image-data optionMatthias Clasen2014-06-172-2/+12
| | | | | | | | Now that we don't include the image data by default anymore, lets add an option that does it. Conflicts: docs/reference/gtk/gtk-update-icon-cache.xml
* updateiconcache: Don't include image data by default anymoreJasper St. Pierre2014-06-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since large images are in the icon cache, and apps don't tend to use that many icons anymore, simply don't include image data and instead make apps load files from disk. Additionally, since they're stored in GdkPixbuf data, that means that we have to first convert them either to a cairo_surface_t, which requires converting pixel data to be premulitplied, or an OpenGL texture, which requires a whole GPU upload anyway. So, even with the icon cache, the goal of icons through zero-copy, mmap()'d data from disk just isn't doable with the icon cache format we have. The icon cache on my disk is nearing 100MB, since we include a bunch of high-resolution application icons, that I doubt would be used by apps at all. Removing this inefficient pixel data makes memory usage for all applications go down, with no speed loss. The icon cache also, however, has an index of what icons are in each folder, which prevents a readdir() and allows GTK+ to know what icon is where without having to do a bunch of stat(); calls. Keeping this data is good for GTK+, so we should still keep the index. It doesn't make sense to remove any code for mapping pixel data from the icon cache. There's a plan in the works to have a symbolic icon cache that does pixel math on 16x16 icons to prevent slow SVG rendering. 16x16 pixels are fairly small, and such images are flat colors, which should compress easily, so the icon cache would be worthwhile here. So let's keep the code around in preparation for that case. https://bugzilla.gnome.org/show_bug.cgi?id=721895
* MSVC 2010+ Projects: Update "Installation" ProcessChun-wei Fan2014-06-092-17/+33
| | | | | | | | | | | | | | | Currently, due to the way that Visual Studio 2010+ projects are handled, the "install" project does not re-build upon changes to the sources, as it does not believe that its dependencies have changed, although the changed sources are automatically recompiled. This means that if a part or more of the solution does not build, or if the sources need some other fixes or enhancements, the up-to-date build is not copied automatically, which can be misleading. Improve on the situation by forcing the "install" project to trigger its rebuild, so that the updated binaries can be copied. This does trigger an MSBuild warning, but having that warning is way better than not having an up-to-date build, especially during testing and development.
* pixbuf-engine: Fix the build with -Werror=format-securityKalev Lember2014-05-231-1/+1
|
* gdkselection-win32.c: Declare Variables At Top Of BlockChun-wei Fan2014-05-161-3/+6
| | | | ...so that builds on Visual C++ can be fixed.
* GtkMountOperation: Clean up a dangling signal handlerMatthias Clasen2014-05-061-10/+14
| | | | | Based on a patch by Eugene Shatokhin, https://bugzilla.gnome.org/show_bug.cgi?id=723366
* gdk/win32: VK_SNAPSHOT maps to GDK_PrintMarc-André Lureau2014-04-241-0/+2
| | | | | | | Also, I am not sure the above VK_PRINT -> GDK_Print mapping is correct, but it doesn't hurt yet. https://bugzilla.gnome.org/show_bug.cgi?id=686170
* win32: do not crash on invalid utf8 conversionMarc-André Lureau2014-04-241-1/+8
| | | | | | | g_utf8_to_utf16() is not guaranteed to succeed. Check the error and return if it failed. https://bugzilla.gnome.org/show_bug.cgi?id=696232
* gdk/win32: remove extra allocation for \r removalMarc-André Lureau2014-04-241-6/+4
| | | | | | | | | | | | | | | | | | | | | | Although I can't find explicit documentation for clipboard pointer, it seems to be possible to modify clibpoard memory without side-effects. According to MSDN, http://msdn.microsoft.com/en-us/library/windows/desktop/aa366596%28v=vs.85%29.aspx "The global and local functions are supported for porting from 16-bit code, or for maintaining source code compatibility with 16-bit Windows. Starting with 32-bit Windows, the global and local functions are implemented as wrapper functions that call the corresponding heap functions using a handle to the process's default heap." "Memory objects allocated by GlobalAlloc and LocalAlloc are in private, committed pages with read/write access that cannot be accessed by other processes. Memory allocated by using GlobalAlloc with GMEM_DDESHARE is not actually shared globally as it is in 16-bit Windows. This value has no effect and is available only for compatibility. " https://bugzilla.gnome.org/show_bug.cgi?id=711553
* win32: add more clipboard data checks to avoid crashMarc-André Lureau2014-04-242-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | It may happen that the received clipboard data is empty, but if it's of type image/bmp, gtk+ will crash: gdk_property_change: 00030AD4 GDK_SELECTION image/bmp REPLACE 8*0 bits: ... delayed rendering gdk_selection_send_notify_for_display: 00030AD4 CLIPBOARD image/bmp GDK_SELECTION (no-op) _gdk_win32_selection_convert_to_dib: 1252003C image/bmp Program received signal SIGSEGV, Segmentation fault. 0x749a9f40 in msvcrt!memmove () from C:\Windows\syswow64\msvcrt.dll Thread 1 (Thread 2248.0x1b34): target=0xc07b) at gdkselection-win32.c:1292 at gdkevents-win32.c:3498 wparam=8, lparam=0) at gdkevents-win32.c:232 message=773, wparam=8, lparam=0) at gdkevents-win32.c:263 C:\Windows\syswow64\user32.dll C:\Users\rugoosse\AppData\Local\virt-viewer\bin\libpangocairo-1.0-0.dll wparam=0, lparam=-1687549457) at gdkevents-win32.c:248 C:\Users\rugoosse\AppData\Local\virt-viewer\bin\libpangocairo-1.0-0.dll https://bugzilla.gnome.org/show_bug.cgi?id=728745
* Visual Studio 2010 Projects: Revamp the ProjectsChun-wei Fan2014-04-0219-2304/+2262
| | | | | | | | | | | | | | | | | | As we are likely to have GTK+-2.x around for some time, revamp the Visual Studio 2010 projects like what was done for rest of the GTK+ stack, namely: -Split the property sheets, in a way like what was done for the rest of the stack. Also clean up the resulting property sheets a bit, and update the projects to use these property sheets. -Use UNIX line endings for all projects and property sheets, to ease future application of patches. -Make the copying of config.h.win32 and gdkconfig.h.win32 into custom build rules, so that they may be removed properly and re-copied during change and update. -Add a PlatformToolset tag, so if we want to support building with Visual Studio 2012/2013, the transition can be done quite easily with a script, such as what is now being done for the Visual Studio 2012 projects for GLib.
* Visual Studio 2008 Projects: Revamp the ProjectsChun-wei Fan2014-04-0213-1667/+1769
| | | | | | | | | | | | | | | | As we are likely to have GTK+-2.x around for some time, revamp the Visual Studio 2008 projects like what was done for rest of the GTK+ stack, namely: -Split the property sheets, in a way like what was done for the rest of the stack. Also clean up the resulting property sheets a bit, and update the projects to use these property sheets. -Use UNIX line endings for all projects and property sheets, to ease future application of patches. -Make the copying of config.h.win32 and gdkconfig.h.win32 into custom build rules, so that they may be removed properly and re-copied during change and update. Similar updates will be applied for the Visual Studio 2010 projects ASAP.
* treeview: properly remove the timeout in expand_collapse_timeout()Michael Natterer2014-04-021-1/+7
| | | | or it will later warn about removing a source that doesn't exist.
* Print to a file in the current directory by defaultMike Gorse2014-03-181-1/+10
| | | | | | | When printing to a file, the filename was not being propagated if a directory was not specified. https://bugzilla.gnome.org/show_bug.cgi?id=711177
* printing: Fail nicely when /tmp is not writableMarek Kasik2014-03-184-5/+6
| | | | | | | Don't crash when /tmp is not writable when printing to file. Show that getting of printer details failed for CUPS printers. https://bugzilla.gnome.org/show_bug.cgi?id=693200
* 2.24.232.24.23Matthias Clasen2014-03-171-0/+21
|
* Bug 634146 - Check g_win32_get_package_installation_directory_of_module() ↵Hans Breuer2014-03-161-1/+1
| | | | | | | | return value Remaining part of patch from Joshua Element Green. https://bugzilla.gnome.org/show_bug.cgi?id=634146
* win32: free allocated gdi objects in 16bppMarc-André Lureau2014-03-162-0/+7
| | | | | | | | | | In 16bpp, Gdk is creating hbitmap with CreateDIBSection() and a hdc with CreateCompatibleDC(). Those 2 objects need to be released when the pixmap is finalized. https://bugzilla.gnome.org/show_bug.cgi?id=671538 Signed-off-by: Hans Breuer <hans@breuer.org>
* exstyle changed after the window size adjustmentPavel2014-03-161-15/+15
| | | | | | | | | | | | Originaly the size of the window based on the client area size has been calculated first and then variables dwStyle and dwExStyle have been changed. Thus the window size has been calculated for different windows type then eventually used when calling CreateWindowEx. This caused for example the Gimp tool windows to have different size than formerly saved in session. The whole code calculating the window size is moved after the last adjustment of dwExStyle variable in this patch. Signed-off-by: Hans Breuer <hans@breuer.org>
* Bug 665507 - Pixmap via cairo DIB breaks gdk_gc_set_stipple() useHans Breuer2014-03-161-28/+11
| | | | | | Only one bitmap can be selected into a device context. Using the DIB created by cairo consumes the one opportunity, so every further SelectObject into the same DC in GDK code will fail.
* win32: restore effect of _gdk_selection_property_deleteHans Breuer2014-03-161-1/+3
| | | | | | | | | | Can not find in the changelog entry why it was disabled at all, see: http://git.gnome.org/browse/gtk+/commit/?id=3f4c73 The ill effect is somewhat hidden: if you try to copy images via clipboard only the first one is pastable, i.e. Gdk keeps the reference to the first image and provides it for later paste.
* printing: Don't crash because of missing g_clear_pointer()Marek Kasik2014-03-121-3/+8
| | | | | | | g_clear_pointer() is not available in glib-2.28 which is minimal required version for gtk+-2.24. https://bugzilla.gnome.org/show_bug.cgi?id=708783
* Bug 711298 - "Edit Scheduled Transaction" window way too modalJohn Ralls2014-01-241-2/+0
| | | | | | | | Put dialogs and utility windows in the same level as normal and toolbar windows so that Gtk can control their stacking instead of forcing them, rather unnaturally, to be on top of all other windows, even other application windows, even when another application has focus.
* Update docs for GtkEntry::activateMatthias Clasen2014-01-221-6/+6
| | | | | | Remove the 'you shall not connect' message from this signal. While it is a keybinding signal, using it from applications is fine and, in fact, expected.
* docs: Fix gdk_pixmap_new arguments in tutorialWilliam Jon McCann2014-01-221-12/+14
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=708119
* GtkFileChooser: fix documentationGiovanni Campagna2014-01-181-3/+4
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=722496
* filechooser: Document the settings keysFederico Mena Quintero2014-01-061-0/+91
| | | | | This is so people can modify gnome-tweak-tool or whatever without directly diving into the source.
* Fixed GtkLabel documentation on linksLuis Menina2013-12-211-1/+1
| | | | An escaped '&lt;' wasn't complete, the 'lt' part was missing.
* gdkwindow: Don't add the same window to "update_windows" twiceMarek Kasik2013-12-181-0/+9
| | | | | | This prevents passing of such window to another GMainLoop. https://bugzilla.gnome.org/show_bug.cgi?id=711552
* gdkwindow: Handle references in "update_windows" list correctlyMarek Kasik2013-12-161-7/+12
| | | | | | | | | | | | Since update_windows list is a static variable in GdkWindow.c which contains pointers to windows which needs to be updated, it can happen that it contains a pointer to a window even after quit from a gtk_main(). If another gtk_main() is called in the same process it tries to process windows in the list which leads to a crash. Correct reference count handling of added windows prevents such applications from crash. https://bugzilla.gnome.org/show_bug.cgi?id=711552
* Bug 651224 - Potential NULL display ptr from quartz ↵John Ralls2013-12-091-1/+3
| | | | gtk_clipboard_wait_for_contents
* iconfactory: Initialize varibale to NULL in failure pathBenjamin Otte2013-12-061-0/+2
| | | | Otherwise we use random memory and that is not good.
* ime: Add builtin handling of dead keysCarlos Garnacho2013-12-051-5/+92
| | | | | | | | | | | | | | | | | | The IME input method has been both ignoring keypresses of non-spacing characters (ditching these as non displayable), and not letting IME do anything about those. Even though, the sparse documentation on IMM/IME seems to hint that applications can't pipe non-spacing characters to the input method manager, and experimentation shown that those characters are indeed handled differently than how it'd be expected. Then, add basic handling of dead keys on the IME input method itself , as it's not mutually exclusive with regular keymaps with dead keys. https://bugzilla.gnome.org/show_bug.cgi?id=704937
* Bug 712536 - Themes with gap_(start|end)_file but no actual file crashJehan2013-12-051-8/+5
| | | | | Code factorization in commit 34fd123 reintroduced bug fixed in 0d396ab with non-equivalent factorized tests.
* GtkFileChooser: avoid a memory leakMatthias Clasen2013-12-011-0/+3
| | | | | | | The directory enumeration code was leaking references to GtkFolder objects. https://bugzilla.gnome.org/show_bug.cgi?id=705367
* Avoid a crash in the pixbuf engineMatthias Clasen2013-12-011-1/+1
| | | | | This is fallout from e4c83bbfdb60fdfe0bae207b1ddae295dc267a23, which removed a necessary check.
* Remove an unused struct memberMatthias Clasen2013-12-011-4/+0
| | | | AsyncFuncData.folder was entirely unused. Drop it.
* pixbuf-engine: Clean up error conditions and destructorsEmmanuele Bassi2013-11-221-36/+23
| | | | | | | Simplify the error checks and move all common behaviour into a utility function. https://bugzilla.gnome.org/show_bug.cgi?id=712536
* pixbuf-engine: Improve ThemePixbuf clean up functionsEmmanuele Bassi2013-11-222-2/+20
| | | | | | | Make theme_pixbuf_destroy() NULL-safe like g_free(), and add a clear function in the spirit of the g_clear_* family of functions. https://bugzilla.gnome.org/show_bug.cgi?id=712536
View Lorry Controller Status