starred/pathcopycopy

Fork 0

mirror of https://github.com/clechasseur/pathcopycopy.git synced 2026-04-25 12:15:58 +03:00

[GH-ISSUE #141] [FEATURE] Ability to hide "Settings..."-Command in Submenu #139

New issue

Closed

opened 2026-02-25 21:32:43 +03:00 by kerem · 12 comments

kerem commented

2026-02-25 21:32:43 +03:00

Owner

Originally created by @0nelight on GitHub (Apr 14, 2021).
Original GitHub issue: https://github.com/clechasseur/pathcopycopy/issues/141

Originally assigned to: @clechasseur on GitHub.

I would like to be able to disable the "Settings..."-Command in the Submenu because I rarley edit the settings and therefore it would be nice to have an option to remove it from the Submenue to keep the UI clean.
In case I disable it I can navigate to the Settings.exe and change my settings there.

Originally created by @0nelight on GitHub (Apr 14, 2021). Original GitHub issue: https://github.com/clechasseur/pathcopycopy/issues/141 Originally assigned to: @clechasseur on GitHub. I would like to be able to disable the "Settings..."-Command in the Submenu because I rarley edit the settings and therefore it would be nice to have an option to remove it from the Submenue to keep the UI clean. In case I disable it I can navigate to the Settings.exe and change my settings there.

kerem

2026-02-25 21:32:43 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-25 21:32:44 +03:00

Author

Owner

@blackcrack commented on GitHub (Apr 15, 2021):

this belongs to the extension and need to show ever, there is no possibility to unhide the settings agains.
Thing to the no-technical/non-extended Users, there want come massive troubles..
in direction "My settingsmenu is gone" "how can i recover my Settingsmenu" and so on..

bad idea... ! trust me.. i be more as 25 Years at some software ..
(was also in Bulletin Board's over Terminal Emu. over Drt. with Cardware, Shareware and some Soft)
best
Blackcrack

Blackysgate .de / .net

@blackcrack commented on GitHub (Apr 15, 2021): this belongs to the extension and need to show ever, there is no possibility to unhide the settings agains. Thing to the no-technical/non-extended Users, there want come massive troubles.. in direction "My settingsmenu is gone" "how can i recover my Settingsmenu" and so on.. bad idea... ! trust me.. i be more as 25 Years at some software .. (was also in Bulletin Board's over Terminal Emu. over Drt. with Cardware, Shareware and some Soft) best Blackcrack Blackysgate .de / .net

kerem commented

2026-02-25 21:32:44 +03:00

Author

Owner

@0nelight commented on GitHub (Apr 15, 2021):

@blackcrack We can offer the option in the registry so the possibility of accidentally disable this by a non-expert user can be avoided completely.

@0nelight commented on GitHub (Apr 15, 2021): @blackcrack We can offer the option in the registry so the possibility of accidentally disable this by a non-expert user can be avoided completely.

kerem commented

2026-02-25 21:32:44 +03:00

Author

Owner

@n0f4c3 commented on GitHub (Apr 15, 2021):

I agree with blackcrack it's a very bad idea and even the way you suggest to set up the option is risky because an inexperienced user might decide to go and change the value in his registry and do the wrong thing

@n0f4c3 commented on GitHub (Apr 15, 2021): I agree with blackcrack it's a very bad idea and even the way you suggest to set up the option is risky because an inexperienced user might decide to go and change the value in his registry and do the wrong thing

kerem commented

2026-02-25 21:32:44 +03:00

Author

Owner

@0nelight commented on GitHub (May 3, 2021):

@n0f4c3 Your argument of "doing the wrong thing" is exactly what a user would do if he enables an option in the Windows-Registry he doesn't intend to enable - that's true for every bit in your computer... Only the users mind can protect him of doing that - and the barrier to do an unintended change of the windows registry is very high due all to the commands which have to be executed before we can change a registry-entry. Either you have to intentially play with settings or you have to be on some kind of drugs to do this unintentionally. I personally don't get your argument, but I am open to discuss.

@0nelight commented on GitHub (May 3, 2021): @n0f4c3 Your argument of "doing the wrong thing" is exactly what a user would do if he enables an option in the Windows-Registry he doesn't intend to enable - that's true for every bit in your computer... Only the users mind can protect him of doing that - and the barrier to do an unintended change of the windows registry is very high due all to the commands which have to be executed before we can change a registry-entry. Either you have to intentially play with settings or you have to be on some kind of drugs to do this unintentionally. I personally don't get your argument, but I am open to discuss.

kerem commented

2026-02-25 21:32:44 +03:00

Author

Owner

@n0f4c3 commented on GitHub (May 3, 2021):

@ 0nelight me this is your argument several levels of security before you can access the regist I don't understand because there is only one and it is this window : (sorry for the French image I am Quebec Canadian)
so to come back to what I said he just has to click on yes and he can do whatever he wants even if it can be fatal for the computer so that's one of the reasons why your idea seems dangerous to me

@n0f4c3 commented on GitHub (May 3, 2021): @ 0nelight me this is your argument several levels of security before you can access the regist I don't understand because there is only one and it is this window : ![20210503_083215](https://user-images.githubusercontent.com/14986315/116877381-ddb19880-abeb-11eb-80cf-a2c0e2c88aec.jpg) (sorry for the French image I am Quebec Canadian) so to come back to what I said he just has to click on yes and he can do whatever he wants even if it can be fatal for the computer so that's one of the reasons why your idea seems dangerous to me

kerem commented

2026-02-25 21:32:44 +03:00

Author

Owner

@0nelight commented on GitHub (May 3, 2021):

What about messing with the million other registry-entries that can mess windows up? Would you touch them when you are not sure what you are doing? No you would not 😅 Additionally you need a lot of steps to change a specific registry entry when starting from the desktop. In case I don‘t answer anymore its because of the inaccuracies in your arguments - don‘t take it personal 😉

@0nelight commented on GitHub (May 3, 2021): What about messing with the million other registry-entries that can mess windows up? Would you touch them when you are not sure what you are doing? No you would not 😅 Additionally you need a lot of steps to change a specific registry entry when starting from the desktop. In case I don‘t answer anymore its because of the inaccuracies in your arguments - don‘t take it personal 😉

kerem commented

2026-02-25 21:32:44 +03:00

Author

Owner

@n0f4c3 commented on GitHub (May 3, 2021):

@0nelight in the best case you are right but for a user who wants to experiment and learn he will do anything even if it can be dangerous because he does not know it

@n0f4c3 commented on GitHub (May 3, 2021): @0nelight in the best case you are right but for a user who wants to experiment and learn he will do anything even if it can be dangerous because he does not know it

kerem commented

2026-02-25 21:32:44 +03:00

Author

Owner

@clechasseur commented on GitHub (May 3, 2021):

There's no need to argue all that much. We already have a setting to completely hide the submenu, which also prevents the user from accessing the settings, and it hasn't caused much trouble in all these years. I believe a registry-only entry would be fine.

@clechasseur commented on GitHub (May 3, 2021): There's no need to argue all that much. We already have a setting to completely hide the submenu, which also prevents the user from accessing the settings, and it hasn't caused much trouble in all these years. I believe a registry-only entry would be fine.

kerem commented

2026-02-25 21:32:44 +03:00

Author

Owner

@n0f4c3 commented on GitHub (May 4, 2021):

@clechasseur Thank you for your answer and sorry for all that

@n0f4c3 commented on GitHub (May 4, 2021): @clechasseur Thank you for your answer and sorry for all that

kerem commented

2026-02-25 21:32:44 +03:00

Author

Owner

@clechasseur commented on GitHub (Jul 26, 2021):

This has been implemented in default and will be part of the next release. To avoid displaying the Settings entry, add the following registry entry in HKEY_CURRENT_USER\Software\clechasseur\PathCopyCopy:

AlwaysShowSettingsEntry (type DWORD, value 0)

@clechasseur commented on GitHub (Jul 26, 2021): This has been implemented in `default` and will be part of the next release. To avoid displaying the Settings entry, add the following registry entry in `HKEY_CURRENT_USER\Software\clechasseur\PathCopyCopy`: `AlwaysShowSettingsEntry` (type `DWORD`, value `0`)

kerem commented

2026-02-25 21:32:44 +03:00

Author

Owner

@ggbbrr commented on GitHub (Aug 31, 2021):

Wasn't this option already present before ?

Key = "KeyLock" ( 0 or 1 )

I know it still works.

@ggbbrr commented on GitHub (Aug 31, 2021): Wasn't this option already present before ? Key = "KeyLock" ( 0 or 1 ) I know it still works.

kerem commented

2026-02-25 21:32:44 +03:00

Author

Owner

@clechasseur commented on GitHub (Aug 31, 2021):

Wasn't this option already present before ?

Key = "KeyLock" ( 0 or 1 )

I know it still works.

KeyLock doesn't really do the same thing. While it doesn't display the Settings entry, true, it also disables editing settings altogether and prevents reading from settings in HKEY_CURRENT_USER if they exist.

@clechasseur commented on GitHub (Aug 31, 2021): > Wasn't this option already present before ? > > Key = "KeyLock" ( 0 or 1 ) > > I know it still works. `KeyLock` doesn't really do the same thing. While it doesn't display the Settings entry, true, it also disables editing settings altogether and prevents reading from settings in `HKEY_CURRENT_USER` if they exist.