Cary OConnor Posted April 10, 2006 Share Posted April 10, 2006 Hi All, We are currently considering removing VBA support from IronCAD in version 9.0. Is anyone using VBA? IronCAD will continue to support its API that uses both VB and C++ development environments. Please let us know if you are currently using VBA. Thanks, Cary Quote Link to comment Share on other sites More sharing options...
Guest ebedding Posted April 11, 2006 Share Posted April 11, 2006 (edited) I have heard C++ is a better & more powerful development environment for faster & more robust code? I have also heard VBA is possibly easier to learn & use? I only need to do some simple customization, and anything Ironcad can provide to make that easier for me would be great. Ironcad support of both C++ and VBA is probably time consuming? Would the effort be better spent on important core software enhancements. Are there any additional Pro's & Cons surrounding this issue? Edited April 11, 2006 by ebedding Quote Link to comment Share on other sites More sharing options...
Cary OConnor Posted April 11, 2006 Author Share Posted April 11, 2006 Well there is additional work to maintain the VBA support and it could have side effects on operations in IronCAD. In addition, if we want to allow users to install both IronCAD and Inovate on the same machine, we need to remove VBA. VBA is really for customizations that are tied to a scene. The API using C++ has more power and debugging capabilities so it is better to use. Cary Quote Link to comment Share on other sites More sharing options...
Robert Andersson Posted April 11, 2006 Share Posted April 11, 2006 Soo this is what you suggest? 1. IronCAD 9.0 will use a API that could be used to program applications in both C++ and VB. 2. The old VBA automation envirement will be removed. Quote Link to comment Share on other sites More sharing options...
Cary OConnor Posted April 11, 2006 Author Share Posted April 11, 2006 Hi Robert, The ICAPI today can support VB or C++. The old automation interface will still exist unsupported as is today. VBA is an additional capability. VBA works in the scene under Macros... Basically it uses the old automation interface and programs within a particular scene versus a general VB add-on that can run on any scene. To my knowledge, very few people have used this. I older versions of IronCAD, we had a double-click pop-up camera orientation tool for scenes. This was using VBA. Hope that helps. Cary Quote Link to comment Share on other sites More sharing options...
B. Ludin Posted April 12, 2006 Share Posted April 12, 2006 Hi Cary I'm using an extended version of the camera direction tool. Now if you would be willing to add the 4 missing standard views to the camera picker toolbar, I would give you my blessings for removing VBA support Cheers, Beat Quote Link to comment Share on other sites More sharing options...
Cary OConnor Posted April 12, 2006 Author Share Posted April 12, 2006 What views are missing? Cary Quote Link to comment Share on other sites More sharing options...
mpawlak Posted April 13, 2006 Share Posted April 13, 2006 Top-Rear-Left, Top-Rear-Right, Bottom-Rear-Left, Bottom-Rear-Right Quote Link to comment Share on other sites More sharing options...
B. Ludin Posted April 15, 2006 Share Posted April 15, 2006 Precisely! And while you're at it, could you add them to the drawing environment, too? Thanks in advance Beat Quote Link to comment Share on other sites More sharing options...
lewishugh@yahoo.com Posted October 19, 2020 Share Posted October 19, 2020 I agree with adding the four missing views. Or, in the alternative, tell me how to add them to the camera picker as a permanent addition. Thanks Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.