Resource folder Bug :/

kam187 · February 11, 2011, 10:59am

Hi,

I just tested 295 and it _still_ has the bug where all resources need to be in the root folder. I dont mean to be harsh but seriously, thats pretty bad and makes the product look a little unprofessional.

I’m still using 243, since 268 - the current “stable” has it too.

I’d appreciate it if you could give this some attention and get it fixed in the next drop.

Rant over.

Thanks. [import]uid: 8872 topic_id: 6424 reply_id: 306424[/import]

carlos_m_icaza · February 12, 2011, 11:25am

There is nothing we can do about that if you are using Android. It is what it is.
C. [import]uid: 24 topic_id: 6424 reply_id: 22405[/import]

kam187 · February 12, 2011, 2:55pm

That has to be the worst reply I’ve seen from an otherwitse good support.

If that’s the case why doesn’t 243 exhibit this bug?

Why is native code able to do it?

At the very least, in the interests of consistency from the corona sdk , why can’t the build process rename the files and arange them in root?

I mean that response just makes me angry. If you don’t want to take android support seriously just say so, or perhaps that’s exactly what you just did say [import]uid: 8872 topic_id: 6424 reply_id: 22451[/import]

carlos_m_icaza · February 12, 2011, 3:41pm

That did came across as gun blazing response !

I sent you an email

Apologies for the callous feedback

Me. [import]uid: 24 topic_id: 6424 reply_id: 22461[/import]

kam187 · February 12, 2011, 3:59pm

Hi.

Thanks, i got your email. That comment makes alot more sense in that context.

Seems like android is a bit of a mess right now! [import]uid: 8872 topic_id: 6424 reply_id: 22466[/import]

H4ch1 · February 13, 2011, 3:15am

It does this on iOs too, for images. It works if I simply write “folder/image.png”, but it doesn’t if I use the output of pathForFile, even though the path is correct. It does this with both resource and document directory, and is the documents one that I really need to use :\ [import]uid: 8486 topic_id: 6424 reply_id: 22546[/import]

mark.carolan · February 16, 2011, 4:39pm

@ H4ch1: if I understand your problem correctly, use the new syntax for loading/saving images, passing the path constant parameter baseDir, rather than using the path generated by pathForFile, which now only seems to work for IO file calls. Same with spritesheets. Docs have just been updated. [import]uid: 3953 topic_id: 6424 reply_id: 23362[/import]