When I modify panels using CFGedit if there are a lot of XML's which CFGedit doesn't understand when I resize or move any additional guage it tends to distort and scramble gauges already in place.  Has anyone else had this problem with CFGedit and if so is there a way to keep from disturbing gauges you aren't manipulating while adding and re-sizing other gauges? The only work around I have found is using cfgedit to map out co-ordinates and then open the panel.cfg and make my changes with syntax.  Has anyone experienced this problem and found a work around with-in cfgedit?

Yes, that's exactly what is happening.  A few gauges end up abnormally big everytime when I resize or reposition any added gauge or even any gauge that is already in place.  And, while with-in cfgedit, it doesn't show that any dimmensions have changed with these gauges.  I think I will try what you suggested and make copy out the original or just open up the back-up and go down it line by line to see what has changed and look to see that the fourth set of numbers is still there in all of them.  I know that two sets are x,y postion on the panel and two sets are x,y size of the gauge.  I think maybe the printed out original would be good in case the abnormalities happen during cfgedit's back-up as well.

I really want to get the commercial version of CFGEdit which can deal with XML gauges.  I wish I could learn C++ but I don't have time for that unfortunatly but if I new it though and I created anything good I wouldn't be tempted by the payware bug.  I would love to create an FMC that could be set-up to use in any aircraft.  There was one included in pro-flight 2000 so I know it is technically poossible that an FMC doesn't have to be tied up in a specific plane's systems to work.  Even if it would only handle basic waypoint nav and basic vnav/waypoint duties it would be better than now which is nothing.

Yes, I could do my work on a copy as you said.  I haven't decided though which is more typing here.  Using CFGedit to map co-ordinates and then typing in the gauge or drag and drop and then checking the new cfg line by line with the backed up and correcting any abnormalities.  I have however learned to save after each and every little change.  Even if it's the background bitmap I changed.  It saves me having to start from scratch again with the original.  I always have the original to fall back on because the zip stays in my documents, "downloaded planes" folder and every other week I move everything to a cdrw to keep space free. I found out how quickly you can chew up space with downloaded freeware.  To date I have something like 12 gig worth of it and a stack of disks.  One for panels, one for scenery, one for aircraft and aircraft packages, one for misc. etc. and I keep a label in each of them as to the contents to make selecting easier if I need the original zips.  Also, my custom panels that I may not be able to re-produce easily I keep backed up.  I have an excellent KLN-90 GPS which I am beta testing for a designer.  He intends to market it on simarket or somewhere.  It even has the map page, both split and full screen.  It works great in concert with Ike Slack's KLN 90 GPS reaout/simicon gauge because instead of popping up the default when you click the go-to switch it opens a near full functional pop-up KLN 90. Anyway, I have all of those panels backed up also, many use the MX-20 MFD for extra.  I hope this gentleman soon releases the final for sale because I have some excellent panels configed this way which I would upload, minus the KLN of course.