add "openas" into lpVerb verbs list #1851
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@tomqiaozc : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am writing to request an update to the technical documentation concerning the
lpVerbparameter. Specifically, I would like to suggest the inclusion of theopenasverb in the list of commonly used options.In my recent project development, I utilized the
openasverb for the "Open With" operation, which allows users to choose an application to open a file. This functionality is essential for our application's flexibility and user experience. As per our development specifications, it is required that all APIs and parameters employed must be supported and documented officially.The existing documentation already provides comprehensive details on commonly used verbs such as
edit,open,explore, and others. Addingopenasto this list would not only align with the documentation's completeness but also support developers who rely on these resources for accurate and authoritative information.