I use JBuilder3 and I've never had a problem finding configuration files
from the initial project directory. In other words, wherever the class that
contains the main(String[] args) I have been able to reference paths based
upon it.(e.g ./ ../ ../images ../models etc.)
Did you properly set up your creation paths for the project? When you
create a project in JB3, it wants to create everything in the myprojects
directory. So if you create your project in another directory you still
have to set the projects input/output file directories to match your
creation directory. Otherwise the project defaults cause all of your files
to be created in the myprojects directory...it will compile fine because of
the dependency checker in JB3, but when you try to run it if your config
files are not in the myprojects directory it will fail.
Anyway, I use JB3 for Java3D and it works like a champ.
>JBuilder v3's debugger uses the Sun JDK with the new debugger hooks, so
>this is not a problem. Seems to work great with Java3D.
It does
>
>However, I have stopped using JBuilder because
>there is minor bug in 3.0 that makes it unusable for me. When an
>application is run or debugged under JBuilder, the initial directory of
>the process is random within the classpath (as opposed to always starting
>at the location of the project file, as happened in JBuilder 2). So if
>you intend to read in configuration files relative to the local directory,
>the system is useless.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
