From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] [PATCH] Title bar and status bar widget
Date: Mon, 12 Nov 2007 22:07:17 +0000 [thread overview]
Message-ID: <1194905177-sup-2828@tomsk> (raw)
In-Reply-To: <1194886848-sup-8236@south>
On 12.11.2007, William Morgan wrote:
> Actually I think the best would be to call the hooks before the lock,
> and pass in the values to actually be drawn into the locked code, so
> that the draw happens within the lock. It means adding a couple
> arguments to some of these methods, probably.
Attached is a patch for this. Not sure if this is the best way of
doing it as I've used accessors on buffer class rather than passing
args.
Marcus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: widget-diffs
Type: application/octet-stream
Size: 2692 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071112/a834f4e4/attachment.obj
next prev parent reply other threads:[~2007-11-12 22:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 10:44 Marcus Williams
2007-11-08 12:10 ` vasudeva
2007-11-09 7:40 ` Marcus Williams
2007-11-12 0:48 ` William Morgan
2007-11-12 9:23 ` Marcus Williams
2007-11-12 17:02 ` William Morgan
2007-11-12 22:07 ` Marcus Williams [this message]
2007-11-26 20:42 ` William Morgan
2007-11-26 20:45 ` Marcus Williams
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=1194905177-sup-2828@tomsk \
--to=marcus-sup@bar-coded.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