/*

 * Copyright (c) 2010, Tess Snider

 Permission is hereby granted, free of charge, to any person obtaining a copy

 of this software and associated documentation files (the "Software"), to deal

 in the Software without restriction, including without limitation the rights

 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell

 copies of the Software, and to permit persons to whom the Software is

 furnished to do so, subject to the following conditions:

 The above copyright notice and this permission notice shall be included in

 all copies or substantial portions of the Software.

 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR

 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE

 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER

 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,

 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN

 THE SOFTWARE.

*/

using System;

using System.IO;

using System.Collections.Generic;

using System.Text.RegularExpressions;

using Gtk;

using DesertPaintLab;

public partial class MainWindow : Gtk.Window

{

	bool unsavedData = false;

	bool shouldShutDown = false;

	List<string> profileList = new List<string>();

	PlayerProfile profile = null;

	Gdk.Window rootWindow = null;

	Gdk.Pixbuf screenBuffer = null;

    // views

    RecipeGeneratorView generatorView;

    SimulatorView simulatorView;

    CaptureView captureView;

	public bool ShouldShutDown

	{

		get

		{

			return shouldShutDown;

		}

	}

	public MainWindow () : base(Gtk.WindowType.Toplevel)

	{

        string appDataPath = FileUtils.AppDataPath;

		if (!System.IO.Directory.Exists(appDataPath))

		{

			System.IO.Directory.CreateDirectory(appDataPath);	

		}

		DirectoryInfo di = new DirectoryInfo(appDataPath);

		DirectoryInfo[] dirs = di.GetDirectories();

		foreach (DirectoryInfo dir in dirs)

		{

			if (dir.Name != "template")

			{

				profileList.Add(dir.Name);

			}

		}

        string colorsPath = FileUtils.FindApplicationResourceFile("colors.txt");

        if (colorsPath == null)

        {

            // failed to find colors.txt file

            MessageDialog md = new MessageDialog(this, 

                DialogFlags.DestroyWithParent,

                MessageType.Error, ButtonsType.Close, 

                "Failed to find colors.txt file. Please check your installation.");

# Desert Paint Lab

This is a tool for players to record their [Pigment Laboratory](http://www.atitd.org/wiki/tale6/Pigment_Laboratory)

ingredient reactions in [A Tale in the Desert](http://www.atitd.com/).

### Features

* Easily scans your screen for the paint bench reaction values, without any math, measuring, or manual number entry.

* Warns you when a reaction clipped below 0.

* Supports multiple character profiles.

* Can export to [PracticalPaint](http://www.atitd.org/wiki/tale7/File:PracticalPaint.Zip) data format.

* Includes simulator for experimenting with recipes without spending ingredients.

* Includes a recipe generator

## Tale 7

This application has been updated for Tale 7.  The current version is a **RELEASE CANDIDATE**.  It may be buggy.

If you find any problems with it, please [open an issue](https://bitbucket.org/Malkyne/desert-paint-lab/issues) or /chat Afrah or Snoerr

in the game.

## Directions

### Download Desert Paint Lab

You can always find the available downloads, on [the download page](https://bitbucket.org/Malkyne/desert-paint-lab/downloads).

This application should run under Mono on Mac, Linux, and Windows.  If you are on Windows,

and do not have Mono installed, you can install [GTK# for .NET](http://www.mono-project.com/download/#download-win),

without the need for installing Mono. On Mac or Linux, download and install the [Mono runtime](http://www.mono-project.com/download).

### Set Up a Profile

The first time you run Desert Paint Lab, it will prompt you to make a profile.  You may either create a new profile, or import an existing PracticalPaint reactions.txt file.

### Start Testing!

Add two ingredients to your paint bench.  Select those same ingredients in Desert Paint Lab.  Then, with the Pigment Lab dialog unobstructred, select the **Capture** button.  Once you are satisfied with the result, click the **Record** button.  The data will automatically be added to your profile.

### Clipped?  Huh?

Occasionally, you will see a warning dialog that informs you that a "Reaction clipped."  That means that one or more of the color components moved outside of the testable range.  This makes it impossible to calculate the reaction from these two ingredients.

You can solve this by doing a three-way test.

1. In your clipped reaction, let's call your **1st** ingredient **A** and your **2nd** ingredient **B**.

1. Select a **non-catalyst** ingredient **C** for which you have already tested **C + A** and **C + B**.  It is OK if there was a reaction in those earlier tests.  Desert Paint Lab can work out the math.

1. In Desert Paint Lab, select ingredients as follows:

    1. **C**

    2. **A**

    3. **B**

1. Add the ingredients in your Pigment Lab _in exactly that order_.

1. Capture.

1. Record.

For clipped reactions, your **C** ingredient should be one that corrects for the clipped color.  Here are some suggested **C** ingredients for clipping correction:

Clip Color  | Clip Direction | Correction | Suggested "C" Ingredient

------------|----------------|------------|---------------------------

Red         | Low            | +Red       | Carrot (224) or Red Sand (144)

Red         | High           | -Red       | Silver Powder (16) or Toad Skin (48)

Green       | Low            | +Green     | Earth Light (240) or Copper (192)

Green       | High           | -Green     | Red Sand (16) or Silver Powder (16)

Blue        | Low            | +Blue      | Earth Light (224) or Copper (192)

Blue        | High           | -Blue      | Red Sand (24) or Clay (32) or Carrot (32) or Silver Powder (32)

In many cases, it may be easiest to go back and do these three-way tests after you have finished all of your other testing.

### Catalysts

For catalyst to catalyst reaction tests, follow the three-way instructions, as above.