[Closed] Are DotNet ListViews behaving different in Max 2010?
Does anyone know if DotNet ListViews are being handled differently in Max 2010 than they were in previous releases of Max? I have some drag ‘n drop functionality built into one of my tools, and it runs great on previous releases, but in Max 2010 there’s some weird stuff going on. Maybe involving index numbers or something… it’s a mess and I can’t really describe it in any greater detail than that yet.
Anyone else have problems with ListViews in Max 2010?
I have not seen direct problems like that but then again I have not tried any drag and drop code in 2010 as of yet. Do you have any code that we can test here? A simple example of what is happening? I know that there is an issue that is stopping my scripted plugins from loading correctly in 2010 but I can’t see that issue having an affect with drag and drop but I could be wrong.
Thanks, Paul
Unfortunately my listview code was tied into a ton of other extraneous code, so it would have been quite time comsuming to prepare a stripped-down example to post. I posted in the hopes that my vague question would have connected immediately with someone with the same problem.
I’ve reworked the part of my code that creates the listview items, and now it works fine in Max 2010. In doing so, I had found some possible logical problems in my code that oddly enough didn’t trip up old versions of Max, but evidenlty did cause problems in 2010. It’s just strange that somewhere in there the maxscript or the dotnet stuff runs differently in those versions.
Thanks again.