|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Building a native executable with Eclipse 4.4 and e(fx)clispe [message #1462107 is a reply to message #1461928] |
Wed, 05 November 2014 02:58  |
Eclipse User |
|
|
|
Why are you using getResource("FXMLFILE").getPath() at all? The
FXMLLoader-API always wants an URL! Your useage of System.getProperty()
stuff also does not really make sense to me but maybe there is.
The problem with your getPath() call is that in the exported version you
are inside the JAR-Filesystem which is different to host filesystem in
many ways where the most prominent are:
* no relative parent paths e.g. ../bla.fxml does not work!
* cases sensitiveness where it is different to the windows-filesystem
Tom
On 05.11.14 04:18, Matthew Meehan wrote:
> I fixed it... so when I am getting all of my FXML files through
> this.getClass().getResource() that works fine BUT if you go
> this.getClass().getResource("").getPath() + "/data" it goes haywire
> outside of the development env.
> Also if a class extends one in another project it seems to want to look
> at the superclasses dir rather than the extended one but it didn't
> happen every time so slightly confused there.
> Anyway stopped using getResource.getPath()+"other string", just using a
> direct getResource.getPath("FXMLFILE") and when applicable used
> System.getProperty("user.dir") and things are now back on the road.
|
|
|
Powered by
FUDForum. Page generated in 0.55232 seconds