Skip to content

Conversation

SandTripper
Copy link

Problem Scope

If the user opens a path that is a server or other paths, the original logic fails to locate textures and model_path correctly. The issue stems from coupling the workspace concept with VSCode's workspace area.

Changes Made

I modified the existing logic to decouple workspace detection from VSCode's workspace concept. Instead, I now retrieve the workspace path alongside the namespace retrieval process. This ensures that we obtain the actual IA workspace path, which allows the system to correctly locate textures and model_path regardless of how the user accesses the application.

@LoneDev6
Copy link
Contributor

Thank you!
Do you think this is stable enough? Did you do some testing with common configurations?

@SandTripper
Copy link
Author

Thank you! Do you think this is stable enough? Did you do some testing with common configurations?

You're welcome! Yes, I've tested various scenarios and configurations, and the system appears to be stable. The testing covered common use cases and different settings, and everything functioned normally.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants