2016 22:10
An: use-livecode@lists.runrev.com
Betreff: Re: AW: Slightly] "Standard" file extension for a preferences file?
On 12/12/2016 12:58 PM, Tiemo Hollmann TB wrote:
> I don't know, what the "how to" standard would be. I am using an .xml
> file for my preferences
My understanding is that OS X prefs files are xml based but the file extension
is .plist.
Bob S
> On Dec 12, 2016, at 13:09 , Paul Dupuis wrote:
>
> On 12/12/2016 12:58 PM, Tiemo Hollmann TB wrote:
>> I don't know, what the "how to" standard would be. I am using an .xml file
>> for my prefer
On 12/12/2016 12:58 PM, Tiemo Hollmann TB wrote:
> I don't know, what the "how to" standard would be. I am using an .xml file
> for my preferences, because it's easy and safe to write and read.
> Tiemo
Just wanted to confirm you use a .xml file extension vs some other
extension on an XML file to ob
Gesendet: Montag, 12. Dezember 2016 17:50
An: How to use LiveCode
Betreff: [OT: Slightly] "Standard" file extension for a preferences file?
So, the debate of the morning here is: Is there a standard or common (most
frequently used) convention for the file extension for a preferences or
optio
.INI [Initialization File] or
.PRF [Preferences or Profile File] as well as the more common .TXT, or
.DAT. I have also see .prefs and .preferences in use.
I have also see a couple attempts are a "proprietary" extensions - for
example is a software products is called XYZ Writer, the p
downloaded 8.1.1 praying that the bug of the disappearing properties inspector
is fixed
nothing worked… preopenstack failed in the msg box. break points did nothing.
reverted to 8.1.1 RC2 same issues.
on a hunch
deleted /library/preferences/RunRev/livecode7.rev
rebooted 8.1.1 everything work
On Thu, Mar 31, 2016 at 5:43 AM, Mark Wieder wrote:
> Don't know why it wasn't there earlier today.
> Took the cats to the vet, came back, and there it was.
>
Mountain Lion was the last cat friendly OS X. ;-)
___
use-livecode mailing list
use-livecode@
On 03/30/2016 11:41 AM, Colin Holgate wrote:
/Users/mark/Library/Preferences/RunRev/livecode7.rev
Thanks. Don't know why it wasn't there earlier today.
Took the cats to the vet, came back, and there it was.
--
Mark Wieder
ahsoftw...@gmail.com
___
On 03/30/2016 11:37 AM, panagiotis merakos wrote:
Isn't it in /Users/username/Library/Preferences/RunRev/ ?
Interesting. That's where I was looking, and it wasn't there earlier.
Now it is. Thanks.
--
Mark Wieder
ahsoftw...@gmail.com
___
use-live
Seems to be here:
/Users/colin/Library/Preferences/RunRev/livecode7.rev
or maybe:
/Users/mark/Library/Preferences/RunRev/livecode7.rev
in your case.
Bit of OS X trivia: if you select the above text and right-click on it, you can
choose Reveal in Finder from the Services menu.
> On Mar 30, 2
Isn't it in /Users/username/Library/Preferences/RunRev/ ?
On 30 Mar 2016 19:26, "Mark Wieder" wrote:
> Having finally taken the plunge and upgraded to El Capitan, I'm having
> trouble locating the LC8 livecode7.rev preferences file. It's not where I
> expected i
Having finally taken the plunge and upgraded to El Capitan, I'm having
trouble locating the LC8 livecode7.rev preferences file. It's not where
I expected it to be. Can someone clue me in as to where to find it?
--
Mark Wieder
ahsoftw...
IMHO this is just kicking the security can down the road. If all developers are
required to keep their global preferences here, then instead of all the app
preferences being accessible from one now restricted location, they are all
available in another. What has really changed? This is what I do
This is true, however, other processes can elevate their privileges by
authenticating through a user/password dialog. Installers do this all the time.
What he is really asking for is a way to invoke the authentication dialog built
into the system, and then apply those privileges to his LC app.
Hi Andre,
Am 30.09.2012 um 22:02 schrieb Andre Garzia :
>> This works on the Mac:
>> specialfolderpath("asup") -> "~/Library/Application Support
>>
> Klaus,
>
> specialfolderpath("asup") returns the system wide Application Support
> folder and not the users Application Support folder. If you ar
On 09/30/2012 10:35 PM, Andre Garzia wrote:
Unless the person on the keyboard has an administrator level access or
password at hand, then you will not be able to write anywhere outside that
persons folder.Your unpriviledged user can't write to /Library or /System,
only the super user can.
Does
If the assistant has its own user on the machine and that user has no
priviledge outside its home folder than you will not be able to write to a
system wide location no matter what you try.
Unless the person on the keyboard has an administrator level access or
password at hand, then you will not b
On Sun, Sep 30, 2012 at 5:19 PM, Andre Garzia wrote:
> Haven't you seen my email above?
Yes, but . . .
> If running as a non-admin user you need to use:
>
> put "~" & specialfolderpath("asup") into tPath.
But this puts it in ~.
I'm after getting the system to request an admin password and put
Folks,
Haven't you seen my email above?
If running as a non-admin user you need to use:
put "~" & specialfolderpath("asup") into tPath.
The return value from specialFolderPath("asup") is the system wide support
folder which the normal user can't write to. You need the user folder which
you will
On Sun, Sep 30, 2012 at 12:48 PM, Klaus on-rev wrote:
>
> This works on the Mac:
> specialfolderpath("asup") -> "~/Library/Application Support
However, running as a user, when trying to create a directory within
it, "can't create that directory"
Is there a way to trigger the password request to
>
> A post in the forums a while back suggested that Apple's localization
> affects only the display of such folder names, while the actual addressable
> folder name remains constant.
>
> I don't have enough experience with Apple's localization to say for sure,
> but it would be convenient if someo
Phil Jimmieson wrote:
> On 30 Sep 2012, at 20:16, "J. Landman Gay" wrote:
>> There's been some discussion about whether Apple still wants
>> prefs stored in Preferences in Mountain Lion (odd as that may seem.)
>> To be safe on all versions of OS X, you may want to use this instead
>> for Macs:
>>
On 30 Sep 2012, at 20:16, "J. Landman Gay" wrote:
> There's been some discussion about whether Apple still wants prefs stored in
> Preferences in Mountain Lion (odd as that may seem.) To be safe on all
> versions of OS X, you may want to use this instead for Macs:
>
> put "~/Library/Applicati
On Sun, Sep 30, 2012 at 12:48 PM, Klaus on-rev wrote:
> This works on the Mac:
> specialfolderpath("asup") -> "~/Library/Application Support
> 4 chars less to type ;-)
I could have used that two hours ago . . .
But now I see a new headache coming . . . I need both per user *AND*
per firm prefer
>
> This works on the Mac:
> specialfolderpath("asup") -> "~/Library/Application Support
>
>
Klaus,
specialfolderpath("asup") returns the system wide Application Support
folder and not the users Application Support folder. If you are using
specialfolderpath("asup") then you will need a "put '~' be
I can store and change a string in a standalone
>> stack to find the preferences file, where I can then stuff the rest?
>> Should this, perhaps, be a custom property?
>
> You can do this:
>
> if the platform = "macos" then
> put specialfolderpath("preferen
On 9/30/12 11:27 AM, Dr. Hawkins wrote:
I'm not ready to face the differences in where things go with mac &
windows, and dealing with the OS preferences settings.
Is there a way that I can store and change a string in a standalone
stack to find the preferences file, where I can then
Richard,
Check out the specialFolderPath() function. It will give you a location to
write your preferences file.
On Sun, Sep 30, 2012 at 2:21 PM, Dr. Hawkins wrote:
> On Sun, Sep 30, 2012 at 9:27 AM, Dr. Hawkins wrote:
> > Is there a way that I can store and change a string in a s
On Sun, Sep 30, 2012 at 9:27 AM, Dr. Hawkins wrote:
> Is there a way that I can store and change a string in a standalone
> stack to find the preferences file, where I can then stuff the rest?
I think I've answered this diddling around; the executable file can't
be changed (whi
I'm not ready to face the differences in where things go with mac &
windows, and dealing with the OS preferences settings.
Is there a way that I can store and change a string in a standalone
stack to find the preferences file, where I can then stuff the rest?
Should this, perhaps, be
Mark and Klaus,
Yes, you are right.
put url ("binfile:" & specialFolderPath("preferences") & "/" & "mileage_prefs")
does work!
I will try the following Windows code again and see if it will work. The last
time it did not work.
IF the platform is "win32" then
if there is a file (spec
Hi Charles,
Am 13.11.2011 um 19:57 schrieb Charles Szasz:
> Klaus,
>
> I left out this bit code: (put arrayDecode(tPrefs)into tPrefs)
AHA! :-D
> So, my code looks like this:
> IF the platform is "MacOS" then
> if there is a file (specialFolderPath(26) & "/" & "mileage_prefs") then
OK, t
Hi Charles,
This doesn't solve the problem on Windows, but try
specialfolderpath("preferences") instead of specialfolderpath(26) In Mac OS X.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xta
Klaus,
I left out this bit code: (put arrayDecode(tPrefs)into tPrefs) So, my code
looks like this:
IF the platform is "MacOS" then
if there is a file (specialFolderPath(26) & "/" & "mileage_prefs") then
put url ("binfile:" & specialFolderPath("preferences") & "/" &
"mileage_pref
Hi Charles,
Am 13.11.2011 um 19:14 schrieb Charles Szasz:
> I am able to set up Preferences for my app. But the following script in the
> preOpenStack will NOT retrieve the data Preferences. Here is my script:
>
> IF the platform is "MacOS" then
> if there is a file (specialFolderPath(26
I am able to set up Preferences for my app. But the following script in the
preOpenStack will NOT retrieve the data Preferences. Here is my script:
IF the platform is "MacOS" then
if there is a file (specialFolderPath(26) & "/" & "mileage_prefs") then
put url ("binfile:" & specia
36 matches
Mail list logo