Ignore:
Timestamp:
07/04/14 08:39:01 (6 years ago)
Author:
ecloud
Message:

default-signal-handler takes 5 args: bus path svc iface mber

However maybe it's a bad idea because a dbus_message has more stuff, so
the handler doesn't get enough info to actually handle the signal.
But what kind of interface is that even if it could? The idea is this
egg is to be a nice high-level abstraction, not a way of digging around
in the bowels of how libdbus does things. And if we pass the whole message
to this handler, it's a C object, so what if the handler tries to keep it
for too long. Have never addressed GC yet anyway.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • release/4/dbus/trunk/examples/receive-car-turn.scm

    r31085 r31086  
    11(use (prefix dbus dbus:))
    22
    3 (dbus:default-signal-handler (lambda (w) (printf "warning: ~a~%" w)))
     3(dbus:default-signal-handler (lambda (bus path svc iface mber)
     4        ((dbus:printing-signal-handler) bus path svc iface mber)
     5        (dbus:dump-callback-table)))
    46
    57(define (turn-right) (printf "car is turning to the right~%"))
Note: See TracChangeset for help on using the changeset viewer.