[BUG]: Location of workspace folder

[fabiovinci]

Describe the bug
When I open a project by double-clicking the .halex file, the "workspace" folder is created in the same directory as the HALE project.
However, if I start the software and open the .halex project from within the application, the "workspace" folder used is the default one located in the AppData\Roaming\wetransform\HALE directory.

To Reproduce
Steps to reproduce the behaviour:

1. Go to the folder containing the .halex project
2. Click on the .halex file
3. Check that the folder with the project contains also the workspace folder

Expected behavior
The workspace folder that should be used must always be the default one.

Screenshots
If applicable, add screenshots to help explain your problem.

[florianesser]

Hi @fabiovinci, thanks for reaching out! I can't immediately reproduce the behaviour you observed with hale»studio 5.4.0 on Windows 10. Double-clicking a .halex or .halez does not create the workspace folder in the same directory for me.

To identify the source of the problem, it would be helpful if you could provide more details about your environment, i.e. hale version used, Windows version and if this is a first-time installation of hale or if you did in-place upgrades from previous versions.

If possible, please also provide the content of the Windows Registry key HKEY_CLASSES_ROOT\HALE.projectfile.xml\shell\open\command (e.g. using regedit). You should see something like C:\Program Files\wetransform\HALE\HALE.exe -data "%APPDATA%\wetransform\HALE" --launcher.openFile "%1".

[fabiovinci]

Hi @florianesser,

thank you for the quick response.

The version of hale is 5.4.0 installed on Windows 11 Home, and it was an upgrade from a previous version.
Recently, I installed, in addition, version 3.5 (same directory, C:\Program Files\wetransform, but in a different sub-folder).
After the installation of version 3.5, I had some difficulty selecting the default application for handling files with the .hale* extension.

The "command" key was not present in the Registry, I added it using the value you provided but the issue persists!