This repository was archived by the owner on Aug 31, 2021. It is now read-only.
[[ Bug 22285 ]] Restrict selection of key field in customprops editor #2133
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
This patch ensures that the key field of the custom properties editor in the property inspector is only selected in response to a change in the tree view hilite.
runrevmark
approved these changes
May 15, 2020
|
@livecode-vulcan review ok 47f395e |
|
💙 review by @runrevmark ok 47f395e |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
This patch ensures that the key field of the custom properties
editor in the property inspector is only selected in response to
a change in the tree view hilite.
This is essentially just a tweak of #2077 but using the fact that
hiliteChangedonly happens when the hilite really changes.