Fluid.bufstats~ does not let you double-click an incorrect attribute

If you create a fluid.bufstats~ object with an attribute it doesn’t have (@deststartchan 0) you get a red error message in the Max window. But if I double-click that red error message it does not jump to the object.


----------begin_max5_patcher----------
1052.3ocyXszaaaDD9rzuBBdVQXe+nmRaOjKtnG7ghhf.CJpUJLkhjfOhsaP
5u8N6rjzhRNJVoz.0GD1c3Lb9lY9lYW5urbQ7lxGbMwQ+Tz6iVr3KKWr.E4E
rne+h3CIOjlmzfpEW3tubymhWEdTq6gVT7t7trsq2zsqoMos4ehdaSYWcpKJ
uraagqogCR7OYTvc31f351c0IGbQjn2Vzc.W2DowMoeLonIh1qlemWqstl1i
DLfl7rBWZYWABIQuvpDPqrh82U6RaCQpjrlrJhorqkbthS3ZJwx0RPl.ejhs
lD8g9W.fhrhbWKF+zmDV10NHk0KMaKlLfDzanpATEzq8wJWv6waRJ1GuJJNN
5CdM95xk9eP+EmTU8YWcSVYAVC7U.H++oxZ+VyJbaVQXKA2V69b1f9RTRRMD
vsPz1UitL9AkHNXZ4VWcQWFFIKAm5cYS6i4mxAJfR.Z5O2sMq7VnT00b2u4J
5BAU7V2tjt71o7jM62kkmmVlGf2hwm.7j9nON7zU8hG088Qj0LqfRMqfUbJW
yT3JXgDpKzgpQuMzAiDRgkv7pJTLsPhqLLtj6WQNwL1S9hPsAOPrFhHrBDQA
ecrYPoJGQNS6YF8RqpKqJqa6y5fo1Q86ZK2WmrMyEXgDTNVhCoajQVCOES6X
NoOmd.RnYC1.5ddw3ltzjKU.RRSgW7jjJmAIHL5DRHRwU5frihy3ckEsCtAX
n+dkqH5Vem2stCYaJyAd8fptb2gS8h1nTZL2aHTiIrBbHiM0Ma1OwLKQP0H5
LVoPqClwrgWkTMZWC3zTe5dpWYDUHjnJMKTvMDBUL0o9YTnc2kU36sbij.tk
QQR.ajEwzFAmdJp+975wZ92fZ+BoaSI2lQJsQSjFSX0Y.7TxsZnRq7+oCqBu
oWEtceZZRDKzRJGgNyxgpaHKSgBVOHlkFh+pIOCln8G9wcWpw3HnQ8y2m7yL
gE3TRk+nyqq+LTSGIh5d5w2ro4D3CcIeedNp2vOya.iGL9By7.o.lKyrGOCx
2vIjz4FVv8GZR1eQJwUjs9OOF3nF5gFxyWcgFZsweh1pmc04l8+xy3l1c7xp
hgKN8hYWXM6n6C.wLeVm1Dt56uj24dC8ZOFlpUhvj3Q.Z8hnuB.rt79hqFgO
gK4XuI+UBg+5iIWO.IL3NBggjZNmE5cXTJkO+.7c0N2O.BwrG2+W3RI9yume
v8mt77x6uZzYfie0gIGTCEmuIgLp77KB1j828SCoLuRDhYtBftCab0uCtO4U
CeOUjfkeIbXoDiD5wSylE.VGtPgGgW9KctNr8b2PRITJtsmEq6u7KTOryJe9
o3Y9y3OWTYIv2RipZ4BEw1ekdMUNmQUaR0kBlS9ZlaRZKitIa+Gai+Q7e3Cy
w+CH9WZSURZPc+4YK+5x+EHndp2L
-----------end_max5_patcher-----------

@weefuzzy is that something that is linked to our wrapper?

That error message is generated by Max, which handles parsing attributes arguments from the object box. Built-in objects are the same:


----------begin_max5_patcher----------
1166.3ocyWszaiaCD9r8uBAc1a.eHIJ0SaaOrWRQOjCEEEAFzxLJbWIRWJp7
nKR+s2gjRxRNIFNANs0GLFNbFxu4IG88kKh2nePzFG8CQ+QzhEee4hEdVNFK
5WuHtg+PYMu0KVrRbudyWiWE1xJdv5YWYz56D+czma0clRQTstaqRz1RANVt
scjwZ+x.ai8FCuQDgh9rpqwS2Fw7KJukqZiv8h4V4jZqn0Ngw.JpkJQotS4g
BomobqGX.X+DNaPR3j0c1ZgscpnAV1G2IBdh3VYkhWGuZjJ55dQasOV6kJdx
QJUCmHsm4NN.QopZsQTZCGZJ5BzpHRVwEoTZFcUTRF0wgldAZ+wyuSrcMfYP
s0bq0H2zYCAnEiADHDwakk1NEbCtsRRPq524Fccs99pZ8FdsUzrS61extlFt
xVpMNbI0pY6Vq06DpsA35QabS6noG1268eUIZzaCNGO.iGXqMxJI3FqEpJ6s
S01JK+1zCXPxQniINA62c2s7VwwTemDb6uh08mc7Zo8wW.dVIj2YMBP29CO5
Z+VOsb4v+OszeKw7c6tSXZ6Obe.ApO9p13VxV4WJUgk9jgXi3N4f7IdNbCja
XAH1YBdqGxCInd+mQ0I8V9R3RcWoOk6fZTETp3U8G61J0WAkTcsq+EgpKXTw
aE2v6psyqi2TcirttTWGf2zDpgb+3vtCdlQYcNbRQBFmuBnnXJij4o.hzzUP
g50yzAOnTRZRAh3DMIivRR8T4DZJ0QgNPMx96BgKB2.pHGkDn.VX3tlpFWUE
pGIroIJF8NsYLE3BZwn7cVckguUJBcKPyBzAm2NtA18vJ83FvgJGzAj84AiK
6J4GK.biVYGDF5x7qP0VzUt9bWIZjaz0a22mYlmOgkhodWGoflWDnRwnrhYd
i3VQcHwel1LBHnOtgyXjfeOGgvIyU10J2q2ZoxkhOVnQnEDbV3NGBlDVdBcd
r3jRuFc8uRF1IF0mmikOlYkyPo44ApmAvCywxRQA2Rl6GKPENoOjTrQ2zLat
.kfYEdHWjlv7vHOgTv7FTZ1n6kWVJT1Y5RcADuSJYvVb0iIGjV.YEMGpJKGL
4fOCgyyCTvoPH85dVJH9VasD5n8at1cGqvXBzvtF6y96LgEXJlL2nMGAFuZI
.Z0j+lmy+5PGhdGK3ERSGqsX8Y7mWC1OYxI54g9LPeYRwzzHWkdRJ9bCK381
Vdk3bGKdu8elzIYnSvyoNRmDVt6EsUuH0yU6+kuwMu53zhhgwlO4rKeLax7.
fMSKNmYVgOM4mp6DeBeLT8RcRwrrjvS.i.rvwB+A.Pi9d0aFg6wU5XsI8CBg
+7i72N.QD38qPqLFkRB0NDLFSO+.7KFg3cfPu2i59ElFxM3v4Gb+tv8IXGGc
tIAak+UeSML4BTZABkez2KfI9XgNK3bru+WJ3wSOqFPWyFg4KvjnuYmqKUD4
C+ovSZodjhm1M6r.PSXfBGBO49NYIYYzh9zQV+DVfiqfdj2x+2xf1aOG2iev
LiLLxCnBZRFpnelQFd96M+2Elr7cuguC5RtUGcor5VPr2w8C57zx+AnlyJ0N
-----------end_max5_patcher-----------

Ah right. I guess the ‘double-click to find the object’ thing only works when its a message and not an attribute.

My bad.


----------begin_max5_patcher----------
1021.3ocyXsziaaCD9r8uBAc1cAeJR0as8PtrE8vdnnHnXAsLWGlJKInGY2s
A4+dGNTRVxdiW6rNEwGjoFNCmu4IG6OubQ75xmrMwQ+bz6iVr3yKWr.I4Irn
+8Ew6LOkkaZP1h2YaZLaswqB60ZepEo+n8gQhkcs4111mqrgSNNN5u62pxzl
8AWw16qsYsgcUzaHqhnTo+Ktv+jwtgLJRQ2NWAbdn9Y8DcaPsVt9i+DOdOiA
MibR8D+xxk9GqNSiqv9HbhGYaY4tp2jskn7eIHm113GaazW21vyJN2UbXbDg
im9bCtorqNa.789un8HZiso0UXZckES3gF34H0Zpp9jstomYTEfG8ik09W0q
vWcEgWI3q01O4F3WhTL0fWqEbYc0HrheJQDGDsbistny0axPbDTYS6y4GZpE
lcAQ+ktMtx6ZMscM2+61htf6CLpGLc4sycDq29fKOOqLO.uEi6.Q99vabX2U
8jG488QjaXoBJUCtka3TthkfqfERIDvGbm8xPGDRHEoDlmUQBSIj3JMiK49U
jCDisWWDZZPCjTMQDVAjnftlJloXaNhblxmr0SsptrprdHjBhlNxeWa41ZyF
ms.8NDjNFhCtaLOpF1Ec6nOo2mtCbntAYlVhMFLtsKybp.vCkEsCLC4Y+Qks
H5NSQSzc1ct0k4a1WZYxx.LLy+yYfuDcDBI3TvUp.sItjXatc2ghpzIIJz2q
ITsNrBNEFatryDRnjTNxJKkqSCqjTRxAJb81YhkRDTEhSPFgREzEKMneYxnb
M.Ry7wn4PkAJ.MNnIBKjknIDpXtR8spP4t2U3KHsiYN7TFMIf0gTOlRK3zCQ
8qWLLln7UpGNybz4UD5w5.shH05vpi.3gUDICw7D+GUXU3j9wsf3eZxcPGs+
z2t6TEFS7qg6Ol9XnK7aDKv8dI9KCOALdghtP3YLmR0Go+p4+G.eHg+0SYQ9
FdbcMX7t1yzyCU7PeYV5zFK9ZGgjdsg0rYpdYfcAdq2bE8jZygZqiWchZSk1
ei1pWb0wh8C4cbyqNNunXX9ryN6BiYSlG.rYd50LyJLL6ul2YGFi7rKy4TUh
HzTcDfodRzuC.rt7whKFg6wkbr1j+cBg+1ylKGfDFbcenIohyYgZGFkR4We.
9tZq8a.gn2i6+DluveU70Gb+kMOu7wKFcZX1JUnyAUSw9aRviNuEBNBYi6e6
6FRYdlHD80x.51s1V+NXRzKF99TQBF9kvkkRzRnS6lcU.XcXfBOBO69NIhjD
dZe5npefTvwlxO4br++XP6smquG+kFpOknnDj0TtHgj1OcthJulVUqo5B9cP
2ZZKit0s8C.aeC5O7Cyw+SC+g1TYB+Ze7u9X4WV9e.2b.LA
-----------end_max5_patcher-----------

I think it’s more to do with how the error is produced. The magic Max API function that gets you the double-click-from-the-console behaviour is object_error – evidently, Max doesn’t call that internally when it encounters bad attributes, don’t know why (possibly it can’t rely on the object being in a valid state at that point).

2 Likes