Comments on: Air file.nativePath Vs. file.url

By: starlover

starlover — Fri, 15 Jul 2011 09:54:31 +0000

And?? Did you miss something?

I too ran into the problem that my images did not load on a mac when i use nativepath as saved image urls.

Can i safely use url instead?

By: Chris Dennett

Chris Dennett — Wed, 06 Oct 2010 20:42:39 +0000

Thank you for this. Swapping .nativePath for .url has now made me all Mac compatible which gives me a nice warm feeling inside… or that may be the wine. But either way, thank you for your post, you’re a wonderful person.

By: deRijk

deRijk — Wed, 10 Mar 2010 13:22:01 +0000

This saved my day Arno.

By: ovaseethell

ovaseethell — Tue, 15 Dec 2009 02:48:41 +0000

Howdy – This is a great place

Just registered and wanted to say hello.

By: Arno Manders

Arno Manders — Thu, 08 May 2008 18:42:54 +0000

that sounds like a reasonable purpose to use nativePath. But why are the people of those scripts using file.nativePath instead of file.url?

By: Greg

Greg — Thu, 08 May 2008 18:22:35 +0000

The nativePath is formatted to a path the average user understands. Some users might see file:///C:/Program Files/… on windows and say: huh?

nativePath would read so they see C:\Program Files\… which would make sense to them.

I’ve always used nativePath when displaying a filepath to a user (like depicting a file they’ve chosen), and a url when you are loading that content into an Image component or something.

By: Quentin

Quentin — Thu, 08 May 2008 16:15:31 +0000

I was wondering the exact same thing…
If someone has a clue!