Re: v13+ LEP permision issues.

2018-05-10 Thread Chip Scheide via 4D_Tech
That is great .. I have always understood On Err Call to be a separate process Thanks for the clarification Chip On Thu, 10 May 2018 15:29:11 +, Keisuke Miyako via 4D_Tech wrote: > perhaps my comments about logging was unwarranted. > > but I think my main points stand: > > 1. no, method

Re: v13+ LEP permision issues.

2018-05-10 Thread Keisuke Miyako via 4D_Tech
perhaps my comments about logging was unwarranted. but I think my main points stand: 1. no, method called on error is not executed in another process. you might be confusing it with method called on *event* 2. no, it is not necessary to use IP. use can pass and return process variables. e.g.

Re: v13+ LEP permision issues.

2018-05-10 Thread Chip Scheide via 4D_Tech
Keisuke, > isn't "Method called on error" executed in the same process as the > invoking method? > > normally the code would only be interested in basic information such as OK, > which changes the course of action (ignore, abort, retry). > > even if more details were available, > there is

Re: v13+ LEP permision issues.

2018-05-09 Thread Keisuke Miyako via 4D_Tech
isn't "Method called on error" executed in the same process as the invoking method? normally the code would only be interested in basic information such as OK, which changes the course of action (ignore, abort, retry). even if more details were available, there is normally not much one can do

RE: v13+ LEP permision issues.

2018-05-09 Thread Chip Scheide via 4D_Tech
Tim, a bit late but... There are other reasons, but one is: Thread safety :) And while this is NOT an issue in v13, I am writing this code now, I might as well make as much of the code thread safe, and future proof, as is reasonable. Using 4D functions requires wrapping an On Err

Re: v13+ LEP permision issues.

2018-04-23 Thread Chip Scheide via 4D_Tech
Jim, Thanks! That put me on the right track. yes, mv needs a full destination path (at least when run through LEP). The permission error was coming from LEP 'pointing' at the hard drive as the current directory; and as such LEP could not write to the location. I had tried a full destination

Re: v13+ LEP permision issues.

2018-04-22 Thread Chip Scheide via 4D_Tech
thanks Jim, I think I did that, but I will try again. > On Apr 20, 2018, at 5:45 PM, Chip Scheide via 4D_Tech > <4d_tech@lists.4d.com> wrote: > >> Trying to rename a file. > [snip] >> when I execute the below line of (LEP) code I get a permissions error >> mv /Volumes/Macintosh\

Re: v13+ LEP permision issues.

2018-04-22 Thread Jim Crate via 4D_Tech
On Apr 20, 2018, at 5:45 PM, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> wrote: > Trying to rename a file. [snip] > when I execute the below line of (LEP) code I get a permissions error > mv /Volumes/Macintosh\ HD/Users/chip/Desktop/_Test\ File\ > move/Some_Win_Name.txt2 Testing.txt > >

Re: v13+ LEP permision issues.

2018-04-22 Thread Keisuke Miyako via 4D_Tech
f.y.i. https://github.com/miyako/4d-plugin-rename 2018/04/21 7:42、Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> のメール: (rename a folder for example) ** 4D Internet Users Group (4D iNUG) FAQ:

RE: v13+ LEP permision issues.

2018-04-20 Thread Chip Scheide via 4D_Tech
Ive written the code to do most of these actions in 4D. 4D's file/folder manipulation functions are FAR slower then the native OS commands. In addition to do some actions (rename a folder for example) requires coding though hoops to the job done. I'll revisit this issue next week... maybe it is

RE: v13+ LEP permision issues.

2018-04-20 Thread Chip Scheide via 4D_Tech
also - rename is not the only thing I am trying to do, it just happens to be the one that came to the fore during testing. On Fri, 20 Apr 2018 22:01:32 +, Timothy Penner via 4D_Tech wrote: > Why use LEP for something that has been built into 4D since v6? >

RE: v13+ LEP permision issues.

2018-04-20 Thread Timothy Penner via 4D_Tech
There is also COPY DOCUMENT which does support folders, and then there is the DELETE FOLDER command. http://doc.4d.com/4Dv15/4D/15.5/COPY-DOCUMENT.301-3576478.en.html http://doc.4d.com/4Dv15/4D/15.5/DELETE-FOLDER.301-3576466.en.html Do you get permission errors when using those? -Tim

RE: v13+ LEP permision issues.

2018-04-20 Thread Chip Scheide via 4D_Tech
does work for folders On Fri, 20 Apr 2018 22:01:32 +, Timothy Penner via 4D_Tech wrote: > Why use LEP for something that has been built into 4D since v6? > http://doc.4d.com/4Dv15/4D/15.5/MOVE-DOCUMENT.301-3576481.en.html > > -Tim > > > >

RE: v13+ LEP permision issues.

2018-04-20 Thread Timothy Penner via 4D_Tech
Why use LEP for something that has been built into 4D since v6? http://doc.4d.com/4Dv15/4D/15.5/MOVE-DOCUMENT.301-3576481.en.html -Tim ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive:

v13+ LEP permision issues.

2018-04-20 Thread Chip Scheide via 4D_Tech
Trying to rename a file. I can manually rename the file. I have set permissions (via finder) to 'read write' for : me, staff, evenyone then I tried setting permissions via terminal, and set permissions for the file to : 777 (RWX) regardless of permission setting I still get a permission error