Hello everyone,

I am currently experiences issues in Pd relating to the xticks, yticks, xlabel, and ylabel. Essentially, this console window spews out all of this information as soon as I load the patch. I am not sure why it isn't working for the "space-curve" array but it works for the "sample-#-curve" array.

Console:

Actual patch which instructs to change the labels:

Outside patch that tells my two arrays to loadbang. The "sample-curve" is the one that doesn't work:

My arrays:

I still can't figure out what isn't working properly. I've check and double checked everything and so I wonder if this is some kind of a bug. It's important to note though that it looks like it actually works. This is even more confusing. Please let me know if you have any ideas!

Thank you!

I'm not sure if the label for the array is just a comment, but it appears that the pound sign is a reserved character. When i name an array space-#-curve the # is replaced with $.

The thing I don't really understand is why there were so many errors registered in the pdwindow. That is strange; there should just be one per bang.

Yeah, and the weird thing is that the "sample-#-curve' works just fine. I'm wondering if it's messing up the other one?

I tested it on a mac and it didn't spit out any tcl errors, but I have a hunch something silently erred. Hmm. I'll poke around the tcl source and skim through the docs to see if I notice anything later.

I would try it with another array name if you can.

Tried it. Did not work.

Would you mind posting what operating system you are using,
the contents of the space-#-curve subpatch (or better, the whole patch),
and the version of pd you are using?

edit:: ah, I see you are using extended. Its easy blaming things on extended.

My operating system is OS X. Yeah I'm using Pd Extended. Haven't switched over to Pd Vanilla, but still have the same issue if I open it in that one too.

Hmm, outside of trying to label an array without realizing it was renamed, I can't reproduce the errors. Your pdwindow has an asterisk instead of the array, so maybe the send in your message is misspelled?

.. really at a loss. You could open the patch in vanilla and save it again - I've not heard of extended making corrupt save files, but I guess its possible.

Honestly, If i were you, I would use an [array define] object to hold the array and then use structs to display the array (keeps you from drawing into the array via mouse). But thats in vanilla, not extended. I can post a patch that has a demo of that.

@lunacyfringe It could be because you are sending the message to the space-curve array.... and also to the space-curve sub-patch...... which complains........ but manages to send the message again.
It doesn't do that in win7 pd-extended though...... so I cannot test. But some other object than the array is also receiving the message and complaining....
Maybe the #..... translated to a variable.... is given a different value in the object that complains otherwise....... and so it never gets the message.
David.