Hi,
Today I have discovered that OSX is using two ways how to mark file as read-only. Either "locking" it (in Finder ctrl+left clik on file->Get Info and check Locked checkbox) or unix file system permissions. So far I thought they are the same and unlocking file also adds writable permission to it. But real life is always about something else J And here comes MonoDevelop into play. 1. Text editor: If file has only read permission, MD can detect it correctly and when saving document it asks to save it (somwhere else or replace original file). BUT if file is "locked", this doesnt work and all changes are lost without any word about the possible problem. 2. Building (e.g. for files, which are set as content and copy always): If file is "locked", file is copied without this flag and during next build it can be overwritten without problems. But if file has only read permission, file is copied with its original permissions and during next build MD complains about it and build fails. Especially point 2 is very annoying. Are there any plans to improve build process (or is there any workaround I can do myself?) to be able to delete/overwrite files without writable permission? Best regards, Ing. Michal Sartoris Resco.net<http://resco.net/>
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
