Well that is reasonably the reason why.

And we are now on .56-2, and ofelia seems to continue to create problems.

What are others using when trying to have access to pdfs or jpegs and want to show them on a screen when using pure data without creating digital clicks in sound.?

Also, I can duplicate the file, change the name, and then open up the new file.

I think it might be a result of using ofelia.

Hello,
There is a patch I am working on that works and that I can save in the same name, but in Pure Data if I try to "Save as" a new name Pd crashes.

Here is the error that I am seeing before it crashes:
(Tcl) UNHANDLED ERROR: bad window path name ".x600002764900"
while executing
"tk_getSaveFile -initialdir $initialdir -initialfile [::pdtk_canvas::cleanname "$initialfile"] -defaultextension .pd -filetypes $::filetypes -parent..."
(procedure "pdtk_canvas_saveas" line 3)
invoked from within
"pdtk_canvas_saveas .x600002764900 {RECORDwTITLE.pd} {/Users/williamraynovich/Documents/Pd/PureDatainformation} 0 "
("uplevel" body line 1)
invoked from within
"uplevel #0 $docmds"(Tcl) UNHANDLED ERROR: bad window path name ".x600002764900"
while executing
"tk_getSaveFile -initialdir $initialdir -initialfile [::pdtk_canvas::cleanname "$initialfile"] -defaultextension .pd -filetypes $::filetypes -parent..."
(procedure "pdtk_canvas_saveas" line 3)
invoked from within
"pdtk_canvas_saveas .x600002764900 {RECORDwTITLE.pd} {/Users/williamraynovich/Documents/Pd/PureDatainformation} 0 "
("uplevel" body line 1)
invoked from within
"uplevel #0 $docmds"

It seems to be something about the path of the RECORDwTITLE object?

Can anyone easily see what the issue is.

Thank you. This is what I was looking for. The help from a few years ago was helpful. I am on to the next step in this process. I am guessing that those who intend to have others use their patches use MAX/MSP?

You have been very helpful.

So, as I am looking at one way to do this, I could put objects that I am using for a specific piece into a folder where I open that piece and do something like this:

declare -path ./name_of_folder_that_I_put_objects_in

Is this what you all do? Or do you not really share complex patches with others to perform?

@alexandros Also, with this, I am more trying to make my patches be able to be used by others more easily. I have to make sure the computer that I am transferring the patch to has all the external objects already downloaded. I was/am hoping there might be an easier way.

Hello,
Yeah I fixed that. I remembered that one and it did help and it has been going well for me.

I am seeing if there is an elegant solution to make it so that I do not have to go in to the Pd patch when using a different computer with a different user ID and change the pathway even in the declare way of making the paths?

So that if I send the Pd patch with all needed objects to another person it will automatically work.

Does that make sense?

Thank you, I am trying to work on this.

I realized that pd pathways seem to be a bit odd or I am doing something wrong. The name on my mac is:

/Users/raynovich/Documents/Pd/externals/NAMEOFFOLDERorPDfile

I think that is how the "data structures" of MacOS systems work? So, if I have to change to a different User name or I want to give a performer my composition to perform than they would have to get all those permissions set up.

Am I doing something wrong?

Maybe there is an easier way?