As I can see, wide majority of beginner suffer from "button sickness". They learn buttons first and stick then everywhere. If you see that some control can solve some problem, it does not mean that you should do it.
The user does not expect that each click on a button arranged in an array will modify your "changeable part". The user expects if from, for example,
. The first look at your picture suggests that you come to the design from a wrong side. By the way, one advice on design: when presenting a sample, never write abstract general text like "Button". Always write real words from the application fields, even when the application does nothing. This habit will help you to avoid many future mistakes. Right now, it creates the impression that you don't care about real user's need and act by a rigid and overly abstract schema which resides in your head; and there is no a room for the knowledge on the application field. It could be only the impression, though, but you don't have to give such impression.
Hatem Ghazy wrote:What are the suitable controls containers I should use?
This question suffers from the lack of logic. How do you think, why do different choices even exist? Because no one of them is the best. It all depends. Which one to chose depends on a number of factors: context, requirements, even the present industrial culture in the user's application field. Nothing can help you until you analyze all that stuff.
Same thing about some other questions on the choice of controls and expressive capabilities. First of all, you need to learn these controls, majority of them.
I think the key problem is this:
Hatem Ghazy wrote:All people answer me in a very advanced and complicated way.
You did not want to listen the answers in so complicated way. Why? If you did not understand something, you could ask your questions. I'm afraid that you don't want to bite a bullet. But you have to. There is no much of a shortcut.
Answering the follow-up question: here: