summaryrefslogtreecommitdiff
path: root/gtk/gtkspinbutton.c
Commit message (Collapse)AuthorAgeFilesLines
* spinbutton: Free the gadget in finalizeTimm Bäder2016-02-101-0/+1
|
* Various documentation fixesTimm Bäder2016-02-081-1/+1
| | | | | | Always have Since: annotations at the very bottom, use the correct ClassName::signal-name/ClassName:property-name syntax, fix a few typos in type names, wrong function names, non-existing type names, etc.
* spin button: Document sizing peculiaritiesMatthias Clasen2016-01-271-1/+5
| | | | | | | Document that it is best to explicitly set width-chars and max-width-chars to avoid surprises. https://bugzilla.gnome.org/show_bug.cgi?id=727294
* spinbutton: Don't expand the buttonsBenjamin Otte2016-01-261-14/+18
| | | | | | | | When the spinbutton grows larger, distribute horizontal size to the entry and vertical size to the buttons. Obviously, horizontal size only matters for horizontal spinbuttons and vertical for vertical spinbuttons.
* spinbutton: Add a base gadgetBenjamin Otte2016-01-251-195/+53
| | | | | This really messes up rendering in Adwaita because the code now renders the spinbutton's entry node when it didn't before.
* entry: Move spinbutton size hackBenjamin Otte2016-01-251-29/+29
| | | | | | If we want to do special sizing for the text, we need to do it for the text. Otherwise paddings, borders and entyr icons will screw up everything.
* spinbutton: Make the entry gadget be the entry's gadgetBenjamin Otte2016-01-221-24/+11
| | | | | This is a big and somewhat evil hack: We replace the entry's gadget's node with the spinbutton's entry node.
* Use convenience API that was introduced recentlyMatthias Clasen2016-01-131-4/+2
| | | | | Use gtk_css_gadget_set_state in all the places where we previously were getting a node from a gadget, just to call gtk_css_node_set_state.
* spinbutton: fix a typoCosimo Cecchi2016-01-021-1/+1
|
* entry: use a gadgetMatthias Clasen2015-12-171-4/+0
| | | | | | Use a gadget for the entry. Selection and progress still just use a CSS node. Most things seem to work correctly with non-zero margin or padding.
* spinbutton: Port the buttons to gadgetsBenjamin Otte2015-12-151-122/+48
|
* iconhelper: Require passing a cssnode to the constructorBenjamin Otte2015-12-151-3/+4
| | | | Note that we don't use it yet.
* cssnode: Change style-changed signalBenjamin Otte2015-12-121-16/+4
| | | | | | | | Instead of having old and new style, now have a GtkCssStyleChange opaque object that will compute the changes you are interested in for you. This simplifies change signal handlers quite a bit and avoids lots of repeated computation in every signal handler.
* iconhelper: Remove the context argumentBenjamin Otte2015-12-091-2/+2
| | | | Instead, use the widget's context.
* iconhelper: Get rid of _gtk_icon_helper_set_window()Benjamin Otte2015-12-091-1/+0
| | | | Instead use the window of the owner widget.
* iconhelper: Require a widget as construction argumentBenjamin Otte2015-12-091-1/+1
| | | | | Note that the caller needs to ensure the widget lives as long as the iconhelper as the iconhelper will not ref the widget.
* Chain up in state_flags_changedBenjamin Otte2015-12-021-0/+2
| | | | | When introducing handlers for state_flags_changed in the node transitions, chaining up was forgotten.
* GtkSpinButton: Update node state on button releaseTimm Bäder2015-11-201-0/+2
|
* spin button: Fix initial button stateMatthias Clasen2015-11-201-14/+19
| | | | | | | | We can't use up_panel and down_panel as differentiators for the buttons, because these window system resources don't exist before realize(). Just use a one-off enum for this purpose. https://bugzilla.gnome.org/show_bug.cgi?id=758094
* Annotate deprecated style propertiesMatthias Clasen2015-11-161-1/+1
| | | | | | Use G_PARAM_DEPRECATED with deprecated style properties. This will make it easier to identify and remove such stale properties from css, since it will now trigger warnings.
* spinbutton: Document some style properties as deprecatedMatthias Clasen2015-11-161-0/+8
| | | | No code change.
* spinbutton: update node state more oftenMatthias Clasen2015-11-141-2/+6
| | | | | We need to update the entry_node state, and we should update the node state initially.
* spinbutton: Use right state when querying paddingBenjamin Otte2015-11-061-4/+2
|
* spin button: Add diagrams to CSS documentationMatthias Clasen2015-11-031-0/+16
|
* spinbutton: Don't set .entryBenjamin Otte2015-10-291-1/+0
| | | | Also fix Adwaita to not use .entry anymore
* entry, spinbutton: Finish css node conversionMatthias Clasen2015-10-281-22/+12
| | | | | | | | | | | | | | | | | | | | | | | | | This commit creates entry and button subnodes for the buttons in GtkSpinButton. The nodes are ordered like this for horizontal spinbutton + entry + image.left + image.right + progress + button.down + button.up and like this for vertical ones: spinbutton + button.down + entry + button.up This arrangement requires cooperation from GtkEntry to place the entry subnodes correctly, and some small changes in the theme. This commit also fixes progress rendering in vertical spin buttons.
* wip: spinbuttonMatthias Clasen2015-10-281-136/+176
|
* spinbutton: Trivial cleanupMatthias Clasen2015-10-281-5/+2
| | | | Use g_clear_object in a few places.
* gtk: Stop setting GDK_EXPOSURE_MASK on random widgetsAlexander Larsson2015-09-141-1/+1
| | | | | | | | | | | | | | These days exposure happens only on the native windows (generally the toplevel window) and is propagated down recursively. The expose event is only useful for backwards compat, and in fact, for double buffered widgets we totally ignore the event (and non-double buffering breaks on wayland). So, by not setting the mask we avoid emitting these events and then later ignoring them. We still keep it on eventbox, fixed and layout as these are used in weird ways that want backwards compat.
* spin button: Add Home and End as key bindingsMatthias Clasen2015-07-191-0/+2
| | | | | | Make these go to the lower/upper boundary of the adjustment, like Ctrl-PageUp/PageDown already do. https://bugzilla.gnome.org/show_bug.cgi?id=309300
* GtkSpinButton: Stop using gtk_adjustment_value_changedMatthias Clasen2015-05-101-1/+3
| | | | This is just an unnecessary indirection.
* Stop using GDK_POINTER_MOTION_HINT_MASK in widgetsMatthias Clasen2015-03-221-1/+1
| | | | | | It is deprecated and no longer needed, and,as observed in https://bugzilla.gnome.org/show_bug.cgi?id=746253 it interferes with turning off event compression.
* spinbutton: Fix get_text_area_size for vertical spinbuttonsBenjamin Otte2015-03-161-11/+3
| | | | | | | | Commit c5905b13b97012fc9e9424718bdce34e0989f512 changed the semantics of this vfunc and get_entry_size but I only fixed one of them in the spinbutton subclass. https://bugzilla.gnome.org/show_bug.cgi?id=746282
* entry: Make code do what it's meant to doBenjamin Otte2015-03-141-32/+0
| | | | | | | | | | | | | | With the 3.0 transition, this code went from just querying the entry's height request to doing a full size request. Then it got code to revert the features that a full size request does. And then it grew code that manually computed the baseline. Avoid this and just do what happened back in the days: Do a regular height request. This changes the semantics of the get_frame_size() vfunc wrt its behavior towards subclasses overwriting the get_height() vfuncs, but I'm happy to live with that.
* GtkSpinButton: Use the proper stateMatthias Clasen2014-11-261-1/+3
| | | | Use the style contexts current state when querying it.
* 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.
* GtkSpinButton: Simplify codeMatthias Clasen2014-10-191-8/+7
| | | | | No need to explicitly specify a parser function, it will be correctly guessed from the property type.
* spinbutton: Set the correct state on the button contextsBenjamin Otte2014-10-161-4/+5
| | | | | | | | | With the recent save-is-child changes, using gtk_style_context_get_padding (context, different_state) will now open a subelement. This is not what we want, so we check the state whenever we get the button contexts.
* spinbutton: Make the swipe gesture only work on touch devicesCarlos Garnacho2014-08-151-0/+1
| | | | | | | This code was relying on the previous GtkGestureSingle::touch-only default value. https://bugzilla.gnome.org/show_bug.cgi?id=734285
* GtkSpinButton: Prevent public API from unsetting the adjustmentDebarshi Ray2014-08-131-4/+4
| | | | | | | | A spin button really needs an adjustment to work. So don't let the user unset the adjustment by passing NULL to gtk_spin_button_set_adjustment. https://bugzilla.gnome.org/show_bug.cgi?id=734660
* GtkSpinButton: Always emit value-changed when the adjustment is changedDebarshi Ray2014-08-131-46/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | Changing adjustment via the property setter would not emit value-changed, however changing it via gtk_spin_button_configure would. This inconsistency had the following side-effects: - Setting an adjustment with a different value would not update the value shown by the spin button. - Creating a spin button like this (common in GtkBuilder XML) will not show the initial value: g_object_new (GTK_TYPE_SPIN_BUTTON, "adjustment", adj, NULL); Let's use the same code path (ie. gtk_spin_button_configure) for all public facing API for setting adjustment. The code that handled the details of swapping out the old adjustment with the new has been split into an unset_adjustment method and the rest has been folded into gtk_spin_button_configure. A spin button really needs an adjustment to work, so we don't need most of the NULL checks. However we do need to check in unset_adjustment because setting a new adjustment during object creation might try to unset a non-existent one. https://bugzilla.gnome.org/show_bug.cgi?id=734660
* GtkSpinButton: Only notify 'adjustment' if the property changedDebarshi Ray2014-08-121-2/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=734649
* GtkSpinButton: Document some signalsGergely POLONKAI2014-07-191-3/+24
| | | | | Based on a patch by Gergely Polonkai, https://bugzilla.gnome.org/show_bug.cgi?id=733174
* Trivial: Use the canonical signal nameMatthias Clasen2014-07-191-1/+1
|
* GtkSpinButton: Set orientable style classes initiallyMatthias Clasen2014-07-181-0/+1
| | | | | This was an omission, horizontal/vertical would only be set when the orientation is changed.
* GtkSpinButton: Use G_PARAM_EXPLICIT_NOTIFYMatthias Clasen2014-06-091-17/+11
|
* gesture: Replace gtk_gesture_attach/detach with event controller APICarlos Garnacho2014-05-271-2/+2
| | | | | | | | Event controllers now auto-attach, and the GtkCapturePhase only determines when are events dispatched, but all controllers are managed by the widget wrt grabs. All callers have been updated.
* spinbutton: Avoid touch text handles to pop upgesturesCarlos Garnacho2014-05-231-29/+16
| | | | | | | | | | | Those get in the middle more than help on these widgets, the widget is already packed with clickable areas and having handles (and their invisible clickable area around) hovering above don't help, plus the purpose in most likely numeric values is a bit doubtful. All touch events are either consumed by the up/down panels, or the swipe gesture, all GtkEntry handling of touch events on the text window is avoided, so handles to not appear anymore.
* spinbutton: Use GTK_PHASE_CAPTURE for touch swipesCarlos Garnacho2014-05-231-2/+2
| | | | | The gesture must be able to catch first events for it to be seen as recognized in event handlers.
* spinbutton: Attach "swipe to spin" controllers to the bubble phaseCarlos Garnacho2014-05-231-32/+3
| | | | | It is unnecessary to have those process events manually, just attach those to the bubble phase.
View Lorry Controller Status