public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Vinicius Gomes <vinicius.gomes@openbossa.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: No way to cancel SendFiles() in obexd
Date: Mon, 14 Dec 2009 19:16:13 +0000	[thread overview]
Message-ID: <1260818173.3311.6022.camel@localhost.localdomain> (raw)
In-Reply-To: <2a9506370912141044s2f5ed846ub2072b0d378d7a11@mail.gmail.com>

On Mon, 2009-12-14 at 15:44 -0300, Vinicius Gomes wrote:
> Hi Bastien,
> 
> On Mon, Dec 14, 2009 at 2:01 PM, Bastien Nocera <hadess@hadess.net> wrote:
> > Heya,
> >
> > I have a slight problem with SendFiles().
> >
> > When sending multiple files, and refusing one of them on the phone, the
> > subsequent files are still sent.
> >
> > Is there a way to avoid that? Or should I rework the UI slightly to
> > mention that some files were not sent?
> >
> 
> As of now, there's no way to avoid that. Personally, I like the
> current behavior, at least, it is consistent with other tools, cp for
> example.

That's fine if you're implementing a command-line tool. Most UIs that do
copy will block until the user acknowledges the problem.

> > For a single file, you'll get a nice "retry" button if the phone refused
> > the connection. I'd prefer it if the agent could ask me whether to carry
> > on sending files, or cancel all the sending.
> >
> 
> Between those two options, I prefer cancel all the sending.

That would be fine by me, at least I can implement re-sending in some
way, even if it's not the way it currently works.

Marcel, what do you think?


      reply	other threads:[~2009-12-14 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 17:01 No way to cancel SendFiles() in obexd Bastien Nocera
2009-12-14 18:44 ` Vinicius Gomes
2009-12-14 19:16   ` Bastien Nocera [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1260818173.3311.6022.camel@localhost.localdomain \
    --to=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=vinicius.gomes@openbossa.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox