Permalink
Commits on Nov 6, 2015
Commits on Nov 5, 2015
  1. @lumag

    INCLUDES -> AM_CPPFLAGS conversion

    Fix the following issue reported by automake:
    
    libkeybinder/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
    lua-keybinder/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
    python-keybinder/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
    
    Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
    lumag committed Nov 5, 2015
  2. @lumag

    Use pygobject-codegen-2.0 instead of deprecated pygtk-codegen-2.0

    Fix the following warning:
    
    note: pygtk-codegen-2.0 is deprecated, use pygobject-codegen-2.0 instead
    note: I will now try to invoke pygobject-codegen-2.0 in the same directory
    
    Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
    lumag committed Nov 5, 2015
  3. @lumag

    Do not use deprecated Gtk-Doc 'Rename to' tag

    This fixes two following warnings:
    
    bind.c:496: Warning: Keybinder: GObject-Introspection specific GTK-Doc
    tag "Rename to" has been deprecated, please use annotations on the
    identifier instead:
     * Rename to: keybinder_bind
       ^
    bind.c:570: Warning: Keybinder: GObject-Introspection specific GTK-Doc
    tag "Rename to" has been deprecated, please use annotations on the
    identifier instead:
     * Rename to: keybinder_unbind
       ^
    
    Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
    lumag committed Nov 5, 2015
  4. @lumag

    Fix memory leak in keybinder_bind_full

    Resources allocated by XkbGetMap() should be freed by XkbFreeKeyboard.
    Otherwise I get the following leaked memory report from Valgrind:
    
    ==14972== 1,920 bytes in 48 blocks are definitely lost in loss record 1,598 of 1,626
    ==14972==    at 0x402C118: calloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
    ==14972==    by 0x5064EA8: XkbGetMap (in /usr/lib/i386-linux-gnu/libX11.so.6.3.0)
    ==14972==    by 0x428019D: grab_ungrab (bind.c:203)
    ==14972==    by 0x4280320: do_grab_key (bind.c:326)
    ==14972==    by 0x4280721: keybinder_bind_full (bind.c:574)
    ==14972==    by 0x4280791: keybinder_bind (bind.c:539)
    ==14972==    by 0x8049220: xvd_keys_init (xvd_keys.c:141)
    ==14972==    by 0x8048F84: main (main.c:126)
    lumag committed Nov 5, 2015
Commits on Jun 17, 2012
  1. python-keybinder: Fixup INCLUDES in Makefile.am

    This fixes a failing make distcheck
    committed Jun 17, 2012
  2. configure.ac: Version 0.3.0

    committed Jun 17, 2012
  3. NEWS: Update for v0.3.0

    committed Jun 17, 2012
Commits on May 8, 2011
  1. Update README

    committed May 8, 2011
  2. Draft NEWS

    committed May 8, 2011
  3. Add forgotten date in NEWS

    committed May 8, 2011
  4. Fixup Makefile.am for distcheck

    committed May 8, 2011
  5. Implement keybinder_bind_full

    keybinder_bind_full includes a GDestroyNotify callback for notification
    when the keybinding callback is unregistered & and generated bindings
    can destroy their closure object. This shadows keybinder_bind in the
    exported bindings.
    committed May 8, 2011
  6. Add introspection annotations for libkeybinder

    Annotate keybinder_bind so that it can be exported, and annotate
    keybinder_unbind so that it is skipped.
    committed May 8, 2011
  7. In introspection bindings, export unbind_all as unbind

    This provides a sensible continuation from old pygtk(2) api to the
    exported introspection api -- .unbind() is the same.
    
    That said, there are still major differences in the exported API for
    python, like having to call Keybinder.init() manuall and many other
    things.
    committed May 8, 2011
  8. Implement keybinder_unbind_all(keystr)

    keybinder_unbind_all unregisters all callbacks for a given keystring.
    
    The per-callback unbind is quirky and impossible for automatic bindings
    to get right, so keybinder_unbind_all will replace unbind for
    introspection bindings.
    committed May 8, 2011
  9. fixup examples/Makefile

    committed May 8, 2011
  10. Allow building libkeybinder against GTK+ 3.0 using --enable-gtk=gtk3

    Enable building the C library itself against GTK+ version 3.
    Python-keybinder will never work against GTK3, but the base C library
    can, just like the lua bindings can.
    committed May 8, 2011
Commits on May 7, 2011
  1. Port bind.c to GTK+ 3.0 (Compatible with 2.20 and 3.0)

    With this change, libkeybinder (the C library part) can be compiled
    against either Gtk+-2.0 or Gtk+-3.0. There were very minor changes
    needed to accomplish that.
    
    However, build configuration has *not yet* been updated and it only
    allows building against Gtk+-2.0 so far. Build configuration will be
    updated when we solve the versioning/naming issue (so that
    keybinder+gtk2 and keybinder+gtk3 don't conflict with each other).
    committed May 7, 2011
  2. @dktrkranz
Commits on May 30, 2010
  1. Update NEWS and README for 0.2.2

    committed May 30, 2010