Re: Stopping double clicking of a file
Re: Stopping double clicking of a file
- Subject: Re: Stopping double clicking of a file
- From: Andrew Farmer <email@hidden>
- Date: Wed, 4 Oct 2006 11:56:04 -0700
On 04 Oct 06, at 11:24, development2 wrote:
On Oct 4, 2006, at 12:19 PM, Hank Heijink wrote:
On Oct 4, 2006, at 2:07 PM, development2 wrote:
Hi,
I need to turn off the ability to allow users to double click on
a file and have them open it up. There are security reasons for
this, as we do not want to allow students to open up the file and
change grades or attendance. So we have to go through our login
procedure that allows the teachers or administrators to open the
file. But I can not see anyway to turn this off. I know in Carbon
this is done through Apple Events, and ma sure that it is done
the same way with Cocoa. I have looked on Apples site and
searched this list, but have not be able to find the answer to this.
Thanks in advance for any help.
Maybe I'm missing something, but this seems a strange way to go
about it. Why don't you just use file permissions to deny certain
users access to a file? I would imagine that permissions for
users, groups, and others offer enough flexibility to solve this
without trying to modify the user interface at such a basic level.
Sorry can't do that. These files are all stored on Windows servers,
and they need to be able to create new files, delete files, etc.
I have to disallow the file form double clicking. It can be caught,
at least in carbon I have done that in the past.
That's not possible, as the event created by double-clicking the file
is handled within the Finder, which you shouldn't be trying to patch.
More importantly, there are many other ways to open the file,
including but not limited to:
* Pressing Cmd-O in the Finder
* Pressing Cmd-down arrow in the Finder
* Right-clicking on the file in the Finder and selecting Open from
the menu
* Dragging the file onto an application icon (in the Finder or on the
Dock)
* Opening the application which reads the file and opening it from
within there
* Running /usr/bin/open from a terminal
* Copying the file to the desktop, renaming it to a .txt, and opening
that
* Copying the file to a removable drive and examining it on another
machine
Store the file on a password-protected share on the Windows server.
Don't try to implement file protections on the client - THAT WILL NOT
WORK.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden