[PD-dev] [ pure-data-Bugs-1572310 ] after Save As..., the path remains at the location

SourceForge.net noreply at sourceforge.net
Mon Apr 28 23:51:38 CEST 2008


Bugs item #1572310, was opened at 2006-10-06 14:20
Message generated for change (Comment added) made by eighthave
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1572310&group_id=55736

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: v0.40.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Nobody/Anonymous (nobody)
Summary: after Save As..., the path remains at the location

Initial Comment:

If you open an instance of an abstraction, then Save
As... to somewhere else, the path of that abstraction
stays at the original location, even though the file
was saved to the new location.  Clicking File->Save
will then save to the original location rather than the
new location.

Tested on Mac OS X with Pd-0.39.2,
Pd-0.39.2-extended-test5, and Pd-0.40-0.


----------------------------------------------------------------------

>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2008-04-28 17:51

Message:
Logged In: YES 
user_id=27104
Originator: YES

Strange, I looked into this.  It seems that just the title bar isn't being
updated, but the patch does think of itself in the new location. [getdir]
will show the new location.  It seems that when canvas_rename() is called
inside of canvas_savetofile(), the directory is not yet updated, when
things get to canvas_reflecttitle(), and therefore canvas_getdir() returns
the old location rather than the new one.  Since this is now cosmetic, I'll
leave it for another day.

----------------------------------------------------------------------

Comment By: Hans-Christoph Steiner (eighthave)
Date: 2006-10-07 17:49

Message:
Logged In: YES 
user_id=27104


"Save As..." means write out a new file.  A new file means a
new class.  The instance that started this process remains
the old class, therefore is no longer related to this new class.

This means its inconsistent to have this instance remain as
the original class.

Also, from a usability perspective, it makes things much
more coherent.  In every other app that I use, when I do
"Save As...", that current view changes to the new file.  It
does not remain on the old file.


----------------------------------------------------------------------

Comment By: Frank Barknecht (fbar)
Date: 2006-10-07 07:53

Message:
Logged In: YES 
user_id=569446

I'm note sure if that's a bug, though I agree, that it's
confusing. But if you open an instance of an abstraction and
save that under a different name, this action doesn't affect
the name of the abstraction's instance as it is used in the
parent patch: This one will stay the same. If you want to
use your newly saved abstraction you need to rename the
instance to the new name as well first.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1572310&group_id=55736




More information about the Pd-dev mailing list