Problems with FlxSave about flixel HOT 7 CLOSED

THanks for the feedback! I've updated FlxSave to return booleans and allow you to set a minimum file size too, should be uploaded asap

from flixel.

Great :) I read a bit on the matter, and there's two things I'd like to note:

1. Not sure if there's any difference, but the example I saw said that SharedObject.flush throws an exception and returns a String on failure, not a Boolean, so it used a try ... catch instead of comparing it to true.
2. It is also possible for SharedObject.getLocal to throw an exception (such as when the user has disabled third-party shared objects), so I also made a second layer of protection there by adding a boolean property "valid" to the class, catching any exception thrown by getLocal on the constructor and setting valid to false if anything went wrong. Then any other method that makes use of the shared object, returns right away if the shared object isn't valid in the first place.

from flixel.

Source: http://www.adobe.com/livedocs/flex/3/langref/flash/net/SharedObject.html

from flixel.

And sorry for the triple post, but just noticed:

Shouldn't "MinFileSize:uint=0" also be added to the methods that make use of forceSave (write and erase) ? Because usually forceSave isn't even used directly but rather through the other two methods.

from flixel.

Yea right on both points, I'll upload some tweaks in a few minutes!

from flixel.

Ok pushed up some new codes, you need to call bind() now before you can call write() or read(), Mode has been updated accordingly

from flixel.

You're the man :)

from flixel.