Re: tsNet docs/sample stacks

yes, more docs would help. I don't see any "SFTP" upload example, only "FTPS" upload. The later, I believe, gets into certificates, which I would rather avoid. On 12/1/16, 8:18 AM, "use-livecode on behalf of Ben Rubinstein"

Re: Clone graphic does not respect dimensions

Jeanne A. E. DeVoto wrote: > At 12:23 PM -0800 12/2/2016, Richard Gaskin wrote: >>I believe the original post here was about cloning, presumably done >>via Option+drag (on macOS, or Cntrl+drag on Win and Linux). > > Hmm, I was under the impression that it was scripted using the > "clone"

Re: Clone graphic does not respect dimensions

At 12:23 PM -0800 12/2/2016, Richard Gaskin wrote: I believe the original post here was about cloning, presumably done via Option+drag (on macOS, or Cntrl+drag on Win and Linux). Hmm, I was under the impression that it was scripted using the "clone" command. I'd forgotten about option-drag...

Re: Clone graphic does not respect dimensions

In any event, if there's going to be a size trap, I don't believe it belongs in the backscript newGraphic handler. If the intention of the minimum size restriction is to prevent accidental double-clicks, there are better ways to deal with that situation. - -- Mark Wieder

Re: live code seems to gratuitously unlock write permission for directories

I've added the following after setting the name, and also moved the save into this block: *if* (char 1 to 6 of bkNm) <> (char -17 to -12 of the long name of this stack) *then* *--date has changed* bmpVrsn stkNm *else* *save* this stack *end* *if* bmpVrsn is my routine to bump the filename.

Re: live code seems to gratuitously unlock write permission for directories

On Fri, Dec 2, 2016 at 12:01 PM, Mike Bonner wrote: > Not sure I understand this but... You open a stack, and then try to change > the permissions of the directory that it resides in so that you then can't > save it? Since the file is already open and "in use" i'm not sure

Re: Clone graphic does not respect dimensions

Jeanne A. E. DeVoto wrote: > At 3:02 AM -0800 12/2/2016, BNig wrote: >> It seems the consensus is to lower the threshold when graphics are >> changed to default sizes. I will do an enhancement request next week >> and propose that the currrent threshold of 8 by 8 and lower will be >> reduced to

Re: live code seems to gratuitously unlock write permission for directories

Not sure I understand this but... You open a stack, and then try to change the permissions of the directory that it resides in so that you then can't save it? Since the file is already open and "in use" i'm not sure its actually possible to change the permissions under those circumstances. If

Re: live code seems to gratuitously unlock write permission for directories

On Fri, Dec 2, 2016 at 11:20 AM, J. Landman Gay wrote: > On 12/2/16 12:55 PM, Dr. Hawkins wrote: > >> *--livecode's own stacks* >> >> *case* char 1 to 3 of stkNm="Rev" >> >> *case* stkNm="Message Box" >> > > This is no longer the case. Some of LC's stacks no longer

Re: live code seems to gratuitously unlock write permission for directories

On Fri, Dec 2, 2016 at 11:05 AM, Bob Sneidar wrote: > So what *actually* happens when you save a file is, the old file is > renamed by prepending a tilde (~) to the filename, then an attempt to save > the file as the original is attempted. If all goes well, the

Re: Clone graphic does not respect dimensions

Yet another option is a 0.618 x 0.618 pixels threshold. I definitely need that when using a HiRes display ;-) "A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools." (Douglas Adams)

Re: Clone graphic does not respect dimensions

At 3:02 AM -0800 12/2/2016, BNig wrote: It seems the consensus is to lower the threshold when graphics are changed to default sizes. I will do an enhancement request next week and propose that the currrent threshold of 8 by 8 and lower will be reduced to 5 by 5 and lower. Is there any reason

Re: live code seems to gratuitously unlock write permission for directories

On 12/2/16 12:55 PM, Dr. Hawkins wrote: *--livecode's own stacks* *case* char 1 to 3 of stkNm="Rev" *case* stkNm="Message Box" This is no longer the case. Some of LC's stacks no longer start with "rev". It probably doesn't matter if you back those up anyway, but just so you know. --

Re: live code seems to gratuitously unlock write permission for directories

So what *actually* happens when you save a file is, the old file is renamed by prepending a tilde (~) to the filename, then an attempt to save the file as the original is attempted. If all goes well, the backup copy is deleted. So in a sense you are not actually saving, you are saving as.

Re: live code seems to gratuitously unlock write permission for directories

On Fri, Dec 2, 2016 at 9:59 AM, Rick Harrison wrote: > Ok, so it sounds like you are using an LC stack file. > You are opening that LC stack from within LC > so LC/macOS, (assuming your are on a Macintosh Computer), > is going to update the “Date Modified” date because

Re: live code seems to gratuitously unlock write permission for directories

Ok, so it sounds like you are using an LC stack file. You are opening that LC stack from within LC so LC/macOS, (assuming your are on a Macintosh Computer), is going to update the “Date Modified” date because LC/you have touched the file. That’s built into the OS and is deliberate. What I

Re: live code seems to gratuitously unlock write permission for directories

On Thu, Dec 1, 2016 at 4:08 PM, Rick Harrison wrote: > If you just want to prevent overwriting of older files, > why don’t you just use a new name for the file. > This is about protecting me from accidental saves. There are a dozen or so separate files. I want a new

Re: [ANN] XLSX Library ready for a test - Looking for testers

You know I am all in... I believe in the your products, Mr. Slug! SKIP On Thu, Dec 1, 2016 at 6:08 PM, Bob Sneidar wrote: > I'll give it a go later. > > Bob S > > > On Nov 30, 2016, at 15:36 , zryip theSlug > wrote:

Re: Clone graphic does not respect dimensions

Richard Gaskin wrote > Michael Julian Lew wrote: > > > Richard Gaskin wrote: > >> BNig wrote: > >>> that is determined somewhat arbitrarily by the > >>> revBackScriptLibrary in handler > >>> > >>> on newGraphic > >>> if the width of the target < 9 and the height of the target < 9 then >