After looking through the Maxscript help docs and searching this forum, I’m still not sure about when/how to use .NET instead of ActiveX controls.
Is it true that no ActiveX controls will work in Max 64bit, or only some? For instance, I saw nothing in the help docs about making tabs with .NET, so does that mean that it’s ok to use ActiveX tabs in Max 64?
Also, I have a script that uses the ActiveX listview control. Will that not work for 64 bit users?
Thanks!
Well, for 9 and higher, you should consider switching to DotNet completely.
We found that if you installed Max 8 and then run Max 9 32 bit, it would use ActiveX without problems. But if you take a virgin Windows and install just Max 9, there will be no ActiveX controls for Listview and Treeview and your only hope is DotNet.
In 64 bit Windows, Microsoft decided to get rid of most ActiveX controls and not recompile them. So you should be using DotNet for Max 9, as people might use your script in both 32 and 64 bit Max on any machine, and that is the least common denominator now.
Hi Jon,
MAXScript help is not a .NET reference. You have a tab control in .NET : System.Windows.Forms.TabControl
I think that if you’re using Max 9 you have to always use .NET controls instead of ActiveX…
Also, .NET user controls are easier to create than ActiveX. .NET is the future…
[font=Verdana][/font][font=Verdana][/font]
Thanks, all, for your replies.
I guess I have some extra work cut out for me trying to learn this .NET stuff if I want to make nice interfaces. Gone are the good’ol days when the Maxscript reference was all you needed…
Thanks!
[sarcasm]
To add to the pile, I just LOVE how the maxscript reference makes NO mention of this compatibility issue in the ActiveX section. That way anyone working his — off on a script can make the whole thing using ActiveX before realizing that it’s complete bunk on a 64-bit system. =(
[/sarcasm]
Actually you just insulted Bobo there since he is, to my knowledge, the primary editor of the maxscript docs. On top of that it is documented in the reference:
-Eric
Ah. I do assert I have only succeeded in insulting myself. 🙁 I realize this is documented at the head of the DotNet section of the reference, as well as the “Changes in Maxscript” section. However, is there a reference to this problem in the “ActiveX” title page of the reference? This is sort of like telling people in town that the volcano is dangerous, but not putting up signs near it.
Note, too, that I have no malicious criticisms for Bobo. He’s a fine forum contributor, and has helped me several times.