Weird spaces possible between @attributes?

rodrigo.constanzo · February 26, 2021, 10:59am

I thought I was going a bit batty, but it seems like you leave a load of extra spaces between @attributes for most objects. It doesn’t seem to happen all the time, but take a look at this:

That’s literally this in text:
fluid.bufstats~ @source #0loudness @stats #0loudness_stats @numchans 1 @startchan 0 @numderivs 1 @blocking 2

(actually Discourse doesn’t even display the extra spaces)

I never actually do this, but I found when I was copy/pasting attributes, I noticed that I’d sometimes have an extra space here or there.

What’s weird about this is if I copy/paste that into a new patch, the spaces go away, but if I delete/undo, it has the spaces still.


----------begin_max5_patcher----------
2162.3oc0as0aaiiE94jeEBde00fWEI2mZ6NyzAXZ2sXaWTrXvf.YYZG0HKY
HQkK6fo+1WdQV1xVVWZjSRMBbno4Q7b46b3gjG+mWdwj4o2Kym38289cuKt3
Ou7hKrcY53hxOewj0A2GFGjaG1jD4coy+5jotuRIuWY69qQpYqhmsVles2qC
RBuNMyCLq7OcGpnf3nfbO3VJSJVmVnhkJ6iEU1qqK0CajNdx7buZcfJK59IS
8lLw6OJGXzB6zpYkWg2+YFkr8QJJ6bSfJ75njUWkICUtmpOEMCyXB.C3dQm5
Q.nYfodHDw8uY.u+v7.9qKuz71zGm5YYbQzhYyKVlqBT4ey604oEYgRu+FHN
sXQhLOW2k4q1qmqbc7ZsTEdcPhV2YGSlx7IOf29uLCZgLK5V6nlGmFdiVj8P
MqswmRaOOHYkQOuLNMPcRENDzrFGdZMNAKlg.b.B6T3PrXpGlJlIDBNjSALD
BKH5N843FM.VFYRvlM2JyxiRSr1.iEPq++ZZl4i7o1OFk39nkcljIuMZ63g.
aWAYZ1So4shLqfO4dexDGsoZkXRQjcvWZL654LW8P7g9HIAqcj9lhEQoeRan
Jxu5CxjBmhYxB4xfhXUcfx7UKihiCSic72EUeiFnTZCl391okcWM1eW6FgDD
HjOU2BCwLjusktAUidgasSkz.2RDgRD.jYnDeDiPss3HLEaZANfLzt4B.EtY
.H3.hqktKndt1mLMfI1x4Hl9wss2MYoaRyTkpcMohpwWnRWkErHRlX0N.a+V
arScawOY5u0p1s5jRc5ZsBMZKM66QVYLdeQXvi0.TwbmvFzS8Rcq.uR2yY.J
m6ZwI3FIqxJ3S0ShYr9lWLWK2S5rXDltUMUSlE.BjIrrrfRXV1fSPBlUfn9U
gHpQEgQgX6HPBrlPaKJD3Kpw7SxkwZOQMSViZFROPqnC8YHGVkqCaPpSbPXn
VDpQIFQIVlES1p8L9HjClV8rt9PRYbsR1Yk.PN20R+TPn5ztLMQsEyoCZ9u1
HS79jI.8mjqilmFuXWTSyB.143pnDSfKYEPBKPPemRYqGJZeDwn3P7g.kpMG
BijrLHrjqf0jv7n+219AiFC8w2ntxRFnM1JLVpiQuyz.MqHnAhZvG04OnciX
35Vkezbt6MYmauam.1Tq8Uu0IhZVLx49SX.qNynxvhN8O6WLsCQfnS698lLc
pk8viyBg19134h8kO+KuHWxoewAe1W2uYPIzGqwU1v+LhuPT1BHZASBMIE4V
Rx.DsQTYaSOpcLoN8SeqnB7oXnadgHHRzJlj2wxIDeHD3R3Rf7IVsJU.0930
er1zkiiRj0M6lj7rK7o4DpuyTZhSXELwo7F90GVjktRl7YK3Zbf31c2DEdFR
scWLTrf4h.hEkQVLcQwiCZsllkWsz6ws9tv3sBk6mjcPtSkgRapUGP49RZcr
rnS33wQOaF+8NYh71fmuvwkX02VnTZCTa4XbT5E7JzDnr0nyV+jYopWZL06B
hR9VO4JMbuJ35wsFeVK+tHMZrMl6He.XIfZ2amEdB8hho9s73nExr1CQ2OG5
N35V21Vei9z3xkcQ6Xpudubwv7CaRS0jT3eVCq8A6IgFpxheDb+nxPRkL6aC
.10Y3iWJHj+Y5BYduiJ1ybJZYY2meAt6PHcD.YT4lh0yamYZJBzwKZdFXsOF
Ep5VW8raO+XlLWpdwkswmBS2HGRDi9tlxA68Z6gqHvlWmKrvmCl2aGlGyhic
FeYTEJcN6yGbBzMmmPCaQ47F33yoqL6ZazRmsEiBl4SXPGEDLzt8SR40pLlh
z+YcGWrzSXhleI3V4xzr0eaz0vCOiRvL5HIbKBxt4UIQqtV8J61eOOmnGrCf
yneRGi9o4U+jNp1a+.OR6lBJz2STt4SmfTETjUcYJUWqB29XFIjxWsLfLCr8
NvGiGEZHWFRqGsKXfWHRamIW+lleHPpGl1MsC7ztKo3nFm9dHlGK0KY5tIv2
lldyjQCxEkbyvPH6NKbefw+a+VvGODoRMoMP.d0x4X6Tz9sRb9h7cduQh9FZ
af5mSrpWOH7nfu8flltNttopwi4naxNkm0zZuOdInbiaOYewTZOO2IKEaRkn
6TnO7rQ.BRYgRHDXNqrEi2iMH3WsbGsJF8VmswStVGbuuo925qLcfBFrWf2F
vh756ugU5u2Hp+I55DLBrs.25+t7PXJRTewRSniQ2NrVlmGrRdlSUkWcK8G2
pkn1LtoFyl1Xqmvr.5Yr9QBUU26neVQWIXNrCcauZ5azO7HW8q913B4qfC5F
NLUkHq7R62ELRL5gfJYvrz6RFLG9zDjzwg+iGBFNCBPBpqPAXLLF471PPc5b
iOC9tLo76fCsZupyTC5aRLZ7YtOnirknBFL6wI.ee2o84CzLmUU5KfB53yi+
a4hAyerprdgUapBTthwXye+WYbb5cCWEhntRfgwgbap5.pFU1Y8YQE..+bH.
neDE.60W7tz3uCHR04eP0YBQcUiz9KBNJL3lhrMwxAkbJA3xqAQA9BKFFwo9
HdOyPiUUdgDHUG1vFayD8XTcMyjgxnaa+l6ZByTsotcLGX+xRbbXN2VTLvhA
n46DPz3VOI53fhx0OXkEss1IPLpqjjKSVj+RaEjcJ4188NnLXYP.ycgQDefn
rH2YvtqdvmFGVUvltpj68NLp2GnR8duYWnSFs4OWIWVDGq57BVNrXN4TJzcl
r9XF1Uz69ZuK+1pvXBTmNoMYxpMEXNygphmbTEpAKSHNi6xy.WgjwHAVveLx
zy996Ux7WV+dAtybZNOLzx.PO+FMscWm3REr1Os7JFNcV.X+NO+JnP.boUpA
vjx6J2G.vvVKK2eJJS8f2OuJsGUFYWUH+vUrte6b1avyvS4aJMg1eKiW9WW9
+A.5QsW.
-----------end_max5_patcher-----------

