Here’s an example of how the configuration file might look, resulting in a graph similiar to the image.

<ApplicationSettings>
  <Parsers>
      <Parser>
          <Name>Ute GT2</Name>
          <BasePath>Z:\</BasePath>
          <FileName>Ute GT2.txt</FileName>
          <Start>2006-10-01 23:00</Start>
          <End>Infinite</End>
          <Color>255;0;0</Color>
      </Parser>
      <Parser>
          <Name>Kompressor</Name>
          <BasePath>Z:\</BasePath>
          <FileName>Kompressor.txt</FileName>
          <Start>2006-10-01 23:00</Start>
          <End>Infinite</End>
          <Color>255;0;0</Color>
      </Parser>
  </Parsers>
  <Graphs>
      <Graph>
          <Title>
          My graph test
          </Title>
          <Curves>
              <Curve>Ute GT2</Curve>
              <Curve>Kompressor</Curve>
          </Curves>
      </Graph>
  </Graphs>
</ApplicationSettings>

There are two main secions; Parsers and Graphs. The first one specifies what data shall be available, the second one then tells the application to create a curve-group, based on the specified data. It is possible can have an unlimited number of curves in one graph and an unlimited number of curve-groups. “Unlimited” means within reason, of course.
As can be seen the example, you can specify Infinite as the end date/time. This results in the application parsing all available data, including newly written data. I’m planning on adding several more of these keywords later on to make the graphs dynamic.