12.6 Signature File Implementation
Now we implement menu item, Signature/N Signature (a1.txt). Double click this menu item and enter:
private void menuItem6_Click(object sender, System.EventArgs e)
{
this.mainMenuToAPI.signature_Training_Segment_Signature
(dataDir + "a1.txt");
}
Again, mainMenuToAPI is an object, which will implement all functions. As we discussed in the last chapter, the main form simply links menu items to functions in the mainMenuToAPI object. The implementation is:
public void signature_Training_Segment_Signature (string outputFile)
{
f.mainMenuToAPI.script.signatureFilter.getSegmentLibrary ( f.gui.imageAbsoultePath,
f.gui.imageID ,
f.gui.imageX,
f.gui.imageY,
f.gui.imageW,
f.gui.imageH ,
outputFile );
}
In this statement, the script object contains all of the objects required for the ImageFinder project. In particular, �script.signatureFilter� is the image signature filter object. The parameters, �f.gui.imageAbsoultePath�, is a string list that has the absolute paths of all source images to be matched. After the completion of signature computation, the results will be stored in a file specified by the last parameter, outputFile.
The only difference between the following menu items is the output file; therefore, all of them will be implemented in a similar fashion:
Signature/Training Signature (t1.txt)
Signature/N Signature (a1.txt)
Signature/M2 Signature (a2.txt)
Signature/M3 Signature (a3.txt)
Signature/M4 Signature (a12.txt)
Copyright (c) 2006 - 2007 Attrasoft. All rights reserved.