🚀 go-pugleaf

Thanks Rich and Max.  I'll try the wiggle (in keeping with the coffee motif,
perhaps it should be "percolate").  I've since found this issue as a bug in
Sun's Bug Parade.  It is currently closed because, I believe, it was not
reproducible.  According to other posters in Bug Parade, this only shows up
when the jList is populated "on the fly" i.e. after the component is first
painted without items in it and then the items are added.  I've tried to
re-open the bug and have posted code to reproduce it.
Thanks again.
-J

Max Polk wrote:

> In article <35E6CE5A.4B8F8D1D@inprise.com>, rwilkman@inprise.com says...
> > ...
> > I suspect all JFC programmers have sets of "wiggle" code like that to
> > coax the UI to look right.
> > ...
>
> A friend, having used JBuilder for a while, was astounded that I could do
> in no time using C++Builder what would take quite a while in JBuilder.
> And no "wiggle" code.
>
> I'm not blaming JBuilder -- one of the best (if not *THE* best) product
> out there today.  I'm just musing about the newness of Java.  Sun doesn't
> document the components that well.
>
> The "feel" of C++Builder and its quick responsiveness and sturdy
> components, based on a very old product (Win32 API) that has undergone
> numerous revision since the early days of Windows (1.x, 2.x, etc), makes
> it a bit faster, in my opinion, than JBuilder.  And it's well documented.
>
> And probably half the difference in speed was simply knowing the
> components in C++Builder so well, and all of us being pretty new to Java
> (what is it, three years now?)