From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [edbrowse-dev] dataset / offsetWidth
Date: Sun, 16 Jun 2019 12:21:55 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1906161216050.37405@carhart.net> (raw)
In-Reply-To: <20190516144455.eklhad@comcast.net>
> That looks ok, do you want me to code or do you want to code and make a
pull request.
I'll do this now. The files affected are decorate and startwindow.
> set_property_string(dso, a[i]+5, u);
Ah! Even more concise. Thanks.
> But 1024 by 768 is prety heavy handed.
Oh yeah, good point. It should be just as happy with any positive number,
at least in the present scenario.
prev parent reply other threads:[~2019-06-16 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 16:24 Kevin Carhart
2019-06-16 18:44 ` Karl Dahlke
2019-06-16 19:21 ` Kevin Carhart [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=alpine.DEB.2.21.1906161216050.37405@carhart.net \
--to=kevin@carhart.net \
--cc=edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.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;
as well as URLs for NNTP newsgroup(s).