I was thinking along those lines as well. It seems that the developer permission is used for quite a bit on the back-end. I know it is also used to disengage a lock from the overview screen--also something that would be nice to seperate out.
Geoff--is granularizing these permissions something that daemon has looked at in the past? Coach B wrote: >Hi Scott, > >Thanx for your suggestions. > >I thought about extending but it seems like overkill. > >Its seems though the most sensible option is that it become a permission >like approve, delete, etc which u can assign to any group u want rather than >having it tied to only developer permission. > >so perhaps something like this: > >add new permission "ShowObjectID" > >Then modify renderobjectoveriew.cfm code: > >iShowObjectID = >request.dmSec.oAuthorisation.checkInheritedPermission(objectid="#parentid#",permissionName="ShowObjectID"); > ><cfif iDeveloperPermission eq 1 Or iShowObjectID Eq 1> > >my 2 cents worth... > > > >-- >View this message in context: >http://www.nabble.com/Displaying-the-ObjectID-in-the-overview-tab-t1288856c621.html#a3449472 >Sent from the FarCry - Dev forum at Nabble.com. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/farcry-dev -~----------~----~----~----~------~----~------~--~---
