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

Having Trouble Saving Anything #44

Closed
desplesda opened this issue Sep 18, 2019 · 7 comments
Closed

Having Trouble Saving Anything #44

desplesda opened this issue Sep 18, 2019 · 7 comments
Labels
bug Something isn't working

Comments

@desplesda
Copy link
Collaborator

Issue by RyokiRayn
Thursday Feb 16, 2017 at 01:35 GMT
Originally opened as InfiniteAmmoInc/Yarn#44


So if I open Yarn in either NW.js or my browser, I can write out the dialogue tree I'm working on just fine, but whenever I go to save I get the four file type options but none of them save anything. In NW.js, if I click save as _____ it opens a separate window with a word document of my tree in it and will not save the file type I request.

@desplesda desplesda added the bug Something isn't working label Sep 18, 2019
@desplesda
Copy link
Collaborator Author

Comment by jettraverso
Wednesday Aug 02, 2017 at 16:34 GMT


My friend and I are using the browser editor, and we cannot save either. Is this a bug from a recent release?

@desplesda
Copy link
Collaborator Author

Comment by Klash120
Wednesday Aug 09, 2017 at 17:39 GMT


Ditto. Using Chrome. Disabling any Adblocker seems to allow saving. Though, nothing will load now :x

@desplesda
Copy link
Collaborator Author

Comment by charblar
Wednesday Jun 13, 2018 at 02:32 GMT


Confirmed, unable to reproduce workaround mentioned by @Klash120. Will readdress after finishing electron port.

@desplesda
Copy link
Collaborator Author

Comment by blurymind
Monday Aug 13, 2018 at 07:40 GMT


@RyokiRayn does that also happen in the electron version?

@blurymind
Copy link
Owner

can you confirm if this bug still persists?

@daviddq
Copy link
Contributor

daviddq commented Jun 11, 2020

What's the current state of this issue? Can we close it?

@blurymind
Copy link
Owner

This bug is quite ancient and the guy who reported it hasnt responded for a year. I think its safe to close it. Someone will reopen the issue if it happens again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants