Re: AppleCommander bugs and glitches

["John B. Matthews" <nospam@nospam.invalid>]

In article <-tqdnfWxvJdQKH7QnZ2dnUVZ_vadnZ2d@giganews.com>,
 Steven Hirsch <snhirsch@gmail.com> wrote:

> > Let me know if you see something obvious. I've tried to tread 
> > gingerly on Rob's code largely to avoid breaking platforms that I 
> > don't use.
> 
> I'm about the last person you'd want picking through Java code, 
> unfortunately. I know enough about it to be dangerous, but not enough 
> to even have a clue how to rebuild and test any modifications.

I understand; it sounds like you have a work-around. I can do limited 
regression testing in emulation, but I don't have the resources for full 
development on linux. If I may ask: What version are you using? What 
package(s) did you install to meet the SWT dependency?

As an aside, I used your method to launch AppleCommander from the Mac OS 
command line, and it exhibited the same hang-on-exit anomaly reported 
here earlier. I suspect I've run afoul of the 32- to 64-bit transition, 
but the result is illuminating. Thanks. For reference:

cd AppleCommander.app/Contents/Resources/Java
java -d32 -XstartOnFirstThread -Dswt.library.path=. \
    -cp .:swt.jar:AppleCommander.jar \
    com.webcodepro.applecommander.ui.AppleCommander

-- 
John B. Matthews
trashgod at gmail dot com
<http://sites.google.com/site/drjohnbmatthews>