public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Roger C. Soares" <rogersoares@intelinet•com.br>
To: "Shawn O. Pearce" <spearce@spearce•org>
Cc: git@vger•kernel.org, robin.rosenberg@dewire•com
Subject: Re: [EGIT PATCH 1/4] Change history page table to SWT.VIRTUAL.
Date: Tue, 01 Apr 2008 00:25:15 -0300	[thread overview]
Message-ID: <47F1AB1B.90309@intelinet.com.br> (raw)
In-Reply-To: <20080331053430.GJ10274@spearce.org>


Shawn O. Pearce escreveu:
> Yea, I originally wrote my series around the VIRTUAL flag but on
> Win32 it caused ArrayIndexOutOfBoundsExceptions to be thrown from
> deep down within the Win32 implementation of the SWT Table widget.
>
> Appears to be something of a known bug, based on the Eclipse issue
> tracker, but not much work happening to fix it.
>   
Hum, a VIRTUAL table sounds like a very usefull feature to be badly 
broken on windows, at least there should be some workaround... is it 
easily reproducible?


> I'll retest this tomorrow on Win32, but I'm pretty certain its
> a bad idea on that platform.  What are you running on, Linux?
> Maybe we can set this flag everywhere except on Win32
Yep, linux.

Maybe another option to try before leaving windows out is the 
ILazyContentProvider. Have you noticed that while GenerateHistoryJob is 
updating the table you can't use it? Because the input is regenerated 
every time, the table keeps going back to the first row.

[]s,
Roger.

  reply	other threads:[~2008-04-01  3:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-30 15:18 [EGIT PATCH 1/4] Change history page table to SWT.VIRTUAL Roger C. Soares
2008-03-31  5:34 ` Shawn O. Pearce
2008-04-01  3:25   ` Roger C. Soares [this message]
2008-04-01  3:36     ` Shawn O. Pearce
2008-04-01  3:54       ` Roger C. Soares
2008-04-01  4:12         ` Shawn O. Pearce

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=47F1AB1B.90309@intelinet.com.br \
    --to=rogersoares@intelinet$(echo .)com.br \
    --cc=git@vger$(echo .)kernel.org \
    --cc=robin.rosenberg@dewire$(echo .)com \
    --cc=spearce@spearce$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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