Open LordPatate opened 3 months ago
Does opening an existing project work?
It'll take me a bit to get to testing this because I run Linux and booting into Windows is a hassle, but I'll take a look into this
Does opening an existing project work?
I have no idea, I don't think I'm able to check since I don't have any existing project on my computer.
I found 8 results for a hardcoded string ".luminol/config" which is probably not the right way to join paths in Rust, right?
I see that the path.join(path)
method exists on several occurrences. I'm guessing that's how Luminol got the first part of the path right? (G:\\LuminolProjects\\.luminol/config
)
let path = self.root_path.join(path.as_ref());
The problem is a but more complicated than that- Luminol has an internal filesystem that's supposed to accept paths that either contain /
or \
(or a mix of both) and that seems to be breaking. Windows actually can handle /
paths, but it still hands out \
whenever querying what's inside a folder.
Interesting, opening a pre-existing project works just fine (even one without the .luminol folder)
Interesting, opening a pre-existing project works just fine (even one without the .luminol folder)
What if you try to save the pre-existing project that did not have .luminol folder? I suspect it will try to write the .luminol/config at save time.
Interesting, opening a pre-existing project works just fine (even one without the .luminol folder)
What if you try to save the pre-existing project that did not have .luminol folder? I suspect it will try to write the .luminol/config at save time.
It actually writes when opening a project without the config file present. This is because the editor has to guess the script path, which will tweak the project, and we'd rather guess the script path only once
Describe the bug
Creating a new project fails on Windows with message : "Error locating destination directory for project". I suspect the problem to be simply an UNIX-style path for the
.luminol/config
file instead of a platform-agnostic path.Trying to re-open the project will fail.
To Reproduce
Steps to reproduce the behavior:
Backtrace
When I tried re-opening the project:
Expected behavior
Creating a new project without errors :)
Desktop
Additional context
Just grabbed the windows build from the latest autobuild deployment pipeline.
I'm a developer, I'll try to take a look, see if I can find the problem and open a PR for it.