On 2016-07-01 17:14, Paul Dupuis wrote:
The problem I am working on has to do with reading and writing a
preferences file and a license file across platforms and within
platforms across versions of the OS and even within a platform
(Windows)
and OS version, the wide range or ways corporate and
On 7/1/2016 10:23 PM, Mark Wieder wrote:
> Agreed. Please file a bug report on this.
Already done. 5 messages above in the thread:
http://quality.livecode.com/show_bug.cgi?id=17927
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit
As Paul Dupuis pointed out, SpecialFolderPath() also accepts numbers. These
are for Win32...
specialFolderPath (2) : Programs
specialFolderPath (5) : Documents
specialFolderPath (6) : Favorites
specialFolderPath (7) : startup
specialFolderPath (8) : Recent
specialFolderPath (9) : SendTo
On 07/01/2016 11:17 AM, Paul Dupuis wrote:
This, by definition, is a bug in LiveCode. It is either a documentation
bug that the dictionary entries for folders and files do not state that
the permissions data is invalid for Windows OR it is a technical bug
that the permission values are invalid
On 7/1/2016 1:50 PM, J. Landman Gay wrote:
> For Windows you can specify specialFolderPath( "0x001a" ) which is the
> approved location for writing app data. On Mac it's the Application
> Support folder ; I thought there was a special designator for that too
> but I don't see one in the
For Windows you can specify specialFolderPath( "0x001a" ) which is the
approved location for writing app data. On Mac it's the Application Support
folder ; I thought there was a special designator for that too but I don't
see one in the dictionary. If memory serves, it's" apsup" I think.
On 7/1/2016 7:49 AM, Mark Waddingham wrote:
> I just wonder if there is a better away to approach the problem you
> are trying to solve; or whether there is actually a problem to solve
> at all (which isn't already solved by thorough error checking and
> handling).
The problem I am working on has
Mark Waddingham wrote:
> There are two things to remember when dealing with files and folders:
>
>1) You have to check for success of all your file operations -
> they can fail for all kinds of reasons which are entirely outwith
> your control, not just permissions issues.
>
>2) There is
On 2016-06-30 23:13, Paul Dupuis wrote:
It would be so much nicer to actually check permissions that tricks
like
writing dummy files and checking for errors
I think it is important to clarify what you are wanting to achieve here.
There are two things to remember when dealing with files and
On 6/30/2016 4:06 PM, Peter TB Brett wrote:
> On 30/06/2016 20:48, Richard Gaskin wrote:
>> My understanding is that Windows lacks true POSIX file-system-level
>> permissions as found in Linux and in Unix flavors like macOS.
>>
>> While it does have file attributes, I believe there is no
>>
On 30/06/2016 21:46, Richard Gaskin wrote:
Back on topic, your description suggests that showing "777" for Windows
files is indeed a bug in LC, since it doesn't accurately reflect the
permissions of the file, yes?
Well, it's more of a missing feature. LiveCode / Revolution has never
Peter TB Brett wrote:
> On 30/06/2016 20:48, Richard Gaskin wrote:
>> My understanding is that Windows lacks true POSIX file-system-level
>> permissions as found in Linux and in Unix flavors like macOS.
>>
>> While it does have file attributes, I believe there is no
>> file-system-level support
On 30/06/2016 20:48, Richard Gaskin wrote:
My understanding is that Windows lacks true POSIX file-system-level
permissions as found in Linux and in Unix flavors like macOS.
While it does have file attributes, I believe there is no
file-system-level support for granting different rights to
Paul Dupuis wrote:
> In 8.1 dp-2 (and as far back as 6.7.11) if you get "the detailed
> folders" and check item 10 (folder permissions) it is ALWAYS 777 under
> Windows (8.1 at least) regardless of the actual folder permissions.
> BUG RECIPE: Make a folder read-only and fetch the detailed
In 8.1 dp-2 (and as far back as 6.7.11) if you get "the detailed
folders" and check item 10 (folder permissions) it is ALWAYS 777 under
Windows (8.1 at least) regardless of the actual folder permissions. BUG
RECIPE: Make a folder read-only and fetch the detailed folders of it's
parent folder.
15 matches
Mail list logo