Closed for Company Meetings: Between September 18 (5pm PDT) and September 22 (12pm PDT), Support and Sales requests will be delayed. Only time-sensitive issues will be addressed during that time. Thanks for your patience.
Debugging "jsobject: bad number"
May 06 2011 | 2:37 pm
I've made a series of changes to a .js file in a project, and suddenly the project is generating gazillions (to be exact: 2988) error messages stating "jsobject: bad number". The Max Window Object column is blank for these messages, there's just the text in the Message column.
It's not the .js file I've been working on that's generating the error messages -- I can drop it into an archived copy of my project and all is well. But the project has a dozen-and-a-half .js files, some of which are triggered by plain-vanilla Max objects that are triggered by the .js in question.
Is there any clever strategy for tracking down which JavaScript is the source of the error message? I can added a few dozen post() messages to each of the other .js files, but there oughta be a better way.
And, yes, I do know what "bad number" means, but I don't see any bad numbers anywhere. Just lots of good numbers.-|
It's a big project (>100 individual files), so not so easy to strip down to a single patch that demonstrates the issue.
- Feb 08 2013 | 9:56 pmHi Peter,did you found the source of your issue? This is just to share information - and maybe others will have the issue in the future: I ran into the same error message. In my case it was related to getvalueof() and the related [pattr] object. pattr couldn't handle when the return value of getvalueof() was null (in the meaning of undefined, not zero).cheers jan
- Feb 10 2013 | 7:32 amHi Jan,Thanks for your comment. To be honest, I don't remember how I eventually solved this problem. It may well have been something like what you mentioned.Thanks, -- Peter
