For the record, I use Win7 – 3dsmax 2012 x64
Maybe Windows version difference, as Miauu said.
Hey guys, why is the discussion stopped. Are you tired?
Anyway I will jump to another topis if you not mind. It’s related to this post by try2script.
I recently find out that max2014 not allow ei crash when you try to dock rollout dialogs with .net controls. Some tools that we use on a daily basis sometimes must remain open during the work but the size of dialog may be too large and covers most of the viewport working space
Maybe is there a better solution for docking or minimizing but as workaround I decide to rewrite from scratch “group” tool to .net example. Options are shown on the image below
.
Any good suggestion idea or comment are welcome.
Perhaps you could have a MacroScript to move them on/off screen?
I am not sure if by opened you mean visible too, but you could use either a button or a hotkey.
The author is already used .net buttons. He like popup effect when moving mouse across the buttons. I know the way how to do the same only with mxs but in this case .net UI has prevailed.
i’m busy… i wrote about 1,000 lines of code for last two days. it will be a new rigging tool
the next subject which i want to discuss is the combining mxs rollout with dotnet controls
Ok Denis,get some rest, this can wait. Maybe this topic can be continued when we talk about only .net
Thank you for this great interface, you removed even the shadow, so it really looks like integrated in max menu! I think, if you add option – right click to any btn => dissapear the top of the tool at all, then it will really look like an integrated tool! When you press right click again, then top appears and works the same like it does now!
But even without this, your solution is original and works in max 2012 and 2014!
How do you plan to move your form when you remove top label?
Then you need to add MMB click event on every button, but that will be bad choise for sure.
I suggest you to use existing look and put the rest of fn’s for buttons (group methods)
there are two ways to use .net forms objects in mxs rollout:
use dotnetcontrols
use one dotnetcontrol (let’s say UserControl) and add all other .net controls as its children
what is better?
where is a difference?
does one method make any advantage against another?
I don’t know what is better because I never used UserControl method.
But the first method has some annoying downsides: dotnet gui elements don’t have the same behavior when they are embedded in a max rollout, especially the text editing part.
Escape and Enter keys are not handled by the keyborad handlers. A few topics talk about that in the forum. It needs some hook tp get them working right.
also for first methde: there are another problem, when youre using loadassembly , sometimes it doesnt work Correctly as dotnetControl, but if Im using 2nd metdhods it working…sometimes while ago, Im use assembly vista control,split button, when Im using it as dotnetcontrol button everything work correctly as I push the button but when it came to dropdown button where it using contextmenu it doesnt work and causing error everytime I leave those control after open , but when Im using second method I have meet no problem at all.
Bassicly using dotnetcontrol as children almost the same as using form in maxscript.