Hope this hasn’t already been reported. If so, my apologies.

I came across this today, actually while teaching the feature to a new Maxer.

In certain situations, sending a message via the new and extremely convenient “click on inlet -> select “Send Message” -> type message” feature seems to be buggy. Here’s an example patch walking your through it with the metro object. I’ve only tested this on Leopard. Can others confirm this behavior (see patch for explanation of exact behavior):

----------begin_max5_patcher----------
795.3oc2XsrbaBCEcs8WgF1zMNLHw6toS6ttnq5htnISGYPAqVPxCHZRZl7u
W8.RsqURIwJ3L0KfAIwU2ygit5He6xEdq4WS57.uE7UvhE2tbwBcSpFVL77B
uF70E03N8v7J3MMDlvakoOA4Zgt8yDaHfFhnkC5Dz5ZPImzwdi.v6Ea6E9fu
rAKdm523qRK0uHe82OCFO13kblfgaH5tdeKEWO1CquQFpZhPmGACstskzISG
rfxYeqkTHLXAFk6GrBDlFotELbAbwNyRG8W5YAh7uOXXQwFJqZu.kYBTr9Vr
NdncikLunrwzBpZ6tkKUWVcjLZjOPBsRfhXkSxZRK.FDDXi9RbM8g1EtGC8g
BMAZ9ou8Dj7scCBQY9AViYUc13wTmKCSz3Fk3HYHJc14wvCkgw1UgYNWEhzn
MHwQpvf4m8f9.QeKaPHxY13sbmyaPM.iScCuMDn734i1P9.If6H.9Ok5Mkzq
kVsQ.zy1JPQMs3G.rTUVrgykC6buOqznehz0gqHm6YglQAuPzbVfin4L3Kl7
TvqppI1DeP6XG93XOZPXDZE5l3HtYKwLZOp7S788ZgABQlvgFQtqw+5dgv9h
OzQf+PXxzvuZCmIP.gv3WJBfQtRB2CVmYJK8P1JBepqXfSi.l9RiAgQlltSg
ONufbXAHL6lwc6vqkEgj4YJ3Jku1BrptjpjjjijIJPXLX.trmUnjIRDXiLej
xOfOvqKAeTfkk0ddkhLBQXdtaJEAM9lGrOeB7qgaEGXXCfqvTaqgctqsPCaF
4HWavnzWEGd.kZg7bt4CMkHmLGYZCdBr79uN5fuEdz4mfMTC+7L2nAMUFfY4
mzCN.QYVntPWScAZTll4FEnINu5N0fiIsDyIzQNxKa9+AmX.F8b43mLeYb9N
uV+ydhd3llIdydcypG9jixL5ChDHL3T4F2BHidk3E2TMLId5Vw0ivqlx96+n
Y8bnZeelpi22VLlrimQE7mIpjzI2JVW+Z2AEt2f1PKKIrcWS1PK2xkZ3gj.b
g0uaSNmBmRNgl0bJaBoTzrlQQSHiRNhLR9vcK+8bKBt0
-----------end_max5_patcher-----------

best,
Zachary

>
> Hi everyone,
>
> Hope this hasn’t already been reported. If so, my apologies.
>
> I came across this today, actually while teaching the feature to a
> new Maxer.
>
> In certain situations, sending a message via the new and extremely
> convenient “click on inlet -> select “Send Message” -> type message”
> feature seems to be buggy. Here’s an example patch walking your
> through it with the metro object. I’ve only tested this on Leopard.
> Can others confirm this behavior (see patch for explanation of exact
> behavior):

Thanks for the report, there were a bug when the value was higher than
127. This is fixed fore the next incremental.

For your second issue though, the “Send Message” feature only send a
message to the left inlet, no matter what. So if you want to change
the speed, you can write “interval 500″ for instance in the send
message box.

ej

And the real issue is that all non-zero numbers above 128 did not start metro. Thanks for fixing it in the next incremental.

But I actually thought I was changing the interval when in fact I wasn’t. Thanks for the info.

Somewhat related to this (i.e. attribute names) – is there a way to have the object inspector display the attribute names by default (it is manually displayed by clicking the @ symbol at the bottom of the window). I get tired of clicking that button every time I open a new inspector. Couldn’t find a preference setting for this. Is it there somewhere?

best,
Zachary

> Ah, I see. I must have missed that detail in the documentation. So
> that shortcut only ever allows you to send a message to the 1st
> inlet, regardless of which inlet you actually clicked.
>
> And the real issue is that all non-zero numbers above 128 did not
> start metro. Thanks for fixing it in the next incremental.
>
> But I actually thought I was changing the interval when in fact I
> wasn’t. Thanks for the info.
>
> Somewhat related to this (i.e. attribute names) – is there a way to
> have the object inspector display the attribute names by default (it
> is manually displayed by clicking the @ symbol at the bottom of the
> window). I get tired of clicking that button every time I open a new
> inspector. Couldn’t find a preference setting for this. Is it there
> somewhere?

This is not saved in the preference, although it will remember that
the option is check for the all “session” (until you restart Max).

ej

Not for me, unless – again – I’m missing something.

1. Create two objects
2. get info on one object and click the “@” button to display attribute names
3. select other object – the @ button must be clicked again. It doesn’t remember the setting
4. select the first object again – it also doesn’t remember the setting

Thanks for the help.

best,
Zachary

I have 5.0.2 installed on all platforms. Does anyone else have this problem? I’m surprised its’ working for you Emmanuel.

In fact, all I have to do (in Vista or Leopard) is:

1. make an object
2. open inspector
3. click the @ button to show attribute names
4. close the inspector
5. reopen the inspector for the same object, and the setting is forgotten

best,
Zachary

1. make an object
2. open object inspector
3. click the @ button to show attribute names
4. close the inspector
5. reopen the inspector for the same object, and the setting is forgotten, requiring you to click teh @ button once again

Can anyone reproduce? Perhaps it’s a byproduct of some combination of global preference settings.

Zachary

–CJ