Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Saving file mangles the code and renderers it unreadable #45

Closed
GoogleCodeExporter opened this issue Mar 30, 2015 · 8 comments
Closed

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Load the .sol
2. Save the .sol
3. See the .sol become corrupted and unreadable by the game

What is the expected output? What do you see instead?
A working, changed .sol save file. A mangled, unreadable .sol save file.

What version of the product are you using? On what operating system?
The online version on windows 7 pro

Please provide any additional information below.
3.5 .air version works just fine and does not mangle the file.


Original issue reported on code.google.com by Garz...@gmail.com on 25 Sep 2014 at 3:50

Attachments:

@GoogleCodeExporter
Copy link
Author

Loading the changed file in the .air 3.5 version shows how mangled the file is.

Original comment by Garz...@gmail.com on 25 Sep 2014 at 3:51

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

The issue here is how complex your file is. And how the flash player handles 
caching duplicate content. It's not well documented and it's more of guess work 
on my side. I'll take a look at it and see if i can do anything. Thanks

Original comment by gmariani405 on 20 Oct 2014 at 10:37

  • Changed state: Accepted
  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

I'll be releasing an update this week that might resolve this issue. Stay tuned!

Original comment by gmariani405 on 21 Oct 2014 at 11:11

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Ok the site has been updated, ctrl-f5 to see the changes. let me know how it 
works

Original comment by gmariani405 on 21 Oct 2014 at 11:15

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

The save files are readable and changes(adding arrays, ect.) work fine now; 
takes about 15s for it to save, but hey, it works.

Original comment by Garz...@gmail.com on 22 Oct 2014 at 3:20

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Can confirm. And yea, hey it's JS, so that is to be expected.

Original comment by Martin.N...@gmail.com on 22 Oct 2014 at 3:41

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Added a save popup so you can tell it's doing something. Closing this ticket 
now.

Original comment by gmariani405 on 23 Oct 2014 at 2:36

  • Changed state: Verified
  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Issue 43 has been merged into this issue.

Original comment by gmariani405 on 22 Nov 2014 at 3:44

  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant