This is in regards to case #073670
The reported issue was that when reordering screens in the MUI, some division logic was applied to make the Order value smaller when moving up, and the Order value bigger when moving down. This occasionally causes the numbers for multiple MUIScreen records to be the same, thus you can move neither screen.
This would be easily resolved by making Order an int rather than a real. We already have logic for an Order field in one of our own tables that works perfectly with Order being an int.
A newer noticed issue is that when Order is not a whole number, during a publish, some odd interpretation error happens with the project XML on the first existing decimal point in regards to "Order" thus causing the publish to crash.
We have had to manually edit the XML to not have decimals several times in several of our projects in order to allow publishing.