Ugly stack filename problem after Save as!

[Richmond]

On 19/02/14 20:31, Klaus major-k wrote:
> Hi Richmond,
>
> Am 19.02.2014 um 19:23 schrieb Richmond <richmondmathewson at gmail.com>:
>
>> On 19/02/14 20:07, Klaus major-k wrote:
>>> Hi friends,
>>>
>>> I am experiencing a very strange problem after I save a stack AS.
>>> Looks like LC remembers the original filename and insist on using it,
>>> EVEN after I quit and restart LC!?
>>>
>>> Today I made a little test and there is something rotten in the state of denmark :-)
>>>
>>> 1. I created a new stack with one field and one button;
>>> on mouseup
>>>    put the filename of this stack into fld 1
>>> end mouseup
>>>
>>> 2. I saved the stack on my desktop
>>>
>>> 3. I click the button, all correct:
>>> <http://major-k.de/temp/stack1_desktop.jpg>
>>>
>>> 4. I save the stack with the same name in another folder using menu "Save as..."
>>>
>>> 5. Then I click the button, the correct path appears in the field, but immediately I get
>>> an error dialog "loop of death", have to hit COMMAND . to get out of this?
>>> <http://major-k.de/temp/stack1_dialog_loop.jpg>
>>>
>>> 6. Then I save the stack CMD-S and it gets saved as in 2. = wrong filename!?
>>> <http://major-k.de/temp/stack1_wrong_filename.jpg
>>>
>>> What is happening?
>>> Where could LC possibly store any previous filename and how to get rid of this?
>>> Checked all props and prop sets to no available.
>> ...
> sorry, I am using LC 6.5.2 of course.
>
>> The 'normal, tedious, way round, until the RunRev chaps stop working a 40 hour week' [some of us: including Thee and Me, Klaus, put in a hell
>> of a lot more than 40 hours] would seem to be this:
>> do your "Save As";
>> then: do a "Close and Remove from Memory",
>> then open the Saved-as stack in its NEW location.
> No, I won't! :-D
>
> LC has been working in this respect correctly for the last couple of years, so this might be a new bug and should be fixed.

That is entirely possible: it does seem that with new versions really 
odd bugs creep in: I don't quite understand why, because, for the sake 
of argument, all the software I have ever developed (and that means from 
FORTRAN, BASIB, PASCAL, ZILOG, Hypercard, ToolBook, Metacard
to Livecode) has never 'lost' things when new things have been added, 
and old things have never been broken by new things.

Probably time to file a bug report.

>
>> Richmond.
> Best
>
> Klaus
>
> --
> Klaus Major
> http://www.major-k.de
> klaus at major-k.de
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode