Quantrix 4.0.46 Update

6.77K viewsQuantrix Announcements


We released 4.0.46 today. The changes focus on the auto-complete functionality of Scripting. Specifically:

-Since java.awt.Color is part of our Scripting API, we should automatically import it for users
-Autocomplete should find the best method declaration, not the last
-Autocomplete throwing NPE in strict mode
-Autocomplete: user defined method invocation not completing correctly
-Autocomplete: Don’t autobox static primitive types
-Quantrix Viewer not building correctly
-Completions appear within comments
-Variables aren’t being tracked for autocompletion
-Improve Autocomplete: Allow for method invocations as parameters
-Improve Autocomplete: allow for new variable invocations and static reference autocompletion

4.0 Beta Users can get the software via Help > Update. Alternatively, you can download the files from this direct URL:


Please send along any feedback or questions to [email:v0uz36ye]support@quantrix.com[/email:v0uz36ye]. Thanks!



I buy a new iMac 27″.
When I enlarge to the maximum size the window, it’s impossible to select the formula toolbar icons.

Only when I reduce the dimensions and the toolbar is automatically replaced below the model toolbar, the problem is solved.




No problem Simonh – 4.0 basically has a bow on it… we are just tying up some Qloud functionality and hope to have it out the door soon! We are actively in the planning stages for 4.1 and we will evaluate this and other scripting requests for future releases.

Thank you very much for your feedback!



OK – does 4.1 mean after the initial release of V4 – i.e. we’ll have to live with this situation for some time? (I’m not asking you to commit to any dates :) but just to understand what “4.1” means in terms of your planning process)




Hi Simon,

This is a known issue, and something we will look at fixing for 4.1. Sorry for any interim inconvenience.



Extended Autocomplete is very useful, but since it works across imported libraries also, performance in the Scripting Console is painfully slow with a large import – response to typed character can be c. 1 sec. (At least I’m guessing that is what is going on).

I thought this issue was introduced with 4.0.46 but having reverted to 4.0.44 I can say that is not true. The problem exists in the prior version also. But removing the imported library does fix it. So whatever class introspection you are doing when applied to imported code is too slow to be viable.