InfoPath Dev

Hi there,

A custom toolbar button does not use the same function syntax as a form button does.

I haven't done these for a while, but if I recall correctly, you just need to create a public function of the same name as the toolbar button name, no parameters:

public void btnTest()
{
...
}

Thanks Greg!!
What if I want to check something and then I want to stop the button action.
For example:

        public void btnCancel_Click(DocActionEvent e)
        {
               e.ReturnStatus = false;
        } 

The "e" will return false so that the button's event will be stopped.

Anyways that I can do the same thing???

Since there is no event object, and the function returns void, whenever you want to stop processing the button click, just do a "return;".

Well, I tried using the "return" keyword. It surely stopped the process of other commands underneath it. But somehow, that's not what I want.
If we have the DocAction object, we can just set it to "false", then other commands underneath it are still able to process until the end. Then, because of setting the DocAction object to "false",
The commandBar onClick will stop processing.

The intention behind this is that i write another method to hook up with the existed toolbar. Once the user click that commandBar button, they are supposed to execute my code from my method first. Once they get out from my method, the other code (dont know where it is, and don't wanna care about it as well since it's abstracted from being known) which is written for that commandBar button will be executed. If I am able to set the DocAction object to "false", I would be able to stop the process of that button right after it finishes running code in my method (so that it will not execute the other code which is written somewhere else).

So, any suggestion??? :(

Thanks

I'm not sure what this other code is you refer to. As I understand it, when you "create" a custom toolbar button, you process it as we describe. That's it. Nothing else runs. Now I don't know everything about custom toolbars, so maybe there's some process of running some other code. In that case, here's my suggestion. Set some value in a secondary DOM indicating the success status of your button code. Then when the other code runs, it can check the value of that secondary DOM node to see what it should do. But I'm not so sure that there is going to be any other code running--though I could be wrong.