ajm objects 0.9 beta 1

1 view
Skip to first unread message

Adam Murray

unread,
Aug 7, 2010, 4:53:28 PM8/7/10
to ajm objects
A new beta version of ajm objects is ready for testing:
http://compusition.com/ajm-objects/ajm-objects-0.9b1.zip

Please start a discussion for any problems you encounter, with a patch
and/or script demonstrating the bug if possible.


Known issues:
* "require" of a custom script (i.e. not a built-in ruby library) may
not work with relative paths.
This used to work when the file was on the Max file path. I think you
can use absolute paths as a workaround in the meantime.

* textedit doesn't really work for inputting scripts anymore, due to a
bug in Max where newlines are stripped out of the text. I brought the
issue to Cycling 74's attention. In general I recommend using
@scriptfile and writing your scripts in a separate text editor
program. See the "script files" section of the ajm.ruby help patch. I
think it's also possible to use the text object instead of textedit
(example forthcoming).

* Some ruby types, such as subclasses of Ruby Numeric, may fail to
convert into a Max datatype. In the "Ruby API Hooks" section of the
help patch, the Complex number examples fails with this error:
<script>:1: could not coerce Complex to class java.lang.Object
(TypeError)
This is a bug in JRuby 1.5 that I am working to get resolved with the
JRuby developers. If you run into a similar problem, you can convert
the Ruby object into a type that Max understands inside your Ruby
script. Converting to a String is usually the best option, so for
example with complex numbers I could call complexNumber.to_s to avoid
this error in the help patch.

* at_exit doesn't behave properly anymore
For now I think you may need to avoid using at_exit and write an
explicit cleanup function that you call as needed.
Reply all
Reply to author
Forward
0 new messages