|
Thanks, anyway to do it with Enums you know??
All generalizations are wrong, including this one!
(\ /)
(O.o)
(><)
|
|
|
|
|
Yes, it should work with enums.
Again, though, it really depends a lot on what you're trying to do, so it's hard to recommend one approach over another... but here's a sample of some different techniques. Each have their strengths and weaknesses, depending on your situation.
Assuming an enum like:
enum MyEnum { Foo, Bar, Baz }
switch way:
bool method(MyEnum val)
{
switch (val)
{
case MyEnum.Foo:
Console.WriteLine("Some");
Console.WriteLine("big");
Console.WriteLine("case");
Console.WriteLine("statement");
Console.WriteLine("that");
Console.WriteLine("Foo");
Console.WriteLine("does");
return true;
case MyEnum.Bar:
throw new Exception("Bar!");
case MyEnum.Baz:
Console.Beep();
Console.WriteLine("Beep.");
return false;
default:
throw new ArgumentOutOfRangeException("val");
}
}
Refactor to methods way:
bool method(MyEnum val)
{
switch (val)
{
case MyEnum.Foo:
return FooMethod();
case MyEnum.Bar:
return BarMethod();
case MyEnum.Baz:
return BazMethod();
default:
throw new ArgumentOutOfRangeException("val");
}
}
bool FooMethod()
{
Console.WriteLine("Some");
Console.WriteLine("big");
Console.WriteLine("case");
Console.WriteLine("statement");
Console.WriteLine("that");
Console.WriteLine("Foo");
Console.WriteLine("does");
return true;
}
bool BarMethod()
{
throw new Exception("Bar!");
}
bool BazMethod()
{
Console.Beep();
Console.WriteLine("Beep.");
return false;
}
Dictionary way (.Invoke() is just for clarity):
delegate bool BoolFunc();
readonly Dictionary<MyEnum, BoolFunc> methods;
MyClassConstructor()
{
methods = new Dictionary<MyEnum, BoolFunc>();
methods.Add(MyEnum.Foo, FooMethod);
methods.Add(MyEnum.Bar, BarMethod);
methods.Add(MyEnum.Baz, BazMethod);
}
bool method(MyEnum val)
{
BoolFunc funcToCall;
if (!methods.TryGetValue(val, out funcToCall))
throw new ArgumentOutOfRangeException("val");
return funcToCall.Invoke();
}
bool FooMethod()
{
Console.WriteLine("Some");
Console.WriteLine("big");
Console.WriteLine("case");
Console.WriteLine("statement");
Console.WriteLine("that");
Console.WriteLine("Foo");
Console.WriteLine("does");
return true;
}
bool BarMethod()
{
throw new Exception("Bar!");
}
bool BazMethod()
{
Console.Beep();
Console.WriteLine("Beep.");
return false;
}
Subclass/override way (the enum actually goes away here):
bool method(MyNonEnumClass val)
{
return val.DoYourThing();
}
abstract class MyNonEnumClass
{
public abstract bool DoYourThing();
}
class FooClass : MyNonEnumClass
{
public override bool DoYourThing()
{
Console.WriteLine("Some");
Console.WriteLine("big");
Console.WriteLine("case");
Console.WriteLine("statement");
Console.WriteLine("that");
Console.WriteLine("Foo");
Console.WriteLine("does");
return true;
}
}
class BarClass : MyNonEnumClass
{
public override bool DoYourThing()
{
throw new Exception("Bar!");
}
}
class BazClass : MyNonEnumClass
{
public override bool DoYourThing()
{
Console.Beep();
Console.WriteLine("Beep.");
return false;
}
}
Hope this helps ease your switch/case pain! 
modified on Wednesday, February 11, 2009 5:21 PM
|
|
|
|
|
There's an even easier way. Take a look at my post below - it's as easy as this.
|
|
|
|
|
Thanks... I did write that way under Dictionary way already, though.
|
|
|
|
|
Wow, thanks akidan!
I think I will go with the last one.
All generalizations are wrong, including this one!
(\ /)
(O.o)
(><)
|
|
|
|
|
My pleasure! Happy I could help.
|
|
|
|
|
Why would you like to throw away the switch case?
This is a great way to code statemachines, for instance when you've got a status.
Or you use if else, but is like the same as switch case.
It really depends on what is it when you would like to get rid of the switch case. It depends on the situation. Show a situation and we'll give the solution.
|
|
|
|
|
You could always use a Dictionary with an enumeration and a Action to use. For instance, you could have an enumeration that closed a window like this:
public enum Operation
{
Close,
Save,
}
public void Action(Operation action)
{
if (_dictionary.ContainsKey(action))
{
_dictionary[action]();
}
}
public void Register(Operation operation, Action action)
{
_dictionary.Add(operation, action);
}Then, you can add your implementation like this:
Register(Operation.Close, delegate(){ this.Close(); });As you can see, calling this method removes the need for a switch altogether.
|
|
|
|
|
Pete O'Hanlon wrote: As you can see, calling this method removes the need for a switch altogether.
Not if you have legacy code as the OP does. He still has to switch the code to the new method. 
|
|
|
|
|
Augh... that's terrible. 
|
|
|
|
|
Hi Pete, I like your solution, it looks short and effecient, however, there's still one big problem.. I cant understand it 
See, I have this statement:
foreach (DataGridViewColumn grdC in grd.Columns)
{
switch (grdC.HeaderText)
{
case "ID":
grdC.HeaderText = "id";
break;
case "NAME":
grdC.HeaderText = "name";
break;
...
}
}<pre>
<div class="ForumSig"><hr><font face="Comic Sans MS" size="2" color="#3300aa">All generalizations are wrong, including this one!</font><font face="Arial" size="4">
(\ /)
(O.o)
(><)</font></hr></div>
|
|
|
|
|
your code is a WTF! All you're doing is lower-casing the header.
This would suffice
foreach (DataGridViewColumn grdC in grd.Columns)
{
grdC.HeaderText = grdC.HeaderText.ToLower();
}
|
|
|
|
|
|
The only place where there's a better solution, is where your switches indicate you should have a collection of classes, each representing a different case with the same overloaded method.
Christian Graus
Driven to the arms of OSX by Vista.
|
|
|
|
|
I have written a code that fills a form with data from a database into textboxes, the thing is some of the textbox comes up with empty information and they leave gaps within my document, is there any way to get rid of them?
Ferron
|
|
|
|
|
To clarify, are you filling a single textbox with more than one value from your database? Or do you have completely empty textboxes and want to format the empty spaces out of the form?
|
|
|
|
|
just one value for each text field. I have the address one under the other and there are making my page look bad. I want to format the empty spaces out
Ferron
|
|
|
|
|
I'm no expert, so there's only one solution I could think of that would work:
if (textbox1.TextLength < 1)
{
textbox2.Location.Y -= [int HeightOfTextbox];
}
I think the location 0,0 is in the upperleft corner, so this should be the right equation, but don't quote me on it. I haven't actually tested this.
modified on Wednesday, February 11, 2009 4:45 PM
|
|
|
|
|
Just for some extra info, you can do this slightly better:
Use pre tags for instance.
And do it like this:
if(String.IsNullOrEmpty(textbox1.Text))
{
textbox.Visible = false;
}
|
|
|
|
|
visible doesn't remove the space there. jst don't show
Ferron
|
|
|
|
|
He was commenting on the formatting of my post, but you should note how he set up his if-statement.
|
|
|
|
|
I was trying to move some the labels with the location.Y method but it doesn't seem to be working. Any help on how get rid of the empty labels as well?
Ferron
|
|
|
|
|
Use the visible property shown in Deresen's post to hide labels you don't want shown.
The labels should be able to move the same as your textboxes.
if (String.IsNullOrEmpty(textbox.Text))
{
textbox.Location.Y -= textbox.Height;
label.Location.Y -= textbox.Height;
}
modified on Wednesday, February 11, 2009 6:01 PM
|
|
|
|
|
i know know how to hide them that's not the problem. The problem is
my form is like this:
--------info--------
[ ]
--------info--------
i want to remove the space created by the empty textbox/label or move it to another location where it doesn't take up space
Ferron
|
|
|
|
|
I understand. In theory I figured it would work to move the controls below the empty textboxes up to fill in the gap, however I can't seem to get it working. Hopefully someone a little more knowledgeable will swing by. In the meantime I'll try and figure it out myself and let you know if I come up with anything. I'm still a newbie, myself.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
, OF COURSE this's not what I'm doing, I'm just giving an example, obviously a bad one