Hello Bingnan,
I am currently quite busy, so answers may take a while or won't cover the full detail.
To your question: "1. The trigger example seems to be receiving an external trigger signal, then triggering the camera. How can I make the output-triggering signal controllable?"
If you open the "Hierachical Box" you will find the following layout:
pasted-from-clipboard.png
In the "Select" Operator you can choose the Triggermode, in your case the one you are looking for is the setting "1", so that the signal from "Generator" gets used as a Trigger.
If you go deeper into the "Generator" you can see the following:
pasted-from-clipboard.png
The Operator "Period" can then adjust your signal. Please read the textboxes for further instructions on how to adjust the trigger signal.
To your secon question:
"2. With the "Overflow", is that means I can use a larger template? Or it is limited by the resources the "Overflow" controls transfer bits but no effect on this?"
The overflow operator CUTS off an image, when a memory element is not capable of holding saving the image.
As you can see in your screenshot from MicroDisplay you have a "1" on Overflow. This means that the memory is not capable of saving the required data with the chosen bandwidth.
The following screenshots describe areas where you have bootlenekcs in your design:
pasted-from-clipboard.png
This will result in your processing pipeline only be able to handle 125 MegaPixel/s , since the SYNC operator creates dummy pixels.
Also after this HBox you have a ParallelDN that will limit your bandwidth.
This is all the help I can give you at the moment, please try to remove those bottlenecks, with operator suchs as ParallelUP before the SYNC operator etc.
Best Regards
Kevin