View Full Version : dotNetPropertyInspector
03-16-2009, 03:25 PM
Created a little utility that I thought others might find useful. Check the following post for screenshot and .ms file.
Basically this is a utility to allow a user to temporarily modify a dotNet component's properties in a propertyGrid, you can then take note of what properties there are what values work well, rapidly prototype look of UI's, etc. Basically the ability that VS gives you, but inside Max.
03-16-2009, 03:38 PM
nice one dave! been meaning to write something like this for a while, but never got round to it, I'm always tending to have VS/reflector open at the same time and shuttling between the two!
03-16-2009, 05:15 PM
Cool! Very usefull!
Could you maybe upload it somewhere where I don't need to register to download?
(I'm lazy...yes I know)
Great work Dave. This will help a lot. So you have Max script calling on dotNet to display dotNet properties in Max script, doesn't this cause some sort of infinite quazality loop and you run the risk of having your whole office just disappear?
03-16-2009, 06:05 PM
I did a quick search but I'm in a hurry and couldn't get any concrete info but it would be cool to have your app "docked" (not actually docked in max but still that's a good idea) and click a button "Inspect" and then click the dotnet control in our form/rollout and have that inspected... dunno If I made myself clear but it's simple, something like Spy++ so that we can have your property inspector running all time without having to insert code in our app. I took a quick look at sendmessage() and findwindow() dunno if it's the right path to go and you needed to write a custom class to do that... maybe there's another way, speak up guys! Cheers (in a hurry here sorry :P)
03-16-2009, 06:23 PM
.zip file attached for those that don't have a TechArtist.org account. Silly me I thought everyone did, its all the rage. :P
Good catch! I forgot to include the callback that prevents said office implosion! Upload incoming soon!
Interesting idea. Have to poke around later tonite to see what options there are.
The thing that will make this really useful is to get it to dump out usable data that can be included in script to initialize the tools we create. Need to spend a bit more time on that one as I suspect it will be a bit tricky. We'll see.
03-16-2009, 11:25 PM
That looks interesting Dave.
As many dotNet mascripters are there, here is a script also using a PropertyGrid that let the user select a node in the viewport and edit its properties. You can select whatever node object type. The PropertyGrid SelectedObject class and instance are built at runtime...
At the moment only integer, float and boolean values in properties are supported.
So, with this dialog you can edit an object parameters withing going to modifier panel or type in the listener.
03-16-2009, 11:41 PM
What an obvious, and good idea. Thanks, both!
03-17-2009, 03:59 AM
very cool Ypuech, some interesting stuff there that I did not know that you could do, gunna have to wrap my brain around that one. :)
03-17-2009, 09:49 AM
WOW cool man, thanks for sharing
03-17-2009, 12:16 PM
I will try to add multi-selection edition over node objects of the same type. I think that would be very powerfull because it's not really always implemented in the modify panel.
Also INode and Modifiers properties in the PropertyGrid.
03-17-2009, 12:16 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.