Custom Panel control -> Not sure if I'm following the rigth path...

Question

4.00/5 (1 vote)

See more:

Hi guys,

I am a relative newbie to OO programming so please be patient :D
For the sake of exercise I've been writing a small desktop app (room booking system, eg. in hotel). In order to visualise all of the rooms available I've created a custom panel control (color coded - red for busy room, green for available and so on). Within my PaintedPanel class I have a method that creates a grid (like a chess board)
of the panels... Using a simple 'for' loop it creates specified number of panels and adds them to parent control. Question is -> is it ok to create an object (or collection of objects) of the particular class within the class itself ? (eg. my PaintedPanel class has a method 'createPanelGrid' in which I create an instances of the PaintedPanel objects).
I decided to do it this way in order to have only one 'onclick' event handler that serves all of the PaintedPanel instances, rather than creating a grid of Panels within my main form logic and having to code multiple event handlers for each and every PaintedPanels.
Does it make sense ? Not sure if I got the idea of custom controls rigth...
Any suggestions will be greatly appreciated.

Cheers,

Mike

Posted 9-Jun-11 0:48am

MTomorowicz

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2011-06-09T01:26:00

You can do that, but your reasoning is slightly flawed.

"I decided to do it this way in order to have only one 'onclick' event handler that serves all of the PaintedPanel instances, rather than creating a grid of Panels within my main form logic and having to code multiple event handlers for each and every PaintedPanels."

The same event handler can handle as many instances as you need: the sender parameter tells you which one it relates to:

void myEventHandler(object sender, EventArgs e)
   {
   MyCustomControl mcc = sender as MyCustomeControl;
   if (mcc != null)
      {
      Console.WriteLine(mcc.APropertyOfTheControl);
      }
   }

Normally, you would keep it so that the Room class does not know or need to know about even the existence of other rooms: instead, You would have a Floor class which knew about all the rooms on a floor, and a Hotel class which knew about all the floors.