From: Mark van Atten <vanattenmark@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] drawterm osx-x11 on x86_64
Date: Fri, 22 Nov 2013 10:18:47 +0100 [thread overview]
Message-ID: <CALAsyW2yF9z820cWZw+q_FuYfF14kTDy+4nWvhMrPBx27Nmo2w@mail.gmail.com> (raw)
In-Reply-To: <CALAsyW10poTm++1OSK7ObTVBvh8qhQdM=qke4_hPG61ftTmYsg@mail.gmail.com>
Well, I wrote `the current sources', but that was wrong: I just
checked bitbucket again and saw your commits of the last few hours. So
I pulled the updates and rebuilt. To my surprise, the phenomena remain
exactly the same. This time I got a message though:
objc[3785]: Object 0x7fb261297930 of class NSConcreteMapTable
autoreleased with no pool in place - just leaking - break on
objc_autoreleaseNoPool() to debug
Mark.
On Fri, Nov 22, 2013 at 10:05 AM, Mark van Atten <vanattenmark@gmail.com> wrote:
> On Fri, Nov 22, 2013 at 1:02 AM, Jeff Sickel <jas@corpus-callosum.com> wrote:
>
>> Will one of you describe the flicker you speak of? I see flicker on
>> Linux’s drawterm X11 when resizing rio windows and other operations,
>> given the round trip time, though the flicker is less on fast local
>> networks.
>
> You are right, of course, that the presence of flicker may depend on
> various things, and my original message was too elliptic.
>
> I drawterm only to a virtual machine on the same computer.
>
> My setup: Mac Mini Late 2012 with 10.8.5. Virtual machine: Virtualbox
> 4.3.0, Bell Labs iso, 1024MB system memory, VT-x/AMD-V and Nested
> Paging on, 32 MB video memory, Intel PRO/1000 MT Desktop bridged
> adapter en1 Wi-Fi (AirPort). Mountain Lion's DHCP server enabled.
>
> Drawterm for osx-x11 built from the current sources at
> http://code.google.com/p/drawterm/
> Drawterm for osx-cocoa built from the current sources at
> https://bitbucket.org/jas/drawterm-cocoa
>
> In the cocoa version, when sweeping a rio window all borders will
> flicker continuously. On resizing with B1 or B2, in addition to the
> flicker, border lines will fail to meet or meet but not at the
> corner. All this independently of window size and sweep speed. When
> creating a new window in sam, three or all corners always break open a
> little.
>
> In the x11 version, when sweeping normally, there will be no flicker
> at any size, and, when sweeping quickly, flicker on one side only (the
> side where the mouse pointer is). I haven't seen border lines fail to
> meet or meet at the wrong place, whether in rio or in sam.
>
> Mark.
next prev parent reply other threads:[~2013-11-22 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 10:40 Mark van Atten
2013-11-21 14:58 ` Jeff Sickel
2013-11-21 15:16 ` erik quanstrom
2013-11-21 15:03 ` Steven Stallion
2013-11-21 15:54 ` Jeff Sickel
2013-11-22 0:02 ` Jeff Sickel
2013-11-22 9:05 ` Mark van Atten
2013-11-22 9:18 ` Mark van Atten [this message]
2013-11-25 16:12 ` Jeff Sickel
2013-11-25 17:44 ` Mark van Atten
2013-11-26 14:36 ` Mark van Atten
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=CALAsyW2yF9z820cWZw+q_FuYfF14kTDy+4nWvhMrPBx27Nmo2w@mail.gmail.com \
--to=vanattenmark@gmail.com \
--cc=9fans@9fans.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).