From: Marcel Holtmann <marcel@holtmann.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Sort devices by type in the treeviews
Date: Mon, 27 Oct 2008 20:45:37 +0100 [thread overview]
Message-ID: <1225136737.7157.26.camel@californication> (raw)
In-Reply-To: <1225024770.1503.1398.camel@cookie.hadess.net>
Hi Bastien,
> Sorting by RSSI means that the devices just around in the treeview
> which is painfully annoying.
we want to sort by RSSI to list devices in range first. However we
should extend the sorting to always list already known or paired devices
first. This should stop them from moving around.
If it stil jumps too much for you, then we might just improve the
sorting mechanism to be a little bit more resistance for jumping around,
but sorting by type gives us no advantage.
Regards
Marcel
next prev parent reply other threads:[~2008-10-27 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 12:39 [PATCH] Sort devices by type in the treeviews Bastien Nocera
2008-10-27 19:45 ` Marcel Holtmann [this message]
2008-10-27 19:56 ` Bastien Nocera
2008-10-27 20:03 ` Marcel Holtmann
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=1225136737.7157.26.camel@californication \
--to=marcel@holtmann.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.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