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

[BUG] Bridge saves file improperly on Linux #129

Closed
CollinScripter opened this issue Dec 22, 2019 · 4 comments
Closed

[BUG] Bridge saves file improperly on Linux #129

CollinScripter opened this issue Dec 22, 2019 · 4 comments
Labels
Bug Something isn't working High Priority

Comments

@CollinScripter
Copy link

Summary
After creating a project, saving a file results in the file being saved in an incorrect file path.

To Reproduce
Steps to reproduce the behavior:

  1. Launch the Bridge AppImage on Linux
  2. Create a new pack
  3. Create and/or modify a file
  4. Save the file
  5. Observe resulting file in folder where bridge was launched

Observed behavior
When saving a modified file, the file is saved in the current directory with the name of the file path where it should have been saved, with inverted slashes.
Expected behavior
When saving a modified file, the file is saved in /home/username/.local/share/mcpelauncher/games/com.mojang/development_behavior_packs/

Screenshots / File Attachments
Bridge File Save

Platform:

  • OS: Kubuntu 19.10
  • App Version: 0.13.32 (AppImage)

Additional context
Linux file paths use forward slashes, not back slashes. The initial pack files are created in the proper locations, the bug only happens with user saved files.

@CollinScripter CollinScripter added the Bug Something isn't working label Dec 22, 2019
@solvedDev solvedDev reopened this Dec 22, 2019
@solvedDev
Copy link
Member

solvedDev commented Dec 22, 2019

The above commit probably fixes this issue. I am not sure whether removing this legacy code line breaks logic elsewhere inside of the app though. That's why I didn't remove it before... Gonna need some more testing before I publish a version with this fix

@solvedDev
Copy link
Member

v0.13.33 has the potential fix in it. Let me know whether the problem still occurs :)

@CollinScripter
Copy link
Author

Seems to work fine. Thanks!

@solvedDev
Copy link
Member

Thanks for the report! :D

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

No branches or pull requests

2 participants