search

asafbibas / jmonkeyengine

Automatically exported from code.google.com/p/jmonkeyengine
0 stars 0 forks source link

Natives fail to be extracted to the user folder #453

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
In some instances the natives in the <user>\.jme3\ folder fail to be replaced 
properly.

Original issue reported on code.google.com by ShadowIs...@gmail.com on 13 Jan 2012 at 5:11

GoogleCodeExporter commented 8 years ago 
Is there any way to reproduce this issue?

Original comment by ShadowIs...@gmail.com on 2 Feb 2012 at 2:22

GoogleCodeExporter commented 8 years ago 
Hm, I guess by running an application in a read-only folder.

Original comment by normen667 on 2 Feb 2012 at 4:55

GoogleCodeExporter commented 8 years ago 
@Normen: When the application runs in a read-only folder, the <user>/.jme3 
folder is used. What I am asking is, under what circumstances can the natives 
fail to be replaced in that folder?

Original comment by ShadowIs...@gmail.com on 2 Feb 2012 at 5:58

GoogleCodeExporter commented 8 years ago 
Yes, and the failure only happens when that is the case, from then on I don't 
know, I do not own a messed up windows.

Original comment by normen667 on 2 Feb 2012 at 9:15

GoogleCodeExporter commented 8 years ago 
I am marking this issue as fixed since I have not heard of any reports of it 
recently. I believe it might have happened when a new version of jME3 ran on a 
PC where an old version was run on.

Original comment by ShadowIs...@gmail.com on 29 May 2012 at 1:19