C#

I change over to using StreamWriter. I have used it before, I wasn't thinking.

using System.IO;
using (StreamWriter list = new StreamWriter("C:\\Users\\Gene\\Desktop\\Test.scr", true)) {

	list.WriteLine("Line " + cabinetx + "," + topy + " @" + cabinetWidth + ",0\n");
}

I changed from  Console.WriteLine( ) to  list.WriteLine( )
Works great. Beautiful thing. It doesn't print to screen but it does write to a text file.

I use progeCad. (similar to AutoCad)
I saw this online. Running script in Cad program
It draws a 1" square box. And it did it all in 1 line of code.

Line 0,0 @1,0 @0,1 @-1,0 close

Starts a line command. Space is like hitting the spacebar or Enter key.
Where do you want to start from? x,y coordinate 0,0. Space
What's the next point? @1,0. Space. and so forth

After that, I drew a cabinet, used it as a model to gather locations and sizes of Left end, right end, top, deck and measured for precise locations and sizes.
From those measurements I typed out these commands

Rectangle 0,4 @0.75,30.5
Rectangle 30,4 @-0.75,30.5
Rectangle 0.75,34.5 @28.5,-0.75
Rectangle 0.75,4 @28.5,0.75

Saved as a script file (.scr) and ran in progeCad as script file

It drew out in a split second what I had drawn previously for a model
After that, it was like candy. What other parts can I draw?

The program is two parts
First part gathers information- width, height, depth. Top drawer and 1 door, with 2 adjustable shelves. This is done thru user input, to change location, sizes and choice of parts.
Numerous windows display, allowing changes. Window is cleared and the next window is diplayed...

Second part is where all the commands code is generated. (similar to lines of code above)
I copy the command codes, paste in a text file, save as script file and run in progecad
Each line, represents one full command in progeCad. The first line runs and jumps to the next line until the end. It just drew several views of the cabinet.

Using StreamWriter, no more copy and pasting.
Thanks again.

using (StreamWriter list = new StreamWriter("C:\\Users\\Gene\\Desktop\\Test.scr", true)) {
    string content = "Line " + cabinetx + "," + topy + " @" + cabinetWidth + ",0\n";
    list.WriteLine(content);
    Console.Write(content);
}

Quote:

I want that enum to be the actual name of a var.

public override void Calculate(FruitType fruitType)

Dave Kreskowiak wrote:

... values in an enum should not be thought of as variable names at all ... It may work in interpreted languages, but it doesn't work in compiled languages. The variable names no longer exist(*).

Dave Kreskowiak wrote:

context of "beginner"

using System;
using System.Collections.Generic;

namespace YourNameSpace
{
    public enum Fruit
    {
        NoFruit, Apple, Orange
    }

    public class FruitCalc
    {
        private Dictionary<Fruit, Func<int, int, Fruit>> CalcFruitDict
            = new Dictionary<Fruit, Func<int, int, Fruit>>
            {
                // lambda notation used here
                {Fruit.Apple, (int napples, int noranges) => napples > noranges ? Fruit.Apple : Fruit.NoFruit },
                {Fruit.Orange, (int napples, int noranges) => napples < noranges ? Fruit.Orange : Fruit.NoFruit },
            };

        public Fruit Calculate(Fruit fruit, int napples, int noranges)
        {
            if (fruit == Fruit.NoFruit)
            {
                throw new InvalidOperationException("Sorry, no fruit means no fruit");
            }

            // check integer parameters for valid range ?

            return CalcFruitDict[fruit](napples, noranges);
        }
    }
}

FruitCalc fcalc = new FruitCalc();

Fruit f1 = fcalc.Calculate(Fruit.Apple, 12, 4);
Fruit f2 = fcalc.Calculate(Fruit.Orange, 14, 24);

Fruit f3 = fcalc.Calculate(Fruit.Apple, 2, 4);
Fruit f4 = fcalc.Calculate(Fruit.Orange, 14, 2);

// force an error
Fruit f5 = fcalc.Calculate(Fruit.NoFruit, 12, 4);

public Fruit Calculate2(Fruit fruit, int napples, int noranges)
{
    switch (fruit)
    {
        case Fruit.Apple:
            return napples > noranges ? Fruit.Apple : Fruit.NoFruit;
        case Fruit.Orange:
            return napples < noranges ? Fruit.Orange : Fruit.NoFruit;
        default:
            throw new InvalidOperationException("Sorry, no fruit means no fruit");
    }
}

public void DropDownSelectChanged(object sender, EventArgs args)
{
  // assuming the sender is the drop down
  var ddl = sender as DropDown; // whatever the actual control is in your GUI
  Calculate(ddl.SelectedItem);
}

// These get set in your constructor.
public Action MoreApplesAction {get; set;}
public Action FewerApplesAction {get; set;}

public void Caclulate(Fruit selectedFruit)
{
  // Of course, these should be properties somewhere
  var Apple = 5
  var Orange = 1

  // It's OK to create guards like this to
  // enhance readability, but don't be surprised
  // when someone objects because of the memory
  // allocation.
  var MoreApples = Apple > Orange;
  var FewerApples = Apple < Orange;

  switch(selectedFruit)
  {
    case Apple:
      if(MoreApplies) MoreApplesAction?.Invoke();
      break;

    case Orange:
      if(FewerApples) FewerApplesAction?.Invoke();
      break;
  }
}