#10637: fix Longitudinal profil does not close properly and it leads to conflicts between the longitudinal profil and measure plugin #10806
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
…y and it leads to conflicts between the longitudinal profil and measure plugin Description: - fix issue of draw conflicts between longitudinal profil and measure plugin in longitudinalProfile epic by reset drawing in 'LPonDockClosedEpic' - add unit test
1 task
MV88
requested changes
Feb 12, 2025
Description: - add drawOwner selector to be used in 'LPonDockClosedEpic' - add unit test
MV88
approved these changes
Feb 12, 2025
|
@ElenaGallo please test it in 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.
Description
This PR includes:
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#10637
What is the new behavior?
Demo_10637.mp4
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information