I have used C# for developing software, since recently started with max projects…
I have a problem if i create custom user control, for a test i just made simple button
–loaded dotNet.loadAssembly my control as dll
then
–Made the dotNetObject control
btn = dotNetObject “DotNetMaxTest.testing”
–Made the form
frm = dotNetObject “MaxCustomControls.MaxForm”
–Allso tried with System.Windows.Forms.Form
–Then Added the button
frm.controls.Add btn
–Made event handler function
function bp =
(
print “Button is pressed”
)
–Linked the event handler
dotNet.addEventHandler btn “click” bp
–Set lifetime so that eventhandler dont go out with trash
dotNet.setLifetimeControl btn #dotnet
–And finally displayed the form
frm.show()
And i get my event handler triggered nicely but just under the button, where actually is gray area when i created custom button control… so when i click on button nothing happens but if i click right next to a button event gets triggered… can anyone please help me a little bit with this. Somenthing got lost in translation because of unawareness of c# that MaxScript exists or somenthing like that…
I hope this was clear enough explanation.
Looks like you’re doing things right, have you tried the same code but with a regular dn button?
-Johan
If you think using somenthing like
btn = dotNetObject “System.Windows.Controls.Button”
I did and if i attach event handler to it it works just fine…
if i understood you correctly.
But the problem is i want to do a custom controll… so i do dotNet.loadAssembly of my custom control dll. And using it like that i get problem from my initial post.
I understand, why I was asking is that we now know the problem is in the assembly. I have made custom .net tools too and many others here, so my guess is it’s in the assembly. Have you overwritten the button handler from the custom control, is it exposed as public etc? Many thing can be the problem.
-Johan
I understaind… I have not changed button control in any way. I used the default one just added it as custom control as a test because im planning to make ui for my max scripts. Basicaly i just draged and droped button as custom control then compiled it as dll and tried to use it in max.
Then the problem is quite simple. You have assigned the click handler to the base of the control. Not the button of the control. You should have overriden the click handler of the base to bypass it through to the button control in the custom control.have created. Or you create a new eventhandler and patch it though to the button. And a third way is to create the eventhandlers in the dotnet control and use the ManagedServices.dll MaxSDK class to execute maxscript code via the control.
Hope this helps,
-Johan
I think you are bang on with this Johan. In my controls I always pass the event on a composite control to a new user control level event with a custom eventarg class as I can explicitly control the data that is getting passed to max.
…In my controls I always pass the event on a composite control to a new user control level event with a custom eventarg class as I can explicitly control the data that is getting passed to max.
it’s too long English. Could you break it for not natives please?
Could you give a small example for a simple button like im trying to do,
The thing i dont understaind is:
if i call event handler for a button in maxscript… like this:
function bp =
(
print “Button is pressed”
)
dotNet.addEventHandler btn “click” bp
dotNet.setLifetimeControl btn #dotnet
how does it relates with event handler i made in C# or does it relate at all…
EDIT: I have managed to get it to work with
Managed.Services.MaxscriptSDK.ExecuteMaxscriptCommand();
wich is good, but the problem with eventhandler thats created in maxscript still remains…
The problem is that when you add a custom control in max, you’re assigning every event handler to the base of that control. So in visual studio, you should have overriden the click event handler so that it invokes the button and not the control base, spend some time on the internet to read about custom controls. This is not a max problem it’s a problem you have with creating a flawed usercontrol. This same problem you have here, would be the same as if you’d use your custom control in some dotnet application.
-Johan