De : Joshua A. Andler <scislac@...400...> The patch simply checks to see if we can write the filetype, if not, throws an error message and then proceeds to open a Save As dialog.
Do we really need this error message? Opening the Save As dialog sounds good enough to me.
So, the question is, would people be okay with us shipping with the user-unfriendly error message in favor of saving people's data? Yes we could create a custom message for it, but I really don't want to break the string freeze again. After 0.47 is out, we could then make a 0.47.1 branch and have the proper error message that explains what went wrong (obviously adding to trunk as well).
I'd remove the error message in 0..47, and add a proper one (if it is really necessary) in 0.47.1.
Regards, -- Nicolas