starred/pathcopycopy
1
0
Fork 0
mirror of https://github.com/clechasseur/pathcopycopy.git synced 2026-04-25 12:15:58 +03:00
Code Issues 31 Projects Releases Packages Wiki Activity

[GH-ISSUE #60] Keylock command modifies submenu #58

New issue
Closed
opened 2026-02-25 21:32:33 +03:00 by kerem · 5 comments
kerem commented 2026-02-25 21:32:33 +03:00
Owner
Copy link

Originally created by @Agivx3 on GitHub (Mar 24, 2019).
Original GitHub issue: https://github.com/clechasseur/pathcopycopy/issues/60

Originally assigned to: @clechasseur on GitHub.

When using keylock command in registry the submenu which you defined before is modified to
suddenly show other entries

Originally created by @Agivx3 on GitHub (Mar 24, 2019). Original GitHub issue: https://github.com/clechasseur/pathcopycopy/issues/60 Originally assigned to: @clechasseur on GitHub. When using keylock command in registry the submenu which you defined before is modified to suddenly show other entries
kerem 2026-02-25 21:32:33 +03:00
  • closed this issue
  • added the
    question
         label
kerem commented 2026-02-25 21:32:33 +03:00
Author
Owner
Copy link

@clechasseur commented on GitHub (Mar 25, 2019):

Can you post a screenshot of the menu with and without KeyLock so that we can see the difference?

<!-- gh-comment-id:476018830 --> @clechasseur commented on GitHub (Mar 25, 2019): Can you post a screenshot of the menu with and without KeyLock so that we can see the difference?
kerem commented 2026-02-25 21:32:33 +03:00
Author
Owner
Copy link

@Agivx3 commented on GitHub (Mar 25, 2019):

Please review the attached screenshots: 1. Settings 2. Without keylock set 3. Keylock set
Screen1
Screen2
Screen3

<!-- gh-comment-id:476062416 --> @Agivx3 commented on GitHub (Mar 25, 2019): Please review the attached screenshots: 1. Settings 2. Without keylock set 3. Keylock set ![Screen1](https://user-images.githubusercontent.com/46596208/54897591-6025e500-4ec9-11e9-99b3-2499a31386fa.jpg) ![Screen2](https://user-images.githubusercontent.com/46596208/54897598-661bc600-4ec9-11e9-9d55-9c890f95528c.jpg) ![Screen3](https://user-images.githubusercontent.com/46596208/54897602-6a47e380-4ec9-11e9-9cd0-fbf37226d037.jpg)
kerem commented 2026-02-25 21:32:33 +03:00
Author
Owner
Copy link

@clechasseur commented on GitHub (Mar 25, 2019):

Hmm. Thanks for the screenshot, I'll look at the code to see what's going on...

<!-- gh-comment-id:476181591 --> @clechasseur commented on GitHub (Mar 25, 2019): Hmm. Thanks for the screenshot, I'll look at the code to see what's going on...
kerem commented 2026-02-25 21:32:33 +03:00
Author
Owner
Copy link

@Agivx3 commented on GitHub (Apr 4, 2019):

Anything new about this ?

<!-- gh-comment-id:479909145 --> @Agivx3 commented on GitHub (Apr 4, 2019): Anything new about this ?
kerem commented 2026-02-25 21:32:33 +03:00
Author
Owner
Copy link

@clechasseur commented on GitHub (Apr 30, 2019):

Ok, sorry it got me so long to get back to this, but I finally took some time to check the code. Basically, this is working as intended.

Path Copy Copy reads settings from registry keys under Software\clechasseur\PathCopyCopy. There's a global copy of this key in HKEY_LOCAL_MACHINE and one for each user in HKEY_CURRENT_USER. Settings in HKCU override those in HKLM.

The KeyLock registry value is a way to lock users out of overriding the global settings. When this is set, the user key is not checked at all - we only use the global key in HKLM.

Thus, what you see is a result of only using the global settings.

If you wanted to see proper settings when using KeyLock, you'd have to configure those settings and then copy them to the registry key in HKEY_LOCAL_MACHINE.

I hope this makes sense, ping here if you need more info. I'll leave this open for a while.

<!-- gh-comment-id:487804205 --> @clechasseur commented on GitHub (Apr 30, 2019): Ok, sorry it got me so long to get back to this, but I finally took some time to check the code. Basically, this is working as intended. Path Copy Copy reads settings from registry keys under Software\clechasseur\PathCopyCopy. There's a global copy of this key in HKEY_LOCAL_MACHINE and one for each user in HKEY_CURRENT_USER. Settings in HKCU override those in HKLM. The KeyLock registry value is a way to lock users out of overriding the global settings. When this is set, the user key is not checked at all - we only use the global key in HKLM. Thus, what you see is a result of only using the global settings. If you wanted to see proper settings when using KeyLock, you'd have to configure those settings and then copy them to the registry key in HKEY_LOCAL_MACHINE. I hope this makes sense, ping here if you need more info. I'll leave this open for a while.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
default
chore/vc17
v20.0
v19.0
v18.0
v17.1.1
v17.1
v17.0.1
v17.0
v16.0.1
v16.0
v15.1
v15.0
v14.0.1
14.0
Labels
Clear labels   
bug

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
fixed

   
help wanted

   
help wanted

   
invalid

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
waiting for input

   
wontfix
No labels
bug
duplicate
enhancement
enhancement
enhancement
fixed
help wanted
help wanted
invalid
pull-request
question
waiting for input
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/pathcopycopy#58
No description provided.