Lesson 17 Try It

John S · #1 (**permalink**) June 12th, 2013, 03:05 PM

Ok, new day, new problem.

I worked through the Lesson 17 Try It, and set the Preferred Contact to 0, like this:

Code:

preferredMethodComboBox.SelectedIndex = 0;

When I ran it, I kept getting an error message that it was out of range.

I replaced the "0" with -1, 1 and 2, and kept getting the error.

Finally, I guessed it was something with the Properties of the preferredMethodComboBox. Comparing mine to the one in your book's downloadable example, I found that my combobox did not have any entries in its "Items".

I thought that was what the code was supposed to do ... initialize the combobox with those Items, and assign indexes to them.

After typing in "None, Email, Phone and Snailmail" into Edit Items for the combobox, the error messages went away and the solution worked.

So what is the purpose of this code? :

Code:

private enum ContactMethod
        {
            None = -1,
            Email = 0,
            Phone = 1,
            SnailMail = 2,
        }

I thought it was supposed to set the indexes for those selections, but None is still 0, Email is 1, Phone is 2, SnailMail is 3.

That is,

preferredMethodComboBox.SelectedIndex = 0;

brings up "None" when I thought it would be "Email"

Your sample code works the same way, 0 is None, not Email.

Rod Stephens · #2 (**permalink**) June 13th, 2013, 12:08 PM

I don't know why it didn't work for you initially and then started working.

You're right that there's something wrong with the enum. The value -1 in a ComboBox means "no selection" so I think the idea was to have "none" not be an actual selection.

To make the values match the indexes of the choices in the ComboBox it should probably be:

Code:

        private enum ContactMethod
        {
            None = 0,
            Email = 1,
            Phone = 2,
            SnailMail = 3,
        }

John S · #3 (**permalink**) June 13th, 2013, 03:47 PM

Yeah that would make more sense.

I'm curious about entering any indexes at all in the enum. When I had the wrong ones in there, the project seemed to ignore them anyway.

The solution did not work originally, until I manually entered the enum Items into the Items editor of the combo box Properties.

I guess I was expecting the code for the enum to enter the values into the combo box, but it didn't work that way.

Rod Stephens · #4 (**permalink**) June 14th, 2013, 08:55 AM

The idea of the enums is to let your code refer to them by names that make sense. I could imagine that it might store values that don't match what's in the ComboBox. Internally a program treats an enum as an integer anyway and doesn't really care what it's textual value is.

John S · #5 (**permalink**) June 14th, 2013, 03:05 PM

I'm just a beginner at this, but it seems like a long way around for nothing.

Perhaps the purpose of the Try It is just to demonstrate how enums and structs work??

In the form, the user selects the preferred way to contact the person being added (None, Email, etc.) which the combobox stores as an integer.

But the code includes an enumerator that matches the integer from the combobox back to a string, so that the structure can store the string?

You not only have to type the choices into the combobox Items, but then also have to type them into the enum, and make sure to do so in the same order!

Why doesn't the structure just store the integer? The only purpose of the result generated by the combobox is to show the person's preferred contact when one uses the "Find"

Looks like a lot of work just to display a selection in a combobox

Rod Stephens · #6 (**permalink**) June 14th, 2013, 06:43 PM

Yes and no. A lot of the Try Its are intended to give you practice with one or two specific concepts. Some also build on others so you need to learn one technique before moving on.

But even in professional programming, following certain standards makes your code much less buggy and bugs cost a huge amount to fix. So you learn certain patterns of design and development to make the code more readable and maintainable.

One of those "best practice" techniques is using enumerated types instead of "magic numbers." That makes your code more readable and easier to understand.

John S · #7 (**permalink**) June 14th, 2013, 07:27 PM

Well that sounds like good advice.

I'm not sure, however, what you're referring to as magic numbers.

Can you give an example or two?

thanks

Rod Stephens · #8 (**permalink**) June 14th, 2013, 09:27 PM

Like when a program lets 1 mean small, 2 mean medium, and 3 mean large. Then the code is full of 1s, 2s, and 3s so you can't keep track of what the numbers mean.

It's much better if the code uses an enum so it says "Small," "Medium," and "Large."