Handling of read-only storage: feeback wanted

2013-05-06 Thread Amaury Pouly
Hi , I'm looking for some feedback on an issue which might not be one: read-only storage. It appears that since virtually all DAP use micro-sd card we never ran into this problem but I am porting Rockbox to the Creative ZEN and ZEN X-Fi which feature a real SD card port and can sense the

Re: Handling of read-only storage: feeback wanted

2013-05-06 Thread Marcin Bukat
Failing to open file(s) for writes seems to be elegant solution but this will probably trigger error messages as well. Moreover I think it should trigger error message to give user feedback that card is write protected (by accident for example). 2013/5/6 Amaury Pouly amaury.po...@gmail.com Hi

Re: Handling of read-only storage: feeback wanted

2013-05-06 Thread Björn Stenberg
Amaury Pouly wrote: A simple solution would be to prevent opening opening a file for writing for example. Gracefully handling read-only media requires at least a thorough review of the relevant file-writing code paths to ensure failure to write shows a (single) sensible message to the user

Re: Handling of read-only storage: feeback wanted

2013-05-06 Thread Lorenzo Miori
Definitely, user must know exactly what's going on BUT errors must not be verbose otherwise usability decreases. I suggest that when introducing such a new behaviour we should carefully think about other possible behaviours (i.e. SD being removed for some reason) and related implications,

Re: Handling of read-only storage: feeback wanted

2013-05-06 Thread Steph MM @ yahoo
My Cowon D2 use real SD. I haven't been using them for a long time now but cannot remember what happens if I move the tab. I would be ready for end-user test, if no compiling or such things are not requested (wouldn't know how to) be to prevent opening opening a file for writing for example.