Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

BYE v3.1.0 Downloaded Images have different File Permissions set than older v3.0.x


s3igell

Question

After a couple of Imaging Sessions with BYE v3.1.0rc4 (had to wait out the SW Monsoon), I've noticed the following difference between Files collected under v3.1.0 and those collected under previous v3.0.3 (and per checking my archives, also older v3.0.x and even v2.x):

 

Files downloaded under a v3.1.0 Imaging Session have File Permissions set for fewer Users than had occurred under previous BYE Versions.  

 

All Releases as well as the Current RC are setting the same File Permissions (essentially the complete set of "non-special" File Permissions:  Full, Read, Execute, Modify, Write).  But previous Releases were setting these permissions for Current User, System, Administrators (I assume these last two may be only if Current User is a member of these Groups - I always am on my own PCs) AND Everyone.  As of v3.1.0, this last User (Everyone) is not being assigned Rights to Images Downloaded via BYE Imaging Sessions.

 

Perhaps this is a Good Thing, as well as a purposeful Change.

 

However, I've learned (after learning about the Image Grading feature as part of also learning about the Offline PREVIEW Mode - great Google Presentation btw) that use of the Image Grading feature causes the addition of the Everyone User Permissions to each File tagged with a "Grade".  Removing the "Grade" doesn't revert the File Permissions change, although it does restore the initial Filename.

Link to comment
Share on other sites

  • Answers 3
  • Created
  • Last Reply

3 answers to this question

Recommended Posts

I have never really paid any attention to file permission.  I'm not sure why 3.0.3 versus 3.1 do not behave in the same manner because I'm not doing anything on purpose here.  

 

Thanks for watching the presentation.  I had a blast too :)

 

Regards,

Link to comment
Share on other sites

Any chance this could be a difference in whether you picked "install for all users" vs. "install for current user only"?

 

I don't recall that prompt coming up during the v3.1.0 installs, which I do allow to install into separate Directories as per Guylain's guidance (although I do change the destination to a subdirectory of Program Files; AND I update the Config files with data from previous version config files so that my configs match).  But, then, installing each of the Release Candidates is something that has become rather rote by now - and I don't pay much attention...

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use