Hi Jon,

Your solution ( as I mentioned before ) works fine when the btnTriggerIMC_Click() is fired for the first time ( the module collapses programmatically  ), but when a user clicks the modulecontainer MinMax button the state is persisted in a cookie. If a user clicks the button, which fires the btnTriggerIMC_Click() for the second time, the module does not collapse.

I hope you can help me out.

Thanks in advance!!

Hi Jon,

thanks for the quick response !!

with the code sample you gave in this forum thread it is possible to collapse the module programmatically. That is when the IMC is triggered. the button which triggers the IMC is an ImageButton in a datagrid. that all goes well.

The page on which the module is included, the MinMax button on the right top of the module can be clicked by the user. When this is done, then the state is persisted in a cookie and that is where the problems begin. Because the user manually expanded the module, the grid is visible again. If the user will click the ImageButton on the datagrid which triggers the IMC, the module will not collapse and the image of the MinMax button does not change. I hope the problems that I am experiencing are now clear to you.

Thanks in advance !!!

Greetings

Hi Jon,

Yes the code you stated has been implemented. It works fine until a user clicks the minmax button on the right top of the module.

Greetings