Protect (read only) Button in Preview mode

[GoogleCodeExporter]

Ideally would like to assign custom functions to buttons... but primarily:

I would really like to have a "protect" (set file to read-only) button (the 
print button would make a good candidate) on the back of the camera like the 
Nikons and 1D series? 

It looks like this is in ML (http://wiki.magiclantern.fm/userguide) "LV on 
60D/600D: you can configure it to protect images with a single button press" 
but I don't have one of these "newer" cameras. I would like to have it in my 
workflow, but also to try the 'selective transfer mode' of the eye-fi cards 
(http://support.eye.fi/software/account/transfer-mode/) with a CF adapter.

Original issue reported on code.google.com by bwieseon...@gmail.com on 23 Nov 2012 at 8:24

[GoogleCodeExporter]

On a first inspection, I could not find anything among the known calls related 
to file protection; this will not be easy.

Original comment by eduardo....@gmail.com on 23 Nov 2012 at 9:49

[GoogleCodeExporter]

Bummer... I was hoping a "chmod 555" option would be easy. =( Thank you for 
checking!

Now that I finally got 400Dplus installed, I just realized in the documentation 
that "DP" is the "Direct Print" button and not "DISP". So setting this to 
"protect" might not be the best choice, all other buttons on the right side 
look good for programming through - except Left and Right (pref Av button).

Original comment by bwieseon...@gmail.com on 23 Nov 2012 at 11:01

[GoogleCodeExporter]

So is this a new call in the 60D/600D cameras? I wonder how ML implements it - 
is there developer docs for it or I wonder if they had to create some kind of 
hack?

Original comment by bwieseon...@gmail.com on 23 Nov 2012 at 11:07

[GoogleCodeExporter]

chmod would not help since the filesystem is FAT.
There should be a way to protect the files, since the OFW can do this.
I will investigate this further.

Original comment by fired...@gmail.com on 23 Nov 2012 at 11:15

• Changed state: Accepted

[GoogleCodeExporter]

status report:

In ML they simulate few button presses to protect the image, this is core 
functionality in the ML cameras. We cannot use this.
Our ways to go are to call internal routines to protect the image.

So far the candidates are:
FIO_SetFileAttributes() - this one should take a string as argument (or some 
more)
FC_SetProtect() - this one should take 2 arguments, they are related to the 
internal catalog structure. My guess is that it takes the number of the folder 
and the number of the image.

In either way, we need to find a way to identify the image first, either the 
filename or the catalog IDs.

note: it may turn out that the FIO_ option is not enough, since the catalog may 
not know that the file is protected (though it will discover that, once the 
user starts deleting files)

Original comment by fired...@gmail.com on 24 Nov 2012 at 1:33

[GoogleCodeExporter]

Thank you. Odd that there is no FIO_GetFileAttributes().  When in Playback mode 
and looking at an image, the image number is displayed in the top right. I 
don't know if there is any way to intercept that or see what files is currently 
being displayed?

Comment: Related to the reason for the feature request - to use Eye-Fi card 
Selective Transfer mode to replicate real-time photo distribution services like 
this: http://www.iso1200.com/2012/11/shootitlive-secret-weapon-behind-times.html

Original comment by bwieseon...@gmail.com on 24 Nov 2012 at 2:05

[GoogleCodeExporter]

There is FIO_GetFileAttributes() in the OFW, but I don't see how this helps us.
About the playback, I will try to find a reliable way to identify the image 
(shouldn't be hard).

Original comment by fired...@gmail.com on 24 Nov 2012 at 2:09

[GoogleCodeExporter]

WRT "catalog may not know that the file is protected"... GetFileAttributes() - 
to hopefully tell us if the file is already write protected, and display a lock 
or visual feedback on the screen to the user - so that pushing whatever the 
"Protect" button is "toggles" the write protection on the displayed file.

Original comment by bwieseon...@gmail.com on 24 Nov 2012 at 2:33

[GoogleCodeExporter]

Caveat: Should toggle "protect" for all files with the same XXXX numbering 
(JPG, CR2), and also since the file naming prefix may change: Issue 84.

Original comment by bwieseon...@gmail.com on 24 Nov 2012 at 2:35

[GoogleCodeExporter]

Original comment by fired...@gmail.com on 7 Feb 2013 at 4:35

• Added labels: Milestone-M2

[GoogleCodeExporter]

this will take some effort in reversing the original code.

Original comment by fired...@gmail.com on 17 Feb 2013 at 4:10

• Added labels: Milestone-M3
• Removed labels: Milestone-M2

[GoogleCodeExporter]

We are moving to GitHub, please follow this issue at 
https://github.com/400plus/400plus/issues/299

Original comment by eduardo....@gmail.com on 16 Mar 2015 at 1:13

• Changed state: Migrated