This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
swt fileviewer
- From: "Erik Poupaert" <erik dot poupaert at chello dot be>
- To: "John Murga" <john at murga dot org>
- Cc: <java at gcc dot gnu dot org>
- Date: Sat, 4 Jan 2003 15:03:07 +0100
- Subject: swt fileviewer
>>>> I think the problem I had with the file manager was just with a weird
event
>>>> loop... the thread stuff and inner classes seems to work fine.
The first thing that starts flying around is:
//X private static final DateFormat dateFormat =
DateFormat.getDateTimeInstance(
//X DateFormat.MEDIUM, DateFormat.MEDIUM);
DateFormat is implemented in terms of SimpleDateFormat, which does (lines
209, 226) a plain getInstance(); already known not to work, at present, in
minGW/gcj. That was actually rather easy to disable.
Fileviewer.exe then manages to start up and enter its initial stage. It
doesn't work properly, however. Trying to move up to a parent directory, and
certainly "refresh" does some threading that runs out of control:
Exception in thread "Thread-1" org.eclipse.swt.SWTException: Widget is
disposed
Exception in thread "main" org.eclipse.swt.SWTException: Widget is disposed
Maybe one of the UnsupportedOperationException(JvNewStringLatin1
("Thread.xxx unimplemented")) exceptions in natRuntime.cc is masked by one
of the above? Don't know. When it will become possible to recompile GCJ
natively with debug information, I would want to re-visit this. It may
become quite interesting, but certainly not easy. I guess that will be some
time after 3.3.