summaryrefslogtreecommitdiff
path: root/gtk/gtkcalendar.c
Commit message (Collapse)AuthorAgeFilesLines
* calendar: Remove custom css background and border drawingTimm Bäder2017-07-191-15/+3
|
* Remove calls to gtk_widget_set_allocationTimm Bäder2017-07-191-1/+0
| | | | gtk_widget_size_allocate_with_baselines does it automatically now.
* set clip of more widgetsTimm Bäder2017-07-191-0/+2
|
* gtk: Mass delete all GtkWidget event mask APICarlos Garnacho2017-05-251-9/+2
| | | | | | | | | | We now rely on toplevels receiving and forwarding all the events the windowing should be able to handle. Event masks are no longer a way to determine whether an event is deliverable ot a widget. Events will always be delivered in the three captured/target/bubbled phases, widgets can now just attach GtkEventControllers and let those handle the events.
* calendar: Fix else branch indentationsTimm Bäder2017-03-181-2/+2
|
* snapshot: Rename gtk_snapshot_translate_2d()Benjamin Otte2017-01-131-14/+14
| | | | It's now called gtk_snapshot_offset().
* snapshot: Rename append APIsBenjamin Otte2017-01-131-7/+7
| | | | | | Instead of having gtk_snapshot_append_foo_node(), just have gtk_snapshot_append_foo(). Nobody needs to know that this internally uses nodes.
* calendar: Implement snapshot()Benjamin Otte2016-12-231-116/+109
|
* API: Remove gtk_cairo_should_draw_window()Benjamin Otte2016-11-231-15/+11
| | | | The answer is: Yes.
* widget: Use ::measure vfunc to measure sizeTimm Bäder2016-10-221-24/+19
| | | | | | | | Add a new ::measure vfunc similar to GtkCssGadget's that widget implementations have to override instead of the old get_preferred_width, get_preferred_height, get_preferred_width_for_height, get_preferred_height_for_width and get_preferred_height_and_baseline_for_width.
* calendar: Use gdk_window_new_input()Benjamin Otte2016-10-181-41/+23
|
* API: stylecontext: Remove state argument from gettersBenjamin Otte2016-10-161-7/+5
| | | | The argument must always be the current state.
* Use NULL for generic marshallers in g_signal_new()Benjamin Otte2016-08-291-7/+7
| | | | | glib will use the correct marshaller automatically. And as a side effect, we also get all glib optimizations, like a va marshaller.
* dnd: Move GtkDragDest to a separate fileMatthias Clasen2016-03-251-0/+1
| | | | | | This follows what was done for GtkDragSource in 415030d25f2552d3937ee3c394c50d22c5382982 and shaves another 500 lines off gtkdnd.c.
* calendar: Remove duplicate flags valueBenjamin Otte2016-03-201-1/+1
| | | | http://www.viva64.com/en/b/0383/
* calendar: Fix drag highlight problemsMatthias Clasen2016-03-111-1/+19
| | | | Don't propagate :drop(active) to components.
* gtk: Strip newlines from g_warning and g_errorMatthias Clasen2016-02-281-4/+4
| | | | g_logv adds one for us already.
* Don't pass widget state flags to GtkStyleContext APITimm Bäder2015-11-221-1/+1
|
* calendar: Add an element nameMatthias Clasen2015-10-281-2/+3
| | | | This will allow us to drop hardcoded type names in the theme.
* gtk: Stop setting GDK_EXPOSURE_MASK on random widgetsAlexander Larsson2015-09-141-1/+0
| | | | | | | | | | | | | | 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.
* Remove some unused dataMatthias Clasen2015-08-091-6/+0
|
* calendar: Handle invalid datesEmmanuele Bassi2015-01-021-0/+6
| | | | | | | | | | | | | GtkCalendar can have an invalid date — mostly at initialization. This means that GDateTime construction may fail. We need to handle that case gracefully, like the old code did. This fixes the `notify` test suite, which started failing with: /Notification/GtkCalendar: GLib-CRITICAL **: g_date_time_get_day_of_week: assertion 'datetime != NULL' failed inside the Continuous builder.
* GtkCalendar: Slightly change overflow behaviourMatthias Clasen2014-12-231-10/+9
| | | | | | | | | If the first of the month was falling on a Sunday, we would not render any days of the previous month, and instead show two weeks of the next month at the bottom. Improve this by showing one week of each. https://bugzilla.gnome.org/show_bug.cgi?id=301835
* GtkCalendar: Use GDateTime for calculationsMatthias Clasen2014-12-231-97/+32
| | | | | Instead of old copy-paste code, use GDateTime to determine week numbers and days of week.
* stylecontext: Split render functions out into gtkrender.[ch]Benjamin Otte2014-10-031-0/+1
|
* GtkCalendar: deal better with a large allocationMatthias Clasen2014-10-011-7/+4
| | | | | | | | | | | | When allocated more than the requested height, GtkCalendar was 'falling apart'. Not only was the main part rendered at the far end of the allocation, clicking on days was broken in this scenario. Fix this by always placing the main part directly under the header and day names. https://bugzilla.gnome.org/show_bug.cgi?id=737670
* Trivial formatting fixMatthias Clasen2014-10-011-3/+6
|
* Fix a typoMatthias Clasen2014-10-011-1/+1
|
* GtkCalendar: Use G_PARAM_EXPLICIT_NOTIFYMatthias Clasen2014-06-091-54/+69
| | | | And make sure we correctly notify for all properties.
* Fix GtkCalendar drawingMatthias Clasen2014-05-141-0/+1
| | | | | A gtk_widget_get_allocation call was unintentionally dropped in 5cb43c70f776a7.
* calendar: don't use focus-line-widthCosimo Cecchi2014-05-091-22/+6
|
* calendar: simplify codeCosimo Cecchi2014-05-091-76/+48
| | | | | Always use the newly introduced get_component_paddings() instead of doing the work manually every time.
* calendar: use CSS paddings instead of focus pad for day/week areasCosimo Cecchi2014-05-091-31/+67
| | | | focus-padding is going away.
* calendar: grab focus first, emit signals afterCarlos Garnacho2014-03-071-3/+3
| | | | | | | It may be unusual, but handlers of day-selected may want to transfer focus somewhere else, without getting it reset back right after by/to the calendar. This makes popovers demo work on the calendar again, for one...
* docs: use Returns: consistentlyWilliam Jon McCann2014-02-191-4/+4
| | | | Instead of Return value:
* docs: use apostrophes in *n'tWilliam Jon McCann2014-02-071-1/+1
|
* docs: list items require blank linesWilliam Jon McCann2014-02-011-3/+4
|
* all: Add names to timeoutsBastien Nocera2013-10-231-0/+2
| | | | | | | Add names to every timeout we setup, so it's easier to track their usage, and debug possible misbehaviour. https://bugzilla.gnome.org/show_bug.cgi?id=710651
* gtkdnd: Introduce a new API for more accurate drag origin dataJasper St. Pierre2013-08-141-2/+3
| | | | | | | | | | | | | | | When trying to drag, we currently the position of the first motion event to determine where the drag came from. This might be alright in the case of the old animation, but the data will be inaccurate if the user has moved the pointer quite a bit since pressing the cursor to start dragging. While we could monkey patch the GdkEvent at the widget layer, this is unintuitive and strange. Add a new API that takes a set of pointer coordinates describing the origin of the drag. Additionally, adapt most widgets to use it and use it with correct coordinates. https://bugzilla.gnome.org/show_bug.cgi?id=705605
* Deprecate and ignore the timeout-initial and timeout-repeat settingsWilliam Jon McCann2013-07-111-14/+5
|
* gtk: Use new macros for defining private dataEmmanuele Bassi2013-07-091-54/+49
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=702996
* Add gtk_widget_(un)register_windowAlexander Larsson2013-02-071-4/+4
| | | | | | | | | | | | This replaces the previously hardcoded calls to gdk_window_set_user_data, and also lets us track which windows are a part of a widget. Old code should continue working as is, but new features that require the windows may not work perfectly. We need this for the transparent widget support to work, as we need to specially mark the windows of child widgets. https://bugzilla.gnome.org/show_bug.cgi?id=687842
* Fix malformed doc commentsMatthias Clasen2012-04-121-3/+3
| | | | | Most of these are forgotten :'s and similar details which gtk-doc now warns about.
* calendar: Set GDK_SCROLL_MASK explicitlyCarlos Garnacho2012-03-011-0/+1
| | | | | selecting for button press/release doesn't suffice anymore to get scroll events.
* Change FSF AddressJavier Jardón2012-02-271-2/+1
|
* gtkcalendar: Use symbolic names for button numbersCarlos Garcia Campos2012-01-271-3/+3
|
* calendar: Use the widget state flags as a base for drawing arrowsRui Matos2011-12-191-20/+16
| | | | | | | | This allows drawing calendar arrows in all possible states the main widget may be in. The arrow_state array is converted into a bit field since it only really needs to store boolean information about prelight for each arrow.
* calendar: Use the widget state flags as a base for drawing daysRui Matos2011-12-191-19/+14
| | | | | Instead of building a set of state flags specifically for drawing days, base it on the underlying widget state flags.
* Make focus rectangles optionalMatthias Clasen2011-08-101-2/+2
| | | | | | | | | | | | | | | | | | This commit introduces a new setting, gtk-visible-focus, backed by the Gtk/VisibleFocus X setting. Its three values control how focus rectangles are displayed. 'always' is equivalent to the traditional GTK+ behaviour of always rendering focus rectangles. 'never' does what it says, and is intended for keyboardless situations, e.g. tablets. 'automatic' hides focus rectangles initially, until the user interacts with the keyboard, at which point focus rectangles become visible. https://bugzilla.gnome.org/show_bug.cgi?id=649567
* calendar: Use gtk_widget_class_accessible_set_role()Benjamin Otte2011-07-181-14/+1
|
View Lorry Controller Status