Re: What's the thread model on Linux?

2001-05-23 Thread Kero van Gelder
But what I found is that kaffe cannot even support 200 users. Interesting! Only the unix-jthreads code gets tested and used a lot, so I wouldn't be too surprised that unix-pthreads can't keep up with unix-jthreads. In any event, the unix-pthreads code should be able to support more

Focus bug

2001-03-24 Thread Kero van Gelder
Hi all, I have a Frame that contains a Canvas, two Scrollbar's and a Label. When I create the Frame, I let the Canvas request focus. It gets it. However, whenever focus is lost to the Frame, the Canvas does not receive focus back again. This is due to the fact that when the mentioned Frame

Layout bug

2001-03-22 Thread Kero van Gelder
Hello all, A bug in the GridLayout manager causes it not to layout when the Container has no children. No check is performed (neither is it in most other managers I suppose), but dividing width by the number of columns is a bad idea... I added a simple check, patch onto cvs (dd 11 March)

Layout bug

2001-03-22 Thread Kero van Gelder
Hm, patch attached now... +--- Kero - [EMAIL PROTECTED] ---+ | Don't split your mentality without thinking twice | | Proud like a God -- Guano Apes | +--- M38c -- http://huizen.dds.nl/~kero ---+ ---

Re: Last Frame disposed; all threads dead?

2000-05-26 Thread Kero van Gelder
Didn't we have this discussion before? I did a short search in the archives, but it is a bit hard to find in the long lists. Have you tried the java.awt.Defaults.AutoStop property? The what? A short look gives me java.awt.Defaults in Kaffe, but not in Sun's API. /** * If set to

Last Frame disposed; all threads dead?

2000-05-25 Thread Kero van Gelder
Hello all, When the last Frame is dispose()d, the prompt returns. I assume all threads die when the last Frame is dispose()d. That's nice, but I am trying to catch the windowClosed() event. From that, I call my own quit() method. It is never reached. It is contrary to Sun behaviour: when using

Re: BufferedInputReader

1999-12-22 Thread Kero van Gelder
I encountered a small problem using the BufferedInputStream. When telling it to skip a big number of bytes, it stops at the first 2k boundary (or, more precisely, from position 32 to skip 37919 bytes lets it stop at position 2048). This is not a bug. The skip() method as defined in

BufferedInputReader

1999-12-21 Thread Kero van Gelder
Hi all! I encountered a small problem using the BufferedInputStream. When telling it to skip a big number of bytes, it stops at the first 2k boundary (or, more precisely, from position 32 to skip 37919 bytes lets it stop at position 2048). Removing the BufferedInputStream and using only the