Feature Request #596

jcom.filter≈ doesn't yet support getTypes message

Added by Trond Lossius over 1 year ago. Updated 3 months ago.

Status:Closed Start date:2010-09-06
Priority:Normal Due date:
Assignee:- % Done:

100%
Category:- Spent time: -
Target version:(Jamoma Platform) - Kansas City Workshop Sprint 2011
Branch:

Description

This object doesn’t yet understand the getTypes message

Related issues

related to Foundation - Feature Request #997: Messages need separate Input and Output TTValues Closed 2011-10-21

Associated revisions

Revision ef822b79
Added by Tim Place 3 months ago

filter≈ help patcher no longer needs bogus args for 'getTypes' message thanks to 2-arg messages. closes #596.

History

#1
Updated by Nils Peters 7 months ago

  • Status changed from New to Resolved

Hi Trond,

getTypes doesn't work, but getTypes 1 works.
There is a small bug in the JAG wrapper, causes a get* message to have an additional argument (e.g., 1)

#2
Updated by Nils Peters 4 months ago

  • Target version set to Kansas City Workshop Sprint 2011

#4
Updated by Tim Place 3 months ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF