[Fwd: Re: [java-dev] [Fwd: A strange error...]]

Hi,


sorry, I hadn't had internet for a few days. My solution was to modify 
this code:

File settings = new File ( Constants.SETTINGS_FILE );

to this new one:

File settings = new File ( System.getProperty ( "user.dir" ), 
Constants.SETTINGS_FILE );

and now everything works. The strange is, that the documentation page 
for java.io.File says that the first constructor I used resolves the 
given relative path against the current user directory, which can be 
accessed with System.getProperty ( "user.dir" ). This means that 
formally the two constructors should give the same result. So, maybe 
this is a JVM bug...


Bye,
Adam


________________
Siska Ádám
+36 (70) 207-63-85
http://apocalypse.rulez.org/~sadam


topher lafata wrote:
> Hey Siska,
> I am not sure what is going on then. It works for me over here.
>
> One other last gasp  alternative is for you to name
> your settings file something unique and use MaxSystem.locate file.
>
> ciao
> t
>
> On Jul 3, 2007, at 03:28 AM, Siska Ádám wrote:
>
>> Yes. I have a test patch that is never being modified, it just has 
>> the mxj with a reference to the class I'm writing. I quit every time 
>> Max before rebuilding the jar archive that has the class I'm 
>> developing. I'm using the normal Max, not Max Runtime. My version is 
>> 4.6.3. I build the jar with Eclipse 3.2.2.
>>
>> Thank you,
>> Adam
>>
>> ________________
>> Siska Ádám
>> +36 (70) 207-63-85
>> http://apocalypse.rulez.org/~sadam
>>
>> topher lafata wrote:
>> > Was your patcher saved when you tried getParentPatcher method?
>> >
>>
>> _______________________________________________
>> java-dev mailing list
>> java-dev at cycling74.com
>> http://www.cycling74.com/mailman/listinfo/java-dev
>
>