You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe. Win32Clipboard is an official documented dependency of ShellAnything. For new users, this makes the process of building ShellAnything longer and harder to build. The less dependency to build the better.
Other users have also mentioned that <clipboard> action should moved as a plugin. Potentially because Win32Clipboard is a dependency (which complicates the build process) with few added functionality.
Describe the solution you'd like
The proposed feature is to merge the Win32Clipboard library directly into ShellAnything. As the developer of both ShellAnything and Win32Clipboard, one should be able to merge both projects in order to make ShellAnything building process easier to follow for new users.
Also both product are published with the MIT license.
Describe alternatives you've considered
Leave the dependency as is.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Win32Clipboard is an official documented dependency of ShellAnything. For new users, this makes the process of building ShellAnything longer and harder to build. The less dependency to build the better.
Other users have also mentioned that
<clipboard>
action should moved as a plugin. Potentially because Win32Clipboard is a dependency (which complicates the build process) with few added functionality.Describe the solution you'd like
The proposed feature is to merge the Win32Clipboard library directly into ShellAnything. As the developer of both ShellAnything and Win32Clipboard, one should be able to merge both projects in order to make ShellAnything building process easier to follow for new users.
Also both product are published with the MIT license.
Describe alternatives you've considered
Leave the dependency as is.
The text was updated successfully, but these errors were encountered: