Here's the problem.
I have a HTPC that outputs DSub RGB thru a ATI 9600XT card. I use a active RGB splitter (
http://www.provantage.com/tripp-lite-b1 ... RPA1C6.htm).......one feed going to a 1440x960 flat panel monitor on top of the HTPC...call it debug monitor. The other feed from the splitter goes into
a RGB to Component transcoder (
http://www.digitalconnection.com/produc ... o/9a60.asp). The output of this transcoder feeds in a component 8x4 matrix switch that feeds my Home Theater PJ and the other LCD TVs in the house. Since my ATI 9600XT card and HTPC doesn't have quite enough punch for 1080 (and all my native display rezs are 1368x768) I drive the TV/PJs at 720P...1280x720 60Hz. Now, as I said I use the 1440x960 monitor as kinda a debug/programming monitor. The issue with XL is that it tries to be too smart on the skin layout with the rez. For example, if a skin is developed in some larger rez (eg. 1440x960) and you go into in 1280x720 it tries to move things around/shrink/etc. The problem is this has many unwanted results....nothing seems to line up. So, for my skins (or any that I tweek).....I have to make sure I only every launch XL to config it in the 1280x720 rez....if not items are mucked up with no recourse to fix. For me, it would be much better that XL does not try to auto-correct for rez changes...it should just keep the image static. Thus if you develop in 1280x720 a skin but display at 1440x960 you'll have more call it border space (say underscan effect). If you devloped on 1440x960 and run XL in lower rez like 1280x720 or 1024x768 you get a cropping (say overscan effect). I know the idea is for the user not to have to worry about this but it is much better to see the real effect of the rez on the skin and have to perhaps save to another version of skin and make your edits. In summary, just MHO, I'd rather have the same skin for different rezs saved than one skin where XL tries to auto-adapt.