Added popover input for Connectivitymatrix editor widget#88
Open
deeptive wants to merge 1 commit intothe-virtual-brain:mainfrom
Open
Added popover input for Connectivitymatrix editor widget#88deeptive wants to merge 1 commit intothe-virtual-brain:mainfrom
deeptive wants to merge 1 commit intothe-virtual-brain:mainfrom
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
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.
Previously, users had to click on a cell, exit the matrix, scroll up, and manually change the cell value. To enhance the user experience, I added a popover input directly on the matrix, allowing users to update the cell value with a single click.
Additionally, I fixed a bug where switching between the weight matrix and the tract length matrix caused the values to not update correctly. The values from the initial matrix were being reflected, leading to confusion and potential incorrect updates. This issue has now been resolved.