[java-dev] [MAX 5]newDefault args broken?
Richard Polfreman
r.polfreman at soton.ac.uk
Fri May 9 05:31:41 MDT 2008
- Previous message: [java-dev] Re: Re: Announce: Python for MaxMSP (beta)
- Next message: [java-dev] Re: [MAX 5]newDefault args broken?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
newDefault() appears to fail to pass on arguments to objects in 5. Thus:
MaxBox buf = p.newDefault(80,20,"buffer~", Atom.parse("fred"));
works fine in Max 4, but in 5 will give an object with <unknown> as the argument (i.e. buffer~ <unknown>).
Workaround is to rewrite everything using newObject, e.g.
MaxBox buf = p.newObject("newex",Atom.parse("80 20 100 196617 buffer~ fred"));
tested on Max 5.0.1, PowerBook G4 1.3GHz, Mac OS X 10.4.11 and MacBook Pro 2.16GHz, Windows XP SP2, jdk 1.6.0_03
rp
ps is the font spec (magic number 196617) documented anywhere?
- Previous message: [java-dev] Re: Re: Announce: Python for MaxMSP (beta)
- Next message: [java-dev] Re: [MAX 5]newDefault args broken?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
