Closed Abe404 closed 1 year ago
Just had this issue with a student - error message said datasets were in the wrong directory but took us a while to figure out why. Only upon reading this issue did I realise that you had to specify the sync directory from the Extras menu.
Thanks for reporting this. I realise this sync directory stuff can be a bit of a hassle and I'd like to make it easier for users to fix it when it goes wrong (or for it to just not go wrong in the first place).
I've implemented the fix as described in this issue (see inserted screenshot):
This is in the master branch but is not in a release yet so I will leave this issue open for now.
I will also keep an eye out for other areas where I can make this sync directory management more intuitive.
Thanks for adding this extra text to the error message, would definitely solve the issue quite quickly.
Sometimes users want to start working with data in a different sync directory. They are not necessarily aware of how to update the sync directory (the option is in the extras menu).
When they create a project they receive a warning that the dataset they are using is not in the right sync directory (it's in the old sync directory and not the new one). At this point we could inform them that there may be an issue with the location of the specified sync directory and that they can update the location of the specified sync directory using the option from the extras menu.