Oh, and that folder DOES exist, and is not visualized, but its hidden attribute is set. One of the first things I do on my windows machines is change settings so that extensions show, and hidden files show.
On Thu, Jul 9, 2015 at 6:01 AM, Mike Bonner <[email protected]> wrote: > Hmm, did you try to write to it? Its writeable to me from LC. I set the > folder to the specialfolder path, and popped some data into a file and it > worked fine. From my reading, that that is the folders purpose. > > If you notice when you check the properties of the folder, the "read only" > is a greyed out (ok, blue'd out) box, not a check. (DON'T change it!) > meaning the folder itself is read only so you can't change it,but is > actually writable. If its checked, that sets the contents of the folder to > read only. > If the folder has been messed with, the only way to fix it is take the > check out (so that the contents are not read only) and then set the read > only attribute on the folder itself from the command line. > > By default though, the folder is set up correctly to be writable. > > On Thu, Jul 9, 2015 at 5:34 AM, Tiemo Hollmann TB <[email protected]> > wrote: > >> Hi Mike, >> just noticed, that specialfolderpath("0x0023") is the same as my up to >> now used specialfolderpath("35"), which was on XP C:\Documents and >> Settings\All Users\ApplicationData. On Win Vista and above this path >> doesn't exists anymore and now is C:\ProgramData, which obviously hasn't >> write permission anymore on all users and gets virtualized, when trying to >> write to it. >> So probably what Peter said, following the windows security guidelines, >> there isn't anymore any "all users" write directory for app data,. >> Tiemo >> >> >> -----Ursprüngliche Nachricht----- >> Von: use-livecode [mailto:[email protected]] Im >> Auftrag von Mike Bonner >> Gesendet: Dienstag, 7. Juli 2015 14:47 >> An: How to use LiveCode >> Betreff: Re: Where to put on windows an option file accessable for all >> users? >> >> you might try specialfolderpath("0x0023") which is the common app data >> folder. (app data for all users). I can't test on xp. On vista/7 the >> directory is c:\ProgramData On xp it should be c:\Documents and >> Settings\All Users\ApplicationData >> >> You'll probably want to create a subfolder for your app of course. >> >> On Tue, Jul 7, 2015 at 4:30 AM, Tiemo Hollmann TB <[email protected]> >> wrote: >> >> > Thank you for your helpful thoughts. >> > >> > How would I differentiate the access to these two different option sets? >> > On a private computer where the user usually is logged in as an admin >> > I would have to offer both option sets. In a school, depending on the >> > log-in the appropriate options. But I never have seen a chance in >> > LiveCode to ask for the user privileges (on Win and Mac) to be able to >> differentiate it. >> > How is this usually be done? >> > Tiemo >> > >> > -----Ursprüngliche Nachricht----- >> > Von: use-livecode [mailto:[email protected]] Im >> > Auftrag von Peter TB Brett >> > Gesendet: Dienstag, 7. Juli 2015 12:17 >> > An: How to use LiveCode >> > Betreff: Re: Where to put on windows an option file accessable for all >> > users? >> > >> > On 2015-07-07 11:08, Tiemo Hollmann TB wrote: >> > > Hi Peter, >> > > >> > > hmmm, never thought about that it could be a design fault. >> > > >> > > Beside real user based options I keep some general options in my >> > > option file, like the path to video files, or a flag if the software >> > > should look automatically for updates. If I think about schools, >> > > where different users can log in the same computer, that’s why I >> > > wanted to keep one option file for all users. >> > > >> > > But if I follow your hint, I would have to split this option file >> > > into an "admin-options-file", which is only accessible for the admin >> > > and a "user-options-file", which is stored in the user files. >> > > >> > > Would you agree to this approach or do you see a chance to keep a >> > > single options file which works in multi-user environments as on a >> > > private single-user computer? >> > >> > Yes, that would be exactly the way I would recommend to structure >> things. >> > You could think of it as follows: >> > >> > 1. Settings that relate to the way the program is installed on the >> > system (e.g. the video files' path, or whether to install updates) -- >> > these are the "per-system" settings and should be controlled by the >> > administrator only. >> > >> > 2. Settings that relate to the way the program is used (e.g. "enable >> > the colour scheme for colour-blind users") -- these are the "per-user" >> > settings and should be controlled (and stored) by each user. >> > >> > It is sometimes a little bit difficult to think about at first. >> > However, dividing the settings in this way means that one user can't >> > mess things up for another user, or interfere with settings that the >> > system administrator has put in for a good reason. :-) >> > >> > The separation of "user" and "system" settings is the recommended way >> > to structure things on most systems nowadays, especially Windows and >> Linux. >> > >> > Don't forget that when you have a single-user computer, you can just >> > treat it as a multi-user computer with one user! >> > >> > Peter >> > >> > -- >> > Dr Peter Brett <[email protected]> LiveCode Engine Development >> > Team >> > >> > >> > _______________________________________________ >> > use-livecode mailing list >> > [email protected] >> > Please visit this url to subscribe, unsubscribe and manage your >> > subscription preferences: >> > http://lists.runrev.com/mailman/listinfo/use-livecode >> > >> > >> > _______________________________________________ >> > use-livecode mailing list >> > [email protected] >> > Please visit this url to subscribe, unsubscribe and manage your >> > subscription preferences: >> > http://lists.runrev.com/mailman/listinfo/use-livecode >> > >> _______________________________________________ >> use-livecode mailing list >> [email protected] >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> >> >> _______________________________________________ >> use-livecode mailing list >> [email protected] >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > > _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
