Negative frameCount in Sprite Sheet giving error

The documentation says the following:

“If frameCount is negative, the sequence starts playing backwards. For example, startFrame = 3 and frameCount = -3 will play frames in a 3, 2, 1 order.”

Yet when I try doing that I’m getting the following error:

Runtime error
sequence frames must be inside the sheet

If I use a positive number it works fine, but I need to play the frames in the reverse order and so far I can’t get it to work. Any suggestions? [import]uid: 10835 topic_id: 3848 reply_id: 303848[/import]

-3 would bring the frame to less than the number of frames. I think you should try -2 so it stops on frame 1. [import]uid: 11024 topic_id: 3848 reply_id: 11725[/import]

But then the documentation would be wrong! I think it’s critical to have accurate documentation and samples for something like Corona, that’s being marketed to beginners. I don’t have the necessary knowledge to identify mistakes in the docs (yet). Anyhow I think I tried with a smaller negative number, but still got an error. In the end I had to hack a different way to do it. [import]uid: 10835 topic_id: 3848 reply_id: 11805[/import]

It’s hard to comment without seeing the problematic line of code. [import]uid: 11024 topic_id: 3848 reply_id: 11807[/import]

I’m starting to implement spritesheets in my game and I’m having the same issue. The line that causes the error is

sprite.add(tileSet, "flipBack", 6, -3, 50, 1)  

If I delete the minus sign the error goes away, so clearly that specific bit is the problem.

The documentation he quoted above is located here:
http://developer.anscamobile.com/reference/sprite-sheets#sprite.add_spriteSet_startFlying_startFrame_frameCount_time_loopCount_

ADDITION: I just worked around this issue by duplicating the frames in the frame data sheet, but obviously having to manually copy/paste frames like this is far from ideal. If I ever have to adjust the spritesheet then I’ll have to redo this workaround. [import]uid: 12108 topic_id: 3848 reply_id: 15314[/import]

@IgnacioCultura
I believe it’s a bug from corona itself, check out SpriteGrabber discussion, I was trying to do the same thing. [import]uid: 11334 topic_id: 3848 reply_id: 15562[/import]

We’re aware of this longstanding bug. The internal tracking # is 3207. At the moment I don’t have any information about when it will be fixed, sorry! [import]uid: 6787 topic_id: 3848 reply_id: 30869[/import]