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

Ecode deleting contents of files on windows #114

Closed
emeraldtip opened this issue Dec 26, 2023 · 2 comments
Closed

Ecode deleting contents of files on windows #114

emeraldtip opened this issue Dec 26, 2023 · 2 comments
Assignees
Labels
bug Something isn't working released windows Windows Operating System

Comments

@emeraldtip
Copy link

So I was editing some qlc showfiles for some lighting things in ecode (cause QLC has a horrible preshow configuring mode) and I tried to open the same file in 2 ecode windows at once and it just wiped the contents of the file completely. Luckily I still had qlc opened so I could overwrite the deletion. When I closed all ecode windows after that and reopened the file in ecode it deleted the contents again.

Video:

ecodebreak.mp4

If I just open the folder in ecode and then navigate to the file from inside ecode, everything works just fine.
Is this an issue with storing the last state of ecode?

@SpartanJ
Copy link
Owner

I think it's not being able to load the file because it's locked or some crappy Window thingy, the file is not empty. I'll try to reproduce it, thanks!

@SpartanJ SpartanJ self-assigned this Dec 26, 2023
@SpartanJ SpartanJ added bug Something isn't working windows Windows Operating System labels Dec 26, 2023
SpartanJ added a commit to SpartanJ/eepp that referenced this issue Jan 2, 2024
@SpartanJ
Copy link
Owner

SpartanJ commented Jan 2, 2024

Ok, the bug does not have to do with the file being open or nothing like that, the bug is that the file path is not properly parsed and believes that the file does not exists, in consequence creates a new empty file with that name. So I was wrong, the file is empty. Basically it will happen with any file opened from the file explorer with ecode that contains non ASCII characters. This is an important bug, I think may release a small bugfix version soon.
I already pushed a fix here.

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

No branches or pull requests

2 participants