Hi Mike,
You wrote "However, using the image posted above, there are 8 possible crosswind components to calculate." You have a point that I admit I didn't fully think of when it comes to the ATIS or AWAS broadcast report. Yet even there, it would only need to calculate and report it for the upwind/approach direction for each runway (reasonable assumption being no-one's going to be landing with a tailwind) and so in a two runway airport only two numbers: For example "Runway 29 crosswind component 9 knots from the right. Runway 36 crosswind component is 23 knots from the right."
And my original request/wish was/is to have iFly do the crosswind calculation on final approach. Since it knows which runway you're lining up on it only has to calculate and give you the crosswind component for one runway.
See how much better things would be if I were in charge?
Alex