Just installed max2013 and I noticed that the cui config file was now in xml format. I did a quick search in the mxs help and could not find any information about the change.
Is there a quick, built-in way to read settings from the file?
E.g if I want to get the height of the command panel I previously used:
((l = (filterString (getINIsetting (cui.getConfigFile()) "Command Panel" "DRect") " "))[4] as integer) - l[2] as integer
straight in mxs, but in max2013 I had to use Xml.Linq in C# to extract the same data, which is a bit more cumbersome:
XElement element = XElement.Load(file);
return
(from item in element.Descendants("DRect")
where (string)item.Parent.Attribute("name") == "Command Panel"
select (int)item.Attribute("bottom") - (int)item.Attribute("top")).First();
//or in a less readable form
return
element.Descendants("DRect").Where(x => (string)x.Parent.Attribute("name") == "Command Panel").Select(x => (int)x.Attribute("bottom") - (int)x.Attribute("top")).First();
i’ve not tasted max 2013 yet… are you serious about this change? f*ck! what is going on?! it pisses me off!
how long the max will rape its real users? all features after max 2009 are just the toying of someone who never worked with max.
SHAME!
har har
this change is indeed a very good one, but don’t expect to suddenly find logic in all of those strange magic numbers used everywhere …
good? i’ve stopped the supporting of my tools any earlier than 2-3 versions behind the recent because of every-time dramatic changes. a tool itself might work fine but its ini settings are screwed up.
Maybe the reason for the change has something to do with support for multiple viewpanels. INI files are not great when you have a variable amount of something.
At least an XML is a structured file and can be handled by standard tools in an organized manner. And i see this as first a step on the way to a possible UI data migration tool.
ini files are a horrible mess when used with more complex data, as the old ui files show…
I really thought your post was meant ironically because of all the other complaints Max 2013 recieves… but well, seems i was wrong
I don’t mind xml, but a note about the change in the help with some elegant ways of retrieving the settings in mxs would be nice.
i am not against anything that makes max better. i just see that the max developers don’t care about people who worked with max for many years. many bugs those i was reported are still there but they add a lot of rubbish with no request and with no sense!
who could get an idea to make this stupid caddy-candy control? the only person how never worked in max!
yes – that’s true for sure, thus i think such small improvements on a totally “non eyecandy” side of things provide some glimpse of hope…
But in reality i think they would’nt have done this if they would’nt have been forced to do so with their unicode effort, which was a company wide change AFAIK
I guess INI files would’nt support unicode ?
i think that 90% of autodesk profit is coming from AUTOCAD. and as i see they don’t do these experiments with the autocad users.
look at Maya today where i worked for many years. It makes me sick looking on the last cell-phone kind design.
maybe i am an old grumbler … well. just ignore my grumbling.
Sure not, Max needs some competent crumblers. The day all grumbling disappears or comes from silly bashers only without well founded arguments, is the day Max is a dead product. Or a tool for casual users only.
new autocad looks bad too… i’ve just looked at. i have noting to say.
it seams like a time for me to play chess in a park…
I think all this eyecandy “goodness” in Autocad and Inventor is already several releases old. So this is nothing new. And sadly enough those packages seem to be the main design decision driving packages for 3ds Max too…
AutoCAD has migration tool at least while 3ds max’s not, and there’s no hope of appearance of such tool. Have to recreate 2012 gui in 2013 max manually :banghead:
update: there’s a way to load old cui’s in 2013, though it is not safe – http://www.the-area.com/forum/autodesk-3ds-max/autodesk-3ds-max–3ds-max-design-2013/max-2013—–max-doesnt-remember-custom-shortcuts/