Hi Frank,
Have you checked the CPU load on your PC while the displays are running? - use the CPU meter in the Windows task manager, as the FlowStone CPU readout won't show anything for CPU used by the graphics.
I have a feeling that you'll see some very high readings, and possibly max'ing out a CPU core when you have both displays running.
FlowStone uses GDI graphics routines for all the screen drawing, which are always processed by your main CPU without any hardware acceleration from the graphics card. This can really eat CPU if you are animating a large area of the screen, especially when you have so many overlapping layers.
Here's a couple of suggestions for getting the CPU load down a bit...
- All of your bitmaps seem to cover the complete area of the display - so when there is a re-draw, there is a lot of processing being done to work out which pixels will be visible through all of the transparent parts. For many of the smaller readouts on the display, it would be better to use smaller bitmaps that only cover their own little areas, and then position them correctly once you have them inside FS.
This will make laying out the panel a bit more tricky, but will lead to much less layers overlapping, and also only a much smaller part of the screen will get redrawn when a control changes.
- I don't know how quickly your flight data is coming in, but if it is very fast, it could be that the screen is being redrawn too quickly. More than about 25-30 screen updates per second will consume a lot of CPU, and many of those frames won't be picked up by your monitor or by your eyes.
You can find in
THIS POST, a little gizmo for controlling the frame rate of animations - it ensures that you always can see the current data, but without showing more frames than are needed by your display.