The examples readme doesn't explain how to run the examples properly

[FSMaxB]

The readme is missing the information that you need to run the cargo commands from the project root.

I found this out because even though the sprite example runs when running cargo from the examples directory, it doesn't actually display the sprite because the relative path is from the project root, so it needs to be run from the project root.

It would be great if this could be explained in the examples README.

[lberrymage]

This should be closed in light of #471 merging

[cart]

Good call!

[cart]

Actually wait this seems like a separate issue. That pr fixes a broken command. This issue points out that assets only work correctly when run from the project root.

[lberrymage]

Oh gotcha gotcha. I can work on fixing that; we probably only need to add

env!("CARGO_MANIFEST_DIR")

to the asset paths.

[cart]

interestingly we already do that for the root path:

Although I think someone mentioned that we don't currently use root path when loading assets directly 😄

[lberrymage]

Huh... I don't if we would want to use the root path in case the user wants to load from an arbitrary directory, but also I don't know if the asset server is intended to be used with a single asset directory. That would make the most sense from a usage perspective at least; a change in .load()s behavior might not actually break that much since people typically have all their assets in one directory.

Not sure if you were implying that we might want to change AssetServer::load()s behavior, but I thought I'd bring it up in case you were leaning in that direction. Of course it's just as easy to manually load from CARGO_MANIFEST_DIR in the examples to solve this particular problem 😉.

[cart]

I think we actually want well-defined (or at least scoped) asset paths, as some platforms require that. I think its natural to restrict loads to the root path.

[lberrymage]

That makes sense. I'll can whip up a PR pretty soon here.

[FSMaxB]

This is great. At first I just had a change to the README in mind, but this fix is much better!