Hi Sylvestre,

you may be using an old version. The current release has an optional  
third argument to connect() when used from bindings. See
http://dev.zuckschwerdt.org/obexftp/browser/trunk/swig/client.i line  
113ff. It was introduced in r196 a year ago
http://dev.zuckschwerdt.org/obexftp/changeset/196

The src arg can either be a number (which will be passed as a string)  
or the name like hci0.

Btw. Changes to a public interface (API) are best done in a compatible  
way. That's why it has many functions with just slightly different  
signatures now.

Am 08.08.2008 um 23:07 schrieb Sylvestre Mergulhão:

> I'm testing sending files with obexftp and push with the Ruby wrapper.
> I saw thats there is no support for sending a file with an especific
> hci device. I'm thinking on how to do this. I thought thats the easier
> is to redefine obexftp_connect_push in obexftp/client.h to use direct
> obexftp_connect_src (and not obexftp_connect_uuid) receiving the hci
> as parameter.

regards,
Christian




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Openobex-users mailing list
Openobex-users@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/openobex-users

Reply via email to