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 as the argument (i.e. buffer~ ).

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

ps is the font spec (magic number 196617) documented anywhere? 

works fine in Max 4, but in 5 will give an object with  as the argument (i.e. buffer~ ).

Workaround is to rewrite everything using newObject, e.g. 

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

ps is the font spec (magic number 196617) documented anywhere? 


max-5newdefault-args-broken

RE the font spec - found Peter Castine's explanation in message #30323 (should have looked harder earlier...).

hey rp, can you link to the right thread, I'm having the same problem but you cant search by post number on this forum

https://cycling74.com/forums/index.php?t=msg&goto=30323&rid=6945&S=2e198e638b3995b4c4d64b16faab7b11&srch=castine+fontlist#msg_30323

[MAX 5]newDefault args broken?