I really cant find the answer to to following problem. (minimize container from code-behind..)

http://www.xs4all.nl/~walaco/minmax.jpg

Greetings Walaca

Have you looked under module settings under Advanced?

 

Bruce

Hi Bruce,

Thanks for the effort,.. but

I don't think we are talking about the same thing. The search module as described is, like normal, just maximized. That's okay. But when user action in the module itself take place (by user clicking on a grid row in my example) I want to collapse the module from the code behind.

I, as logged on administrator,  do not want to configure the module to be minimized in the first place. Collapsing of the module only has to take place when a user does something with the content of the module.

Do you have anymore suggestions

In your diagram you say that you tried to set the value in the Page_load event. Have you tried the same code in the Page_Init event of your module? I had a similar issue where I wanted to override the Container's title with code in my module. This had to be done in Page_Init. By the time Page_load fired it was too late.

okay, I misunderstood. I'm thinking you will need to do this in the onchange event. I'm thinking (and I have not tested this) that you should be able to use the Client API. Take a look in the documentation at the file Client API MinMax.doc and post some code for us to look at. If you can use the client API then maybe Jon can jump in here and clarify exactly how.

 

Bruce

  

You can probably do this with the ClientAPI as well. The MinMax info for a container is persisted as a cookie. So, you may be able to directly change the cookie from the client. In the ClientAPI there is a property called MinMaxContentVisibile(). You should be able to use this.

But, I believe you should be able to handle it on the server in a postback as well. The problem (I think) is that the minmax control (Visibility.ascx) is part of the container, not the module. I believe the approach mentioned in the post as this.ModuleConfiguration.Visibility = VisibilityState.Minimize will work. However, it won't work when executed in the Page_Load of the module because the Page_load for the container has already completed its processing. When you want your module to affect the state of the container you have to put the code in an event that runs before the module's Load event. So, if you move the code to the module's Page_Init event it should work.