I wanted to see how to shorten some of these expressions if possible as I'm still learning...It´s a script that'll toggle meshes between High Quality Display and Low Quality Display. Some of my bigger concerns are three: 1-To set something to HQ, I believe the only flag needed is -polygonObject, even though in the Script…
1) Those options are all for nurbs objects, the hotkey is designed as a catch-all. So if you're only going to be using polygons, you don't need to worry about it. 2) I'm not sure about polygonobject = 0, I thought maybe it was some legacy thing or used in subdiv surfaces, but a fresh primitive or import return 0 until I…
In the code you posted, if objects have po=3 then they will only be toggled to 1 if no other object is 1. Let me know if there's something you didn't understand. The strangest thing might be the enumerate function, which returns a tuple (a read-only array) that is being unpacked into the 'index, v' variables (aka multiple…
The thing with toggling is that if the selected objects have different modes then it's best to set everyone to the same mode first, and then only toggle when all objects have the same mode. This is how most software do it. Also, displaySmoothness seems to take an object list as parameter, and return lists as well, maybe…
@throttlekitty Thank you for the answers man :) You're totally right with using the getPOValue <= [1L] expression too! @RN And that's the exact behaviour I'm doing here, no? Also it's the first time I see a for expression using that kind of syntax, I'll have to read a bit to understand that haha...Thanks for showing me…