Improved window parameter handling #3457
Open
+127
−56
Conversation
This file contains 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
Deploying wails with
|
| Latest commit: |
5f89fde
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://fa50aa13.wails.pages.dev |
| Branch Preview URL: | https://v3-alpha-feature-new-window.wails.pages.dev |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Original PR: #3424
Description
** This PR has been opened up to start a discussion on what the right solution is **
There will be times when you want to know what window made a call to a bound method. This PR offers 2 solutions for 2 different scenarios:
context.Contextin the first parameter, the context will have a value "window" which will return the calling window.application.Windowas the first parameter. It will always be populated with the calling window if called from JS.The
bindingexample has been updated to show both usages.