All users vs current user settings
An award-winning drawing program for children of all ages
Brought to you by:
wkendrick
Menu
▾
▴
#201 All users vs current user settings
When configuring special display resolution settings for the current user, they are not honored if setting for all users is "Full screen". Obviously "All users" should act as a template and after that current user should be able to modify that. Now "All users" seems to overide other settings.
i have fixed this bug.what i hve to do next or how to submit?
i have written there all user vs current user setting ,where i made changes
same in this file
hello
check these files.
Assigning to Pere, since he's been very good about accepting patches for us. :) (Reassign to nobody, if you'd rather not work on this, Pere!)
Not sure this is a valid bug. Could be confusion that "all users" is system-wide settings, while "current user" has its own, separate settings, which may override them.
Still here, even though problem is not valid for my case any more, kids grew out of this program long time ago and iMac also not in use any more. So I have no idea, if current version possibly still has the problem. If you read the description carefully, you'd noticed that problem was that "system" overrides "user" settings when it should be of course vice versa. md ekramul ansari on the chain mentioned that he/she had already fixed the problem on the code and was asking way to submit it, based on the chain nothing happened after that though.
I can confirm,: remove the ~/tuxpaintrc file and set allusers to fullscreen native, start tuxpaint and see it running fullscreen, close tuxpaint, set current user to windowed 800x600, start tuxpaint and see it still running fullscreen.
The code from Ekramul adresses it by changing the binary checkbox 'Use "AllUsers" settings' into a tristate 'Merge', 'Use "All Users" settings', 'Discard "all users" settings'
being the first 2 the same behavior as currently and the last one making use of the sysconfig=no entry in the config file.
Note that this is an improvement for tuxpaint-config (allow users to make use of the sysconfig=no feature) but only a partial solution for this bug as the real problem seems to lay on how we parse the config files in tuxpaint itself.
I've made a diff from Ekramul's code and adapted to the current source so it applies fine, Bill, could you take a look at it?
Thanks
BTW, also BIG THANKS fro the bug/feature request/tasks cleanup :)
@perepujal Thanks for "rebasing" this patch, and @ekramula2 thanks for the original code and please accept my apologies for us not merging it sooner! I think some of the labels need reworking, but otherwise I think this makes sense. I may also add some additional text to the main "About" text, to explain how this works.