Why is that?

For example:

This helpfile of PDjs appears blank in Vanilla:
js-help.pd

#N canvas 2802 562 675 300 12;
#X obj 312 53 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1
-1;
#X msg 314 74 compile;
#X obj 240 253 print js;
#X text 412 204 Load JavaScript file js-help.js;
#X text 412 225 args are available through;
#X text 413 244 property jsarguments in JS;
#X obj 244 202 js js-help.js arg1 arg2;
#X text 371 73 recompile source;
#X text 11 9 js: Execute JavaScript;
#X floatatom 314 102 5 0 0 0 - - -;
#X msg 320 129 1 2 3;
#X text 331 51 call function bang;
#X text 357 99 call function msg_float;
#X text 373 129 call function list;
#X msg 142 61 setprop name test;
#X msg 143 87 getprop name;
#X text 25 59 set JS property;
#X text 26 88 get JS property;
#X msg 322 167 test x y z;
#X text 409 165 call function test;
#X text 41 28 https://github.com/mganss/pdjs;
#X connect 0 0 6 0;
#X connect 1 0 6 0;
#X connect 6 0 2 0;
#X connect 9 0 6 0;
#X connect 10 0 6 0;
#X connect 14 0 6 0;
#X connect 15 0 6 0;
#X connect 18 0 6 0;

That one is made in Vanilla and opens:
js-help-vanilla.pd

#N canvas 80 229 1014 606 12;
#X obj 142 191 js js-help.js arg1 arg2;
#X msg 127 59 setprop name test;
#X msg 127 85 getprop name;
#X obj 290 45 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1
-1;
#X msg 293 65 compile;
#X floatatom 293 93 5 0 0 0 - - -;
#X msg 304 118 1 2 3;
#X msg 308 149 test x y z;
#X obj 142 215 print js;
#X text 13 58 set JS property;
#X text 13 85 get JS property;
#X text 14 10 js: Execute JavaScript;
#X text 63 26 https://github.com/mganss/pdjs;
#X text 312 41 call function bang;
#X text 354 63 recompile source;
#X text 345 93 call function msg_float;
#X text 358 119 call function list;
#X text 394 149 call function test;
#X text 309 191 Load JavaScript file js-help.js;
#X text 309 212 args are available through;
#X text 309 234 property jsarguments in JS;
#X connect 0 0 8 0;
#X connect 1 0 0 0;
#X connect 2 0 0 0;
#X connect 3 0 0 0;
#X connect 4 0 0 0;
#X connect 5 0 0 0;
#X connect 6 0 0 0;
#X connect 7 0 0 0;

One more example:

A patch from the pd-list, does not open in Vanilla:
lock-in-amplifier.pd

@jancsika ?

@lacuna I see nothing wrong with them and they both work just fine in 52.1 for me beyond the js object not creating since I do not have pdjs installed.

51.4 and 52.1 Win10

Now I replaced the first line of these non-working patches by the working one:

#N canvas 80 229 1014 606 12; 

And yes they open now!

So these patches starting with

#N canvas 2802 562 675 300 12;

or

#N canvas 785 1198 794 777 12;

appear blank.

not sure why, but fixed

@lacuna said:

So these patches starting with

#N canvas 2802 562 675 300 12;

or

#N canvas 785 1198 794 777 12;

appear blank.

If (I'm guessing) the canvas parameters are "left-X top-Y width height" (and I guess 12 is a zoom factor but I'm not sure), then X = 2802 is very, very far to the right, and 1198 is very, very far down. On my laptop, I've got 1366x768; a window positioned 2802 pixels away from screen left would far, far out of bounds.

The window manager that I use in Linux will "fix" offscreen window coordinates, so when I open the js-help patch, it appears flush against the right and bottom screen borders. The stated coordinates are out of bounds on my system; the window manager shifts them to be on screen. The problem is technically there, but masked by the window manager.

I have seen Windows not adjust out of bounds window coordinates -- i.e., open a subpatch within a student's patch, and couldn't see the window at all.

I'm not 100% certain that's the problem here -- but I'll observe that the action you took, which resolved the problem, was to change the upper-left window coordinates to be much closer to the top left of the screen.

hjh

Thank you

From time to time it happens with found patches around the Internet (quite annoying, but now I'm happy with the work-around). The window is minimized, small and blank.

I am not 100% sure if they all where made with Purr Data,
but am sure that at least some where made with it and someone told me once, her "Purr Data patches won't open in Vanilla",
so I assumed this would be a Purr Data > Vanilla thing, - could even be a cross-system problem or both or Win only. ...Didn't try to open with Purr Data or Linux...
They might also be made on higher resolution bigger screens or multi-screens.

I am facing a similar problem. I was working on de-subpatching timbre-ID examples and at some point the patch only works on puur data. On vanilla it complains about not having the declared arrays, although it is working fine on puur data:

soundfiler read: 0-timbreID-set: no such table
0-timbreOrder: no such object 
0-timbreOrder: no such object 

Could this be some kind of UTF/ASCII problem ? It seems that pd vanilla is eating the $...

I am on windows 11, pd 0.52.2 puur data 2.17.0( pd 0.48.0)

here is the patch:
order-no-subpatches.pd
grain-player-unit-abs.pd (should be inside a lib folder)

@fmiramar said:

seems that pd vanilla is eating the $...

this is because Vanilla reads $0 in objects only, not in messages.
PurrData does read [$0-arrayname(

you can substitute

[o]
|
[$0-arrayname(
|
[print}

by

[o]
|
[f $0]
|
[$1-arrayname(
[
[print]

https://forum.pdpatchrepo.info/topic/5724/dollar-signs-in-objects-and-messages/21

On topic of my first post:
Same happens with some [pd subpatches], too.

@ddw_music said:

I have seen Windows not adjust out of bounds window coordinates -- i.e., open a subpatch within a student's patch, and couldn't see the window at all.

... here is a patch that parses pd-patches and puts all windows back on screen:

move_windows_6np.pd
test.pd

thx again!

(latest update v6 fixes negative canvas positions, too.)

Even in the documentation of pd 0.52 a few subpatches have not been opening!!!

replacing: pd-0.52-2/doc/5.reference/text-object-help.pd line 949 field 2
replacing: pd-0.52-2/doc/5.reference/tabread-help.pd line 25 field 3
replacing: pd-0.52-2/doc/3.audio.examples/I10.phase.bash.pd line 3 field 2
replacing: pd-0.52-2/doc/3.audio.examples/I10.phase.bash.pd line 298 field 2

EDIT: Added a [spigot], - now only overwrites if actual changes have been made.

EDIT also see this post! https://forum.pdpatchrepo.info/topic/14404/disappearing-patches/11

simply don't expect Vanilla and Purr Data to be compatible, they are not. There are many issues opening vanilla patches in purr data and vice versa