rodrigo.constanzo · February 26, 2021, 11:26am

Oh, the inclusion of the jit.gl.mesh there is to show that when this is happening with fluid.objects~ I can’t ever get native Max objects to behave in the same way. As in, if I add extra spaces to native objects, the moment I hit enter, they disappear.

weefuzzy · February 26, 2021, 11:36am

Can’t reproduce this at all on 8.1.15 – and it’s not something we have any agency in (how boxes are drawn)

rodrigo.constanzo · February 26, 2021, 11:51am

I’m on 8.1.1 (there’s another update?). I’ll see if I can reproduce it. The reason I mention it here is that this is something I’ve never seen with other native objects.

Actually here’s a video of it happening consistently (pardon my one handed faff/typing):

Maybe it’s something to do with how attributes are named/parsed?

tremblap · February 26, 2021, 12:08pm

I can’t reproduce but I can say that attribute autocompletion has always been (native or ours) a complicated issue with Max. I hate that you cannot have it to work in the middle of a list for instance, and so many other irritants… so I feel sorry for your (custom) problem but cannot help from here either.

tremblap · February 26, 2021, 1:32pm

btw your comparison is not ‘fair’ - try to modify the attributes on an already instantiated object with already other attributes. This is the kind of behaviour that is bad in Max in general with all objects. At the moment ours and jit* behave the same and ‘rightly’ here… but again, I never got autocompletion to work anywhere than the end of the attributes… and in messages only for the first item…

rodrigo.constanzo · February 26, 2021, 3:02pm

It seems to be independent of autocomplete, and I can’t get the same behavior on any other non-fluid. objects, but if it’s nothing that you have control of, it doesn’t matter one way or another.

When I made the post I presumed there was an attribute type/flag or something that allowed for this kind of behavior.