SteveMyres Posted January 12, 2017 Share Posted January 12, 2017 If I open file preferences, set preferred editing colors, hit OK to exit, the next time I open DF, the colors and fonts are unchanged, and if I open Preferences again, the settings are unchanged from the original. Link to comment Share on other sites More sharing options...
AzeoTech Posted January 12, 2017 Share Posted January 12, 2017 Newer versions of Windows have tightened security over the registry where these settings are stored. I believe we adjust the security settings during install in 16.3 (not earlier releases as this is a new thing), so 16.3 should work. If not, then we may have missed a spot. We only open up the parts of the registry DAQFactory uses. Link to comment Share on other sites More sharing options...
SteveMyres Posted January 12, 2017 Author Share Posted January 12, 2017 It's Win7 Pro, so not that new. Is that new enough for what you're describing? This is on 5.91. So if the issue you're talking about is the problem, is there any reason not to update to 16.3? Link to comment Share on other sites More sharing options...
AzeoTech Posted January 12, 2017 Share Posted January 12, 2017 Yes, I believe it started with Win 7 and only got worse with Win 10. There is no reason not to upgrade to 16.3 from 5.91. You may see out of order screen controls in any component groups, but otherwise should be good. Customers running 5.87 however I typically recommend sticking with 5.87 unless they want the new features. Its a "if it ain't broke, don't fix it" thought. 5.87 -> 5.9 was a compiler change so requires a little more application testing for the customer under the new release than a normal upgrade. Link to comment Share on other sites More sharing options...
SteveMyres Posted January 12, 2017 Author Share Posted January 12, 2017 OK, I'll update to 16.3 then. Thanks! Link to comment Share on other sites More sharing options...
SteveMyres Posted January 12, 2017 Author Share Posted January 12, 2017 OK, update to 16.3. Seems like it's Guru Mode selection that doesn't stick. Then, if I select a dark background in the normal settings. manually without trying to use Guru Mode, it only changes the background NOT behind sequence code. Then the sequence code is still in the default color on white background. Font changes don't save either. Link to comment Share on other sites More sharing options...
SteveMyres Posted January 12, 2017 Author Share Posted January 12, 2017 OK part of that is the Admin account issue that affects use of Registry variables. I'm developing from the same User account from which the app runs. If I develop in an admin account, the font and color settings do save (though the background issue I mentioned is still in effect). Link to comment Share on other sites More sharing options...
SteveMyres Posted March 31, 2018 Author Share Posted March 31, 2018 Still on Win7 SP1, DF 16.3, and it's acting like I described before for user mode, even logged in as an admin. Guru Mode doesn't stick, and changing the default background without enabling user mode only changes the background NOT behind the sequence portion of each line. From the end of the text to the right side of the window, the change is effective. Link to comment Share on other sites More sharing options...
AzeoTech Posted April 12, 2018 Share Posted April 12, 2018 You have to actually run DAQFactory as an admin, as the settings are saved in the registry, and depending on your Windows settings, you can't edit the registry unless the application is run as an admin, even if you are logged in as an admin. I believe 17.1 sets the security of the DAQFactory part of the registry to fix this. Link to comment Share on other sites More sharing options...
SteveMyres Posted April 14, 2018 Author Share Posted April 14, 2018 Oh, okay. Windows is so annoying, with Run As Admin not being the same thing as running as an....admin. English? Who needs that? Link to comment Share on other sites More sharing options...
AzeoTech Posted April 16, 2018 Share Posted April 16, 2018 It is Windows trying to protect us from ourselves, and truthfully I find it handy. I don't really want to login on my workstation as a general user because of all the limitations, but an open admin like it used to be really is too much freedom and makes it easy for a simple accidental click to cause a lot of damage. With Run as Admin elevating even for logged in admins, it gives a sort of half ground, with some extra security for advanced user's at the price of an extra step in those rare occasions you need full privileges. Really, we need to move the registry variables and settings out of the registry and into a flat file. Link to comment Share on other sites More sharing options...
SteveMyres Posted April 17, 2018 Author Share Posted April 17, 2018 Well, I don't object too strongly to there being another level, but they should name it more descriptively, like "Run As SuperAdmin" or something. The nomenclature is poor. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.