1. 21 Dec, 2010 11 commits
  2. 15 Dec, 2010 1 commit
    • Carlos Garnacho's avatar
      Add gdk_event_[gs]et_source_device(). · f5a20ab6
      Carlos Garnacho authored
      This function may be used to know the hardware device that triggered
      an event, it could resort to the master device in the few cases there's
      not a direct hardware device to relate to the event (i.e.: crossing events
      due to grabs)
      f5a20ab6
  3. 15 Oct, 2010 1 commit
  4. 26 Sep, 2010 1 commit
  5. 21 Sep, 2010 1 commit
    • Owen W. Taylor's avatar
      Use g_warning() for X errors and X IO errors · 93e203e0
      Owen W. Taylor authored
      Currently fprintf(stderr, ...) is used for X error and X IO errors
      (unless compiled with debugging, in which case g_error() is used for
      X errors.)
      
      But if an application is redirecting log messages, we really want
      X errors to appear in that same log, so it's better to use a g_logv()
      variant.
      
      Though g_warning() isn't really appropriate for "lost connection to the
      server", G_LOG_LEVEL_INFO isn't part of the "prefixed log levels"
      so will produce output without the application name and PID.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=630216
      93e203e0
  6. 19 Sep, 2010 1 commit
  7. 18 Sep, 2010 3 commits
  8. 10 Jul, 2010 1 commit
  9. 29 Jun, 2010 2 commits
  10. 26 May, 2010 1 commit
  11. 25 May, 2010 1 commit
  12. 08 Jun, 2009 1 commit
  13. 01 Jun, 2009 2 commits
  14. 29 May, 2009 1 commit
  15. 02 Apr, 2009 12 commits