1. 12 Feb, 2018 1 commit
    • Rafal Luzynski's avatar
      calendar: Use the new "%OB" format if supported · cbf118c2
      Rafal Luzynski authored
      Due to the recent changes introduced in glibc 2.27 "%OB" is the
      correct format to obtain a month name as used in the calendar
      header.  The same rule has been working in BSD family (including
      OS X) since 1990s.  This simple hack checks whether "%OB" is supported
      at runtime and uses it if it is, falls back to the old "%B" otherwise.
      
      Closes: #9
      cbf118c2
  2. 01 Aug, 2017 1 commit
    • Daniel Boles's avatar
      Calendar: Add default case to appease Coverity · cd7e5fae
      Daniel Boles authored
      CID 1432024 (#1 of 1): Uninitialized scalar variable (UNINIT)
      2. uninit_use_in_call: Using uninitialized value rect.x when calling
      calendar_arrow_rectangle.
      
      Add a default case to the switch which will bail out with
      g_assert_not_reached(), which should reassure Coverity that the method
      is always called with a valid value that is handled in the switch.
      cd7e5fae
  3. 18 Mar, 2017 1 commit
  4. 29 Aug, 2016 1 commit
  5. 25 Mar, 2016 1 commit
  6. 20 Mar, 2016 1 commit
  7. 11 Mar, 2016 1 commit
  8. 28 Feb, 2016 1 commit
  9. 22 Nov, 2015 1 commit
  10. 28 Oct, 2015 1 commit
  11. 14 Sep, 2015 1 commit
    • Alexander Larsson's avatar
      gtk: Stop setting GDK_EXPOSURE_MASK on random widgets · d5f17549
      Alexander Larsson authored
      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.
      d5f17549
  12. 09 Aug, 2015 1 commit
  13. 02 Jan, 2015 1 commit
    • Emmanuele Bassi's avatar
      calendar: Handle invalid dates · b46fdb2d
      Emmanuele Bassi authored
      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.
      b46fdb2d
  14. 24 Dec, 2014 2 commits
  15. 03 Oct, 2014 1 commit
  16. 02 Oct, 2014 1 commit
  17. 01 Oct, 2014 2 commits
  18. 09 Jun, 2014 1 commit
  19. 15 May, 2014 1 commit
  20. 09 May, 2014 3 commits
  21. 07 Mar, 2014 1 commit
    • Carlos Garnacho's avatar
      calendar: grab focus first, emit signals after · efb4f2db
      Carlos Garnacho authored
      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...
      efb4f2db
  22. 19 Feb, 2014 1 commit
  23. 07 Feb, 2014 1 commit
  24. 01 Feb, 2014 1 commit
  25. 23 Oct, 2013 1 commit
  26. 14 Aug, 2013 1 commit
    • Jasper St. Pierre's avatar
      gtkdnd: Introduce a new API for more accurate drag origin data · 030b62d1
      Jasper St. Pierre authored
      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
      030b62d1
  27. 11 Jul, 2013 1 commit
  28. 09 Jul, 2013 1 commit
  29. 07 Feb, 2013 1 commit
    • Alexander Larsson's avatar
      Add gtk_widget_(un)register_window · 3d4cd4db
      Alexander Larsson authored
      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
      3d4cd4db
  30. 13 Apr, 2012 1 commit
  31. 01 Mar, 2012 1 commit
  32. 27 Feb, 2012 1 commit
  33. 27 Jan, 2012 1 commit
  34. 19 Dec, 2011 2 commits
  35. 10 Aug, 2011 1 commit
    • Matthias Clasen's avatar
      Make focus rectangles optional · 2ba9c4b4
      Matthias Clasen authored
      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
      2ba9c4b4