Three bugs in MSP USB Descriptor tool

I downloaded the latest descriptor tool.  The installer is MSPUSBDescriptorTool-5_00_10_19-windows-installer and the help...about says v5.00.00.14.

Bug 1:  HID interfaces are reversed in order each time the tool is opened.  To reproduce, open the tool and add three HID interfaces.  Change the Interface String field on each one to be unique.  Save the configuration, close the tool, then reopen the tool.  The interfaces will be in reversed order.

Bug 2: Report Length field of Custom HID interfaces does not appear to be saved in XML file.

Bug 3: Custom HID interfaces result in corrupt XML save files, and the tool will crash when opening the file.  To reproduce, add an HID interface, change it from Datapipe to Custom, hit "ok" in the descriptor box, and save the file.  The save file looks like this:

                            <hidInterface intString="HID Interface 0">
                                <hidParams>
                                    <pollIntv>1</pollIntv>
                                    <hidRepType>3<![CDATA[0x06, 0x00, 0xff,                  // Usage Page (Vendor Defined)
0x09, 0x01,                        // Usage Page (Vendor Defined)
0xa1, 0x01,                        // COLLECTION (Application)
0x85, 0x3f,                        // Report ID (Vendor Defined)
0x95, MAX_PACKET_SIZE-1,           // Report Count
0x75, 0x08,                        // Report Size
0x25, 0x01,                        // Usage Maximum
0x15, 0x01,                        // Usage Minimum
0x09, 0x01,                        // Vendor Usage
0x81, 0x02,                        // Input (Data,Var,Abs)
0x85, 0x3f,                        // Report ID (Vendor Defined)
0x95, MAX_PACKET_SIZE-1,           // Report Count
0x75, 0x08,                        // Report Size
0x25, 0x01,                        // Usage Maximum
0x15, 0x01,                        // Usage Minimum
0x09, 0x01,                        // Vendor Usage
0x91 ,0x02,                        // Output (Data,Var,Abs)
0xc0                                // end Application Collection]]></hidRepType>
                                    <hidRepString/>
                                </hidParams>
                            </hidInterface>

If you edit the file to look like this, the tool can read in the XML:

                            <hidInterface intString="HID Interface">
                                <hidParams>
                                    <pollIntv>1</pollIntv>
                                    <hidRepType>3</hidRepType>
                                    <hidRepString><![CDATA[0x06, 0x00, 0xff,                  // Usage Page (Vendor Defined)
0x09, 0x01,                        // Usage Page (Vendor Defined)
0xa1, 0x01,                        // COLLECTION (Application)
0x85, 0x3f,                        // Report ID (Vendor Defined)
0x95, MAX_PACKET_SIZE-1,           // Report Count
0x75, 0x08,                        // Report Size
0x25, 0x01,                        // Usage Maximum
0x15, 0x01,                        // Usage Minimum
0x09, 0x01,                        // Vendor Usage
0x81, 0x02,                        // Input (Data,Var,Abs)
0x85, 0x3f,                        // Report ID (Vendor Defined)
0x95, MAX_PACKET_SIZE-1,           // Report Count
0x75, 0x08,                        // Report Size
0x25, 0x01,                        // Usage Maximum
0x15, 0x01,                        // Usage Minimum
0x09, 0x01,                        // Vendor Usage
0x91 ,0x02,                        // Output (Data,Var,Abs)
0xc0                                // end Application Collection]]>
                                    </hidRepString>
                                </hidParams>
                            </hidInterface>