Re: save stack as filename failing most of the time

I tried, but it works fine for me every time in LC8.1.2 (Build 14013) (I no longer have RC3 installed), on MacOS Sierra 10.12.2. This is the test script I used: on mouseUp put"/Users/paulhibbert/Documents/001 Test Folder/paultest.xx.to.Compile.livecode" into tFileName replace "xx" with char

Re: save stack as filename failing most of the time

livecode has been unable to reproduce the bug. Could someone who was able to make a stack to manifest this please upload? *Comment # 1 on bug 19042 from Panos Merakos

Re: save stack as filename failing most of the time

Hi again, Ok, so first looked at the settings for the defaultFolder, and then I set the defaultFolder to where I wanted everything to be saved. I chose to use my desktop to be super easy. It turned out that the defaultFolder somehow strangely got set to a RunRev Application Support folder

Re: save stack as filename failing most of the time

Since there is no error, and it shows "TestSaveStack" my guess is it IS saving the file correctly, but a folder along the way to where the file is saved is hidden (hence being unsearchable.) If you set the folder to a known location (prior to the save) and then save it, it will probably be right

Re: save stack as filename failing most of the time

On Thu, Jan 5, 2017 at 9:47 AM, Rick Harrison via use-livecode < use-livecode@lists.runrev.com> wrote: > > Searching my entire hard drive doesn’t show > any file named “TestSaveStack”. > Do you get the same result if you make a stack in a known location, perhaps InitialTestStack, and then use

Re: save stack as filename failing most of the time

Hi all, > Am 05.01.2017 um 18:47 schrieb Rick Harrison via use-livecode > : > > Hi Mike, > > Using your code in the button shows in the message box > TestSaveStack > > Which is the name of the file. > > Searching my entire hard drive doesn’t show > any file

Re: save stack as filename failing most of the time

Hi Mike, Using your code in the button shows in the message box TestSaveStack Which is the name of the file. Searching my entire hard drive doesn’t show any file named “TestSaveStack”. There is no error reported for "the result”. Rick > On Jan 5, 2017, at 11:32 AM, Mike Bonner via

Re: save stack as filename failing most of the time

If you change it to on mouseup save this stack as "TestSaveStack" put it && the result put cr & the files after msg end mouseup does it return an error? If not, does it show the file? If the default folder is set to an unwritable folder you should receive an error. If not, you should see the

Re: save stack as filename failing most of the time

> On Jan 3, 2017, at 6:38 PM, Bob Sneidar wrote: > > Not sure this helps you but I use Save this stack all the time and I can see > the stack in the finder append a tilde (~), create a new stack file then the > file with the tilde goes away. My changes are always

Re: save stack as filename failing most of the time

On Wed, Jan 4, 2017 at 3:39 PM, J. Landman Gay wrote: > On 1/4/17 4:37 PM, Dr. Hawkins wrote: > >> "the sub stacksof" also reveals no substack. >> > > Is that a typo? Does "substacks of" also fail? > failed autocorrect? It was actually "substacks of" -- Dr. Richard

Re: save stack as filename failing most of the time

On 1/4/17 4:37 PM, Dr. Hawkins wrote: "the sub stacksof" also reveals no substack. Is that a typo? Does "substacks of" also fail? -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com

Re: save stack as filename failing most of the time

Now I'm seeing "put" fail to put things in the message box, which I suspect is related. And the application browser insists that there is a substack to one of my stacks that shouldn't be there. It strives saving and duplication, but when I open that stack by itself, it shows no sub stack. "the

Re: save stack as filename failing most of the time

On Tue, Jan 3, 2017 at 3:38 PM, Bob Sneidar wrote: > Not sure this helps you but I use Save this stack all the time and I can > see the stack in the finder append a tilde (~), create a new stack file > then the file with the tilde goes away. My changes are always

Re: save stack as filename failing most of the time

Not sure this helps you but I use Save this stack all the time and I can see the stack in the finder append a tilde (~), create a new stack file then the file with the tilde goes away. My changes are always there afterwards. Bob S On Jan 3, 2017, at 14:01 , Rick Harrison

Re: save stack as filename failing most of the time

On Tue, Jan 3, 2017 at 2:01 PM, Rick Harrison wrote: > I just tried the save statement from within a stack > and I too have found that the stack is not getting saved! > Has anyone reported this as bug? Is there a work around? > This one was so bizarre that I need to

Re: save stack as filename failing most of the time

I just tried the save statement from within a stack and I too have found that the stack is not getting saved! Has anyone reported this as bug? Is there a work around? Thanks, Rick > On Dec 30, 2016, at 6:06 PM, Dr. Hawkins wrote: > > Just saw it happen. > > Apparently, it

Re: save stack as filename failing most of the time

Just saw it happen. Apparently, it is simply ignoring the new name--I see the ~ stack renaming, and then the new stack is created with the original name, not the contents of filNam, and the ~ stack deleted. -- Dr. Richard E. Hawkins, Esq. (702) 508-8462