Bug #157

readonly not properly implemented in jcom.parameter

Added by Trond Lossius almost 10 years ago. Updated about 6 years ago.

Status:RejectedStart date:2009-05-29
Priority:LowDue date:
Assignee:Trond Lossius% Done:

0%

Category:-Estimated time:1.00 hour
Target version:-Spent time:-
Branch: OS:

Description

The readonly attribute implementation is lacking:

If a value is receieved in the left inlet of jcom.parameter, we get spurious OSC messages from jcom.in and jcom.hub.

As the attribute does not seem to be used anyewhere yet, I guess this is low priority....

----------begin_max5_patcher----------
520.3oc2VsrSiCCEccxWgkW2o3G4QyrhuB1fPH2DSqQI1QIthBH92G+HsSYD
DLsATG1DGe801mywWeu943H3R0VdOD7av0fnnmiihblrFhF5GAaXaKqY8N2f
2UqjaZfy7CY9UHq4Z2X3Ai2ojZIqg67+JdWESxNXBpM5cyfLX0aR+XK2CE6t
vzvY.3RlbEDbyAqbu3ImWXzbzf4VltbsPt51Ndo1uBoolQAXeSJx0oXNZ+JI
pbnSs79egyfVauDGa+LKPcPxevL4czRy251XXaGukKq.Wn485IRkvumJc7BC
A4jj7hQEljiQXZ388rU72j6jyBtW3CGHKbM4uC4w+vHOk3ncBNMD1ilv6D2W
pZla3vWcRCa9hiRYnNIII2mrHcr6DKlZcQHOakEe.CM2G2rXLYIepkk0aVdt
pKCYQ7EURyGSVNpJK+mTgcH7.mg93Rro+LykR7bGivikKkN02MZYcFJq4cfK
suxv70vFPS+pacGpfK63rJkr9Q.dhhhnidG5zxuP7EjHevaQNTDcN.qEx+8o
qtcwZ+0JauZSW4NHO7juYf+tOUFUTHYZgRdnSIuxo0hpJta7cbpQT0pDR8.H
.27lmyAioj.vT12JjBRkLwX.b3PJKYdp8zNyekgtu2Ih07PvJ5ygUJovBOZg
q1WBcw9dmHXSCAreuQeAfH5IfHSmWh+CbZuUFC
-----------end_max5_patcher-----------


Related issues

Related to Modular - Bug #361: crash with /view/size:/value/inc Closed 2009-11-22
Copied to Max - Bug #1402: readonly not properly implemented in jcom.parameter Closed 2009-05-29

History

#1 Updated by Trond Lossius about 7 years ago

  • Status changed from New to Assigned
  • Assignee set to Trond Lossius

#2 Updated by Trond Lossius about 7 years ago

  • Target version set to core-maintenance-sprint

#3 Updated by Trond Lossius about 7 years ago

This bug is related to #361.

Updated test patch:


----------begin_max5_patcher----------
705.3oc4W1saaBCEG+ZxSgk0tLKEiwAxtp618.raplpbBtItBrQfSW6p569L
GSnsIAJMkxhztAjOFv+O+74C7iS7vK02KJwnugtB4483DOOvTkAu5wd3L98q
R4kviguckNa1VIdpaNi3dCX+hevyzY7c1UayjpTgAdIxyF0aM6a0Yx7PtvoC
LF8q5ox4lUajp0WWHVYbyxhm4OEQCgq99U2hrWadEYBHG8xa+Jghqr8zjIUW
l1SGznWuNULD9gTY5zUBmypjOgAdQPy0i5KA3lOTAOSXDEWKT7kovh4eB9Yl
nrjuVbvFYgfmnUoOf9B4nPHn13MZkoT9GX8IAVsOb6w6.Sb.r8RcCNNXBwuP
OJKYfY9dgjmdJ692jpsdPm69uxw8awwCZywsK.2fmhvK4p0cRgHHff3t4hQH
KZI5X9QovOEEIbEenibTheaWzCBbxKD4BUB5Binz7wI3oE53nU.ABfhVzIzB
6DZCXJEPDj+rnn9mQ8YfEpuKuJH1EY0BWH++vEJEHRH0uOfwenASKYRPOVqi
7IVFppBTuHyBnFLi0UlT7XxEo5L.KzXGch6BKQiIV1rc4+RtTW2003lE0EVl
OzX4Lpmcc3AIh81MsYiYO68JAyUJsgajZEL6AgTmA0jCbLj3S5plLcLywZ1L
PPiqKq7HThXkLimhtr4GmIe7PQZmIh8rHUfqqV.qypT8taO7x3ToZ+CLBJnx
9qwZodawpc5t9W0QOKgDKBkplXvqZTyKdlMxjDAL8NLkHKqRCRZOOnupo5DU
uobBGO4zC0PGM0vNq1ph5iZr+bFhzgbxjI4Z6QxqCdoggyX1N3D3zkgLZynm
WnAyAl2GGf79b.6garJNXgq7XbbynOA8S5Sp67wKWoW77Tycc043442IJJq+
lfTrMJtUWTMb9TXnT4FBeQbg3N4tmmMo5q8zj+RQyi2O
-----------end_max5_patcher-----------

The conclusion is that @readonly currently seem to be totally ignored.

Also some notes for further testing. A Spotlight search for readonly in Jamoma Modular indicates that it is currently used in the following files:

jcom.message.maxref.yml
jcom.parameter.cpp
jcom.parameter.h
jcom.parameter.maxref.yml
jcom.paramui.cpp
jcom.textslider.cpp
jcom.ui.cpp
jcom.ui.h
jcom.ui.internals.cpp
jmod.cueManager.maxpat
jmod.cueTrigger.maxpat
jmod.sur.ambi.decode~.maxpat
jmod.sur.input~.maxpat

#4 Updated by Nils Peters almost 7 years ago

Trond Lossius wrote:

This bug is related to #361.

Updated test patch:

what is the expected behavior for the @readonly attribute for the different inputs ?

#5 Updated by Trond Lossius almost 7 years ago

  • Target version deleted (core-maintenance-sprint)

Removing this issue from the core sprint. Postponing adressing of this issue to after the 0.6 release. We might want to revisit if the readonly attribute is at all needed.

#6 Updated by Trond Lossius about 6 years ago

  • Status changed from Assigned to Rejected

Also available in: Atom PDF