summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* widget: Synthesize crossing only if sensitivity changed while propagating stateRui Matos2011-12-141-2/+3
|
* Add has-origin property for GtkScaleAndrea Cimitan2011-12-146-31/+171
| | | | | | | | | | | If the scale has an origin (it will have one by default), GtkRange will render the two sides before/after the current value with different style classes, making it possible for themes to use different colors and properties for the two areas. This was possible in GTK 2 with style details, but got lost during the road to 3.0. https://bugzilla.gnome.org/show_bug.cgi?id=665140
* wayland: Add dummy implementation of the wl_data_device functionalityRob Bradford2011-12-141-0/+159
| | | | | | Setup listener functions for the drag and drop events as well as the selection events. Then create and save a data structure representing the data offer from the other client.
* wayland: Add an implementation for GdkAtomRob Bradford2011-12-141-4/+75
| | | | | | This implementation is based on a hash table. The hard coded GtkSelection atoms are preloaded into the hash table at the correct values. User generated atoms start after the last preloaded atom.
* wayland: Get the data device during input device setupRob Bradford2011-12-141-0/+7
| | | | | The data device is a associated with the input device - fetch the data device from the data manager for the current input device.
* wayland: Retrieve the data device manager objectRob Bradford2011-12-142-0/+5
| | | | | | The data device manager is a global object that provides the support infrastructure around data devices. These data device objects are the basis for handling drag and drop as well as selections in Wayland.
* wayland: Don't use deprecated function: gdk_window_get_pointerRob Bradford2011-12-141-1/+1
| | | | Replace it with gdk_window_get_device_position.
* Updated Slovak translationPavol Šimo2011-12-141-1113/+1561
|
* print dialog: Fix authentication logicJan Rękorajski2011-12-141-5/+10
| | | | | | | Reset state of CUPS requests correctly during authentization and check CUPS requests for errors. Don't initialize variables holding password and username with empty string (#664640).
* Fix nicks for the window class enumMatthias Clasen2011-12-131-2/+2
| | | | | | As pointed out in bug 665999, these were just not right. Before this commit, the nicks were 'output' and 'only'. After this commit, they are 'input-output' and 'input-only'.
* Fix set_focus_child handling during focus changesAlexander Larsson2011-12-141-3/+8
| | | | | | | | | | | In many cases we used to set focus_child to NULL all the way up to the top and then to the right value, even if there was a common ancestor, meaning these see a temporary NULL value for focus_child. Only when the new focus widgets direct parent was in the previous ancestor list did we stop early. This fixes that by always stopping propagation when reaching the common ancestor.
* GtkFrame: Fix a casting in the compute_child_allocation() methodClaudio Saavedra2011-12-131-4/+4
| | | | | | | The casting used to calculate the child allocation is confusing MAX(). As a result, width and height end up with negative values, which makes no sense. https://bugzilla.gnome.org/show_bug.cgi?id=666109
* themingengine: split a GtkThemingBackground objectCosimo Cecchi2011-12-124-403/+564
| | | | | Allows easier modification and general sanity of the CSS background rendering code.
* image: take misc padding into account when calculating x/y draw coordsCosimo Cecchi2011-12-121-1/+1
| | | | This fixes the misc-alignment.ui reftest.
* image: add gtk_image_get_preferred_size()Cosimo Cecchi2011-12-121-19/+29
| | | | | Add a function to query the preferred size of the GtkImage, and use it in the get_preferred_width/height implementations.
* treeview: Ensure selection's changed signalBenjamin Otte2011-12-101-1/+1
| | | | | | | | | | | | | There was a corner case where the changed signal was not emitted. If rows were built like this: 1 (not selected) + 2 (selected) + 3 (not selected) And row 1 was removed, no signal would be emitted. I like it when writing tests actually finds bugs that have been around since 2003 - introduced by 4a03ea2334bde7d2e15d0933c5a78f5a2338a854 actually. :)
* treeview: Don't try to optimize away selection_changed signalBenjamin Otte2011-12-101-4/+2
| | | | | | We get certain cases, in particular with SELECTION_MULTIPLE, where we cannot figure out in advance of real_set_cursor() if the selection will actually change.
* tests: Add select/unselect callsBenjamin Otte2011-12-101-5/+46
|
* treeview: Add a CURSOR_INVALID flag to set_cursor_row()Benjamin Otte2011-12-101-6/+6
| | | | | This is necessary so the code doesn't attempt to do things with the previous cursor, which currently cause crashes.
* treeview: Replace lots of boolean args with flagsBenjamin Otte2011-12-101-23/+26
| | | | I want to add more and 3 boolean args is essentially unreadable code.
* tests: Add sanity checks for selectionBenjamin Otte2011-12-101-14/+78
| | | | We want to know that the selection emits "changed" when it changes.
* docs: Update code demo for newer glibBenjamin Otte2011-12-101-2/+1
|
* tests: Dump the operation that is performed to stderrBenjamin Otte2011-12-101-1/+33
|
* tests: Make treechanging test run as fast as possibleBenjamin Otte2011-12-101-1/+1
|
* treeview: Handle the case where the cursor row gets deletedBenjamin Otte2011-12-101-2/+62
| | | | | | | | | | | | | | | | Previously, the cursor would just become invalid, which used to reselect the first row in the treeview later on (without a cursor-changed signal). This leads to a crash now with the recent refactorings. The patch is longer than I'd like it to be, but the situation is kinda complicated, because we want to make sure to move the cursor to a good row. It works like this: 1) From the deleted row, search forward for the first row that is not going to be deleted and is not a separator. 2) If no such row exists, search backwards for a row that is not a separator. 3) If no such node exists, clear the cursor.
* treeview: Replace cursor handling by keeping the nodeBenjamin Otte2011-12-101-175/+114
| | | | | | | | | | | Previously the code used a GtkTreeRowReference, which was (a) less performant and more importantly (b) hiding errors. The errors being hidden were the referenced row becoming invalid or collapsed, because such rows would not be valid cursor rows and it would be necesary to select a new row and emit a "cursor-changed" signal. So if a crash bisects down to this commit, it is very likely that the cursor has not correctly been updated and the cursor row is invalid.
* tests: Put random number into local variableBenjamin Otte2011-12-101-1/+4
| | | | | This way, we can see what function had previously been called when the checks fail.
* treeview: Use _gtk_rbtree_contains() in a11y codeBenjamin Otte2011-12-101-37/+6
|
* rbtree: Add _gtk_rbtree_contains()Benjamin Otte2011-12-102-0/+27
| | | | It's useful in a bunch of places, so split it out
* Fix move-resize emulation with XI2Matthias Clasen2011-12-091-0/+27
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=650943
* wayland: Load cursors from wayland directory under XDG_DATA_DIRSRob Bradford2011-12-091-22/+44
| | | | | | | This means we don't have to have hardcoded "/usr/share/wayland" to find the cursors. This change also fixes up the warning messages for when loading fails.
* Updated Breton translationDenis Arnaud2011-12-091-1039/+1426
|
* Updated Breton translationDenis Arnaud2011-12-091-21/+18
|
* Revert 3fd7dbc94074826755da7fc3237e439ba6e81adaMatthias Clasen2011-12-081-2/+0
| | | | | | | | Calling gdk_keymap_add_virtual_modifiers causes _all_ virtual modifiers to be added, which causes problem when they are co-located on the same real modifier (as Super and Hyper often are). Effectively, this made it impossible to enter key combinations involving Super, since they all turn into Super+Hyper.
* Test some virtual modifiersMatthias Clasen2011-12-081-3/+3
| | | | | This adds some accelerators involving Super and Hyper to testmerge. This helps in testing our accel matching for those.
* print to file: fixed lost filename in guiTimothy Arceri2011-12-071-1/+10
| | | | | | | Stop widget creating an event before updating both directory and filename values. https://bugzilla.gnome.org/show_bug.cgi?id=603823
* overlay: Properly allocate the child upon additionBenjamin Otte2011-12-081-0/+1
| | | | | This ensures that after addition the child gets assigned the proper allocation and the child window is properly shown/hidden.
* overlay: Move codeBenjamin Otte2011-12-081-35/+32
| | | | | | | Move code for child allocation into the child allocation function. Don't keep it in the overlay allocation code. See the next commit for why this is useful.
* overlay: Create child window before setting parentBenjamin Otte2011-12-081-3/+7
| | | | Otherwise, the window will not be used when set_parent() maps the child.
* progressbar: Set state flags on drawRui Matos2011-12-071-0/+5
| | | | We were missing setting state flags on the style context before drawing.
* widget: Unset window-unfocused in gtk_widget_unparent()Rui Matos2011-12-071-0/+3
| | | | | | | Widgets without a parent aren't inside a toplevel window so we must remove window-unfocused as it doesn't make sense outside a toplevel. https://bugzilla.gnome.org/show_bug.cgi?id=661428
* treeview: Fix crash when scrolling to endBenjamin Otte2011-12-071-1/+1
| | | | | | This broke in a4630d0e7b233479825b059e0df0e6d65b0e6734 https://bugzilla.gnome.org/show_bug.cgi?id=665741
* window: copy back window surface data when the implicit paint is flushedCosimo Cecchi2011-12-071-13/+17
| | | | | | | | | | When an implicit paint is flushed during expose, e.g. because a non-double buffered widget is painting, make sure to copy the existing data from the window surface we rendered before flushing back to the paint surface, instead of using an empty base. Code was already handling that (and said so in the comment), but only when no implicit paint was used at all, and not in the case when it's flushed mid-expose.
* window: trivial cleanupCosimo Cecchi2011-12-061-1/+1
|
* window: remove unused arguments and variablesCosimo Cecchi2011-12-061-7/+3
| | | | Trivial cleanup, no functional change.
* modifierstyle: Fix compile errorsBenjamin Otte2011-12-061-6/+0
| | | | Introduced in 7bd2446801ffd0fc2ac5cc98fcd675ac4f3935d6
* Fix demo to use a "normal" transparent value now that it works.Alexander Larsson2011-12-061-1/+1
| | | | The last commit fixed this, so lets have a sane value in the demo code.
* Remove broken optimization in style modifier overridesAlexander Larsson2011-12-061-23/+0
| | | | | | | | | We used to only set the override color or font if it was different than the existing value. However, that means you can't change it to an override that is the same as the default value for the property. With this fixed you can e.g. override with a color of 0,0,0,0 which you couldn't before.
* Try to fix linkingMatthias Clasen2011-12-052-6/+11
| | | | | | | | We need to link against gdk against pangoft2 on X11. Also add Requires.private to gdk-3.0.pc, and try to clean things up some. https://bugzilla.gnome.org/show_bug.cgi?id=665326
* gtk-demo: Add test of transparent GdkWindowsAlexander Larsson2011-12-062-0/+249
| | | | This shows a semi-transparent shadow from a GtkOverlay window
View Lorry Controller Status