Bug #280

jcom.parameter bug with ramp function when changing type attribute via jcom.hub

Added by Julien Rabin almost 12 years ago. Updated almost 9 years ago.

Status:ClosedStart date:2009-08-13
Priority:NormalDue date:
Assignee:Tim Place% Done:


Category:-Spent time:0.20 hour
Target version:0.5.5
Branch: OS:


As explained in the patch attached, it seems the ramp function does not work anymore once the :/type attribute has been set via a message to jcom.hub (for example from integer to decimal). Actually, setting type as decimal via jcom.hub for a jcom.param which is already set as decimal also prevents the ramp function from working.

OS 10.5

type-bug.maxpat (8.38 KB) Julien Rabin, 2009-08-13 01:16 pm


#1 Updated by Pascal Baltazar almost 12 years ago

  • Assignee set to Tim Place
  • Target version set to 0.5.1

as reported to the devel list, this bug is not related to the new types names, as he was occuring on previous versions (with msg_float and such...)

#2 Updated by Tim Place over 11 years ago

  • Target version changed from 0.5.1 to 0.5.2

#3 Updated by Nils Peters over 9 years ago

  • Target version changed from 0.5.2 to 0.5.5

#4 Updated by Pascal Baltazar almost 9 years ago

  • Status changed from New to Closed

This is now working - I guess it has been fixed by Trond's work on dataspace and ramping ?

Anyway, it works, so I'm closing the issue

Also available in: Atom PDF