Code

Re: Dynamically enable/disable "changed" Event handlers?

Th Calu — Wed, 12 Sep 2018 14:02:55 GMT

Thanks for your quick answer.... At this time, I did like you (using a global flag), but It's not a perfect solution against events bubbling, performances etc... I try with delegate, addhandler/removehandler, syntax of InfoPath 2003 etc... without any succes :(

Re: Dynamically enable/disable "changed" Event handlers?

meissen — Wed, 12 Sep 2018 11:44:40 GMT

I haven't found a solution as of yet. I just use a global flag and if it's not true I exit the procedure.

Re: Dynamically enable/disable "changed" Event handlers?

Th Calu — Wed, 12 Sep 2018 09:15:13 GMT

Hello, did somebody find a solution ?

Dynamically enable/disable "changed" Event handlers?

meissen — Mon, 29 Aug 2016 20:09:48 GMT

Does anyone know if there's a way to programmatically enable/disable "Changed" event handlers in VB? I have a form with 11 repeating sections that are built out using VB loops. Each time a row is added, my "Changed" event handlers get triggered. Although the first line of the "Changed" event sub is an "if not (flag) then return" which stops the Changed event at the first line of the sub, it still slows down my code execution. With the event handlers enabled I'm averaging ~142 seconds to execute my loops. With the event handlers disabled, I'm averaging 80 seconds. Big difference when you're waiting for the form to build out and be usable.

I have already tried moving "AddHandler" and "RemoveHandler" outside of the Startup method and received error messages for such. Was wondering if anyone else knew of some tricks to stop these change events from triggering?