<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Am 10.06.2010 um 20:43 schrieb ttlee1984:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Sedat,<br><br>Thanks. But it works like Johannes's advice, <br>dbus-send --session --type=method_call --print-reply --dest=org.freedesktop.Hal /org/freedesktop/Hal/device/computer_backlight org.freedesktop.Hal.Device.LaptopPanel.GetBrightness<br> <br>And the --dest argument, like pointed by Dean, is the well known bus name (connection name, or called service name by Qt. I am relieved that I am not the only one who got confused). <br><br>By the way, I have to say I am not quite clear why this argument is necessary. Sure it represents the connection to the bus, but in our method calling case, isn't it enough to have 1) object path and 2) method name (including interface)? It is also my question in the Qt API <font><font size="2">createMethodCall</font></font> I pasted before. I always get confused about these concepts.<br></blockquote><div><br></div></div>Two parameters are not enough: The object path is per-server<div>and the interface name is not connected to any server either,</div><div>it's not necessary that org.foo.bar serves objects that expose</div><div>interfaces named org.foo.bar.baz; it can serve objects that expose</div><div>ham.egg.whatnot as well.</div><div><br></div><div>In short: you need to specify the server name as this information is</div><div>not present in the object path and not in the interface name.</div><div><br></div><div>Hope that helps,</div><div><br></div><div>:M:</div><div><br></div></body></html>