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

Config file folder does not exist on windows #618

Open
knmcguire opened this issue Jul 8, 2022 · 1 comment
Open

Config file folder does not exist on windows #618

knmcguire opened this issue Jul 8, 2022 · 1 comment

Comments

@knmcguire
Copy link
Member

The cfclient has a logblogs tab that can also save logging data on the go. This seem to fail on windows.

OS: Windows 11
Cfclient: latest master

How to recreate:
1- Connect to the crazyflie with the cfclient, start the logblock tab, and start logging of one of the logging variables:
2- The terminal says: INFO:cfclient.utils.logdatawriter:Started logging of block [sensors/magnetometer] to file [C:\Users...\AppData\Local\Bitcraze\cfclient\logdata\20220708T11-45-56\sensors-magnetometer-20220708T11-45-59.csv] or something similar.
3- If you go to that file, the folder doesn't exist.

Also the menu option 'go to config folder' does not seem to work either

@knmcguire knmcguire changed the title Logblog writing file fails on windows Config file folder does not exist on windows 11 Feb 15, 2023
@knmcguire knmcguire changed the title Config file folder does not exist on windows 11 Config file folder does not exist on windows Feb 20, 2023
@knmcguire
Copy link
Member Author

So we have done some research, and apparently, this happens when python is installed from the Windows Store, which is apparently in a different folder: C:\Users\USERNAME\AppData\Local\Packages\PYTHONVERSION\LocalCache\Local\Bitcraze\cfclient

https://stackoverflow.com/questions/15098751/where-does-windows-store-apps-stores-its-local-settings

This was very unclear as the Appdata module still opens the regular one: C:\Users\USERNAME\AppData\Local\Bitcraze\cfclient\ and it still does so for the config.

No clear solution for this but we should warn people with the installation instructions

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

No branches or pull requests

1 participant