this is a pretty annoying thing...most of the time, the patches open correctly but once in a while they start to open offscreen, and once it starts they keep doing this, so if I am editing a huge project with many pieces I have to keep going and "maximizing" the patch, which then cannot be resized...a constant loop.

this seems to be new in the most recent version of pd? anyone have any suggestions?

I've also experienced this in the recent version.
It's pretty annoying. I don't think there's any solution but to wait for the fixed version.

If you check in Pd's browser/Pure Data/manuals/pd-msg/1.msg_and_patch/6.relocate_windows.pd you can use messaging to Pd to restore a window's position.
It's not really a fix to the problem, but it should help whenever this occurs.

I've had this problem as well and I'm pretty sure it has to do with saving on a patch on another display and then loading it without that display attached. Each patch saves its location and width and sometimes the saved location is past the edge of the primary display's screen area.

Hey, me too!

Thank you, Alexandros - pasting in the bit of that help file lets me access my subpatches again. SO good.

But still a pain, of course. I don't know if this solves the core of the Coalman issue, but can the erroneous numbers be tweaked if you edit the patch as a text file? I tried, but I didn't know what I was doing. WOULD this work, and if so, does anyone know which line(s) I would edit, and what realistic-looking values might be?

Mmmm... erroneous tweaking...

Heh heh... kinda answered my own question there.

I opened the patch as a text file (duplicating it first, in case I fouled majorly!) then did a ctl-F (apple-F) search for the name of my errant subpatch. Every time I found my subpatch as:

#N canvas 1234 1234 1024 675 "the_name" 0;

(for instance) I changed the first two numbers (1234 in this hypothetical example) to "5," and the subpatches opened in plain view.

Computers can do anything!

@alexandros Thanks - that works!. Still annoying, though - just happened whilst I was trying to access a subpatch within the zl helpfile,which has a name separated by whitespace, and I can't figure out how to get this to work with the relocate message....doh!

I just recently started getting this problem as well, a problem I hadn't encountered on Pd-vanilla 0.45-4 (OSX) but I am experiencing this problem with the vanilla distribution with the MobMuPlat software. I will try the "plain text" solution, but it would be great if we could come up with a way to replicate this issue so we can alert MIller for the next version. This problem wasn't created for me when working on a patch with an external screen not attached (as suggested by portabello), I am however using an external monitor attached. I tried unplugging the external monitor (hoping this would gather all the windows) but this didn't work. VERY frustrating!