Dynamically creating and destroying containers

Dew Drop - May 8, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - May 8, 2008 | Alvin Ashcraft's Morning Dew — Thu, 08 May 2008 13:18:53 GMT

Pingback from Dew Drop - May 8, 2008 | Alvin Ashcraft's Morning Dew

re: Dynamically creating and destroying containers

BenHayat — Wed, 07 May 2008 23:54:55 GMT

Nick, sending you an email with my question

Thank you!

..Ben

re: Dynamically creating and destroying containers

Radiox — Wed, 07 May 2008 23:29:06 GMT

hi Ben,Jesse,

If I understand right, this is what you need:

instantiate a control from a separate xaml and show it from Page.xaml.cs, click on Close button and then, Page.xaml.cs will know about the click and act by hiding the control then removing it.

When you click close on the instantiated control, you call a method that activates an event:

public delegate void this_IsClosing();

public event this_Close isClosing;

private void ButtonClose_MouseLeftButtonUp(object sender, MouseButtonEventArgs e)

{

isClosing();

//you can hide it here if you wish

}

then, in Page.xaml.cs

//this instantiates your control

//make sure is known in the class

//so that you can remove it later

MyControl c= new MyControl();

c.isClosing+=new MyControl.this_Close(doTheTrickHere);

void doTheTrickHere()

{

//remove the control here

c.Visibility = Visibility.Collapsed;

LayoutRoot.Remove(c);

}

I have this implemented in my own application. If my explanation is not good, please let me know. nick At fastcom.ie

re: Dynamically creating and destroying containers

BenHayat — Wed, 07 May 2008 21:03:14 GMT

>>Entirely my fault, I didn't take the time to fully understand the problem<<

This is what I like about you, your honesty and being humble!!!

Not a problem... Trust me, this was posted on the forum a while back and the Only response I got, was to raise an event when the User Control's Close button was pressed.

Then in the main page, I have to have an event handler (who has subscribed to the raised event) to remove it from the Grid's children and set the form to null.

I'm getting closer to what I want to do, and that's why I thought I get a lift or hand holding on this last part.

I appreciate your effort and if you do get a chance, I'll still welcome your input!

..Ben

re: Dynamically creating and destroying containers

jesseliberty — Wed, 07 May 2008 19:32:27 GMT

Entirely my fault, I didn't take the time to fully understand the problem (though I did enjoy working through the problem I did understand!).

Okay, what you want is a bit harder (only in that I haven't thought through how to do it). I have two suggestions: (1) definately post it to the forums so that you are not waiting for me and (2) I'll try to work on that as well.

Thanks and sorry for missing the boat.

-j

re: Dynamically creating and destroying containers

BenHayat — Wed, 07 May 2008 18:10:42 GMT

Hi Jesse;

First thank you for your help. You asked me a series of questions and I answered them all to clarify an important point that you had missed in my first question and also sent you an email with screen shots that further described what I was looking for.

The solution you gave wasn't what I was asking. I was mainly asking about "Dynamically creating USER CONTROLS" from the main page and destroying them from main page. You created the stackpanel with two buttons on the same page. That's easy to close or destroy.

What I'm asking is, your create button should Instantiate a User Control that is in a separate Xaml file and separate class. Inside this User Control, there is a button that says "Close". When the user Clicks on this "Close" Button inside of the User Control, I want this close button to raise an event that the "MainPage" will respond to the event and then destroy the User Control.

If you go back to my last answers, I think I tried to clarify that the close button is in a different class and file than the one who created it.

That's where I got the challenge!

Hope thic clarifies it now!