From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH 2/2] ui responsiveness tweaks
Date: Thu, 03 Sep 2009 10:58:16 -0700 [thread overview]
Message-ID: <1252000456-sup-1452@masanjin.net> (raw)
In-Reply-To: <1251053171-11450-2-git-send-email-rlane@club.cc.cmu.edu>
Both of these patches are on the branch preemptive-loading, merged into
next. Thanks! It's a nice touch.
I didn't really notice any differe from thread prioritization and
Thread.pass call, but maybe that's my setup. Regardless, it can't hurt.
I also reworked the load-more callback mechanism to be a little more
thread safe and a little less insane. Now it uses a queue and has a
dedicated loader thread pulling things off of it. Message thread loading
is currently configured to just drop concurrent calls, so it should work
fine.
Now, all we need is a faster cursor in thread-index-mode. I will grant a
Sup medal to anyone who can make that happen!
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-09-03 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 18:46 [sup-talk] [PATCH 1/2] preemptively load messages when scrolling Rich Lane
2009-08-23 18:46 ` [sup-talk] [PATCH 2/2] ui responsiveness tweaks Rich Lane
2009-08-26 21:15 ` Carl Worth
2009-08-27 2:54 ` Ingmar Vanhassel
2009-09-02 3:59 ` Rich Lane
2009-09-03 17:58 ` William Morgan [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=1252000456-sup-1452@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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