Issues

Tab_Sel · Post by **Tab_Sel** » Fri Jan 24, 2014 3:07 pm

Jamstix saves files in the program folder, which leads to permission issues. For example when saving key map. Maybe offer a file save dialog?

Post by **Ralph @ Rayzoon** » Fri Jan 24, 2014 3:17 pm

This is one of the reasons we don't recommend installing to the 'Program Files' folder.

Tab_Sel · Post by **Tab_Sel** » Fri Jan 24, 2014 3:35 pm

That's why ms designed the appdata folder for and their whole security paradigm around its file/folder structure?

Can't it be designed conforming to ms windows design?

Post by **Ralph @ Rayzoon** » Fri Jan 24, 2014 4:03 pm

You are absolutely correct.

Jamstix OSX already follows that paradigm as it pertains to OSX (~/Library/Application Support). The Windows version will transition to the AppData folder with Jamstix 4.

However, please note that many Windows users prefer to store the Jamstix data on a 'fast streaming' drive and therefore specify an entirely different location anyway.

Tab_Sel · Post by **Tab_Sel** » Fri Jan 24, 2014 4:41 pm

Of course.
This is why plugin dll is installed into program files, content on a different location, specified by the user, defaulting to application support/appdata?

But I was talking about the files jamstix creates, like keymap. It's hardcoded to be created in the program files folder, resulting in permission failure. there sure is a way to at least ask the user where to create these files?

Post by **Ralph @ Rayzoon** » Fri Jan 24, 2014 5:37 pm

We don't want to split the Jamstix data location. It must remain one folder, which the user can move around, if need be, without losing any saved changes or additions.

The keymap saving is not hard-coded to 'Program Files'. It is hard-coded to the Jamstix data folder, which may be under PF or somewhere else.

Tab_Sel · Post by **Tab_Sel** » Sat Jan 25, 2014 2:11 am

Ok, thanks, so there sure is a short tutorial here in the forums on how to move Jamstixs data folder to appdata correctly?