Notifications
Clear all

[Closed] 3dsmax ListView options

Hey all,

I’ve been out of max development for about a year or so – what are the current options / constraints for list views? I guess it’s between AX and .net, so I guess that means I need to make a call on which max version to support up to (which one!?), or write some wrapper scripts to let me access either.

Is that correct?

Cheers,
Dave

7 Replies

AX is pretty much out these days to anything above Max9 – with the exception of the 32 bit platform. You should look to convert/ or write any new tools using dotnet versions of things like trees and lists, IMHO. there is a section in the help about converting these

Ah, cool, thanks Pete.

Has anyone made a list of all the freely available and useful to mx .net controls yet?
I tried this with AX, but so many of them just wouldn’t work within max.

Woah – loads of properties, methods, etc!

I hate hacking around in the editor for this sort of thing. Is it better to build stuff in Visual Studio, making use of the intellisense, then port the code to max after?

I found both Visual Studio Express and especially Bobo’s WIP DotNet reference very very helpful.

www.scriptspot.com/bobo -> dotNet and Max9
msdn.microsoft.com -> Library

Regards,
Thorsten

Absolutely get VS express edition. Specifically, looking at the designer file in Visual Studio shows you how it handles various properties, and the class type it is expecting (for example to move the position of text on a button needs a contentalignment class passed as the property)

It’s way faster than probing about in max. You can see the designer (it’s not there by default, you have to show it as VS doesn’t recommend you alter it) by pressing “show all files” in the solution explorer.

 PEN

I have tutorials as well on my site.

http://www.paulneale.com/tutorials/dotNet/dotNet.htm

It’s worth getting used to using the MSDN .net2 class library reference , too – mostly, under System.Windows.Forms. The other-language examples give a good idea of the intended usage, and give you cross-referencing, which is sometimes easier than ploughing through the references of a VS solution. I’m not a natural-born fan of MS, but the more you use this, the more you realise how superbly the framework, (and its docs) are designed.