Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove redundant information on selected realization #8509

Closed
dafeda opened this issue Aug 19, 2024 · 4 comments · May be fixed by #8511
Closed

Remove redundant information on selected realization #8509

dafeda opened this issue Aug 19, 2024 · 4 comments · May be fixed by #8511
Assignees
@andreas-el
Labels
improvement Something nice to have, that will make life easier for developers or users or both. qt

Comments

@dafeda
Copy link
Contributor

dafeda commented Aug 19, 2024 •
edited
Loading

Information marked in red is redundant and can be removed.
The current implementation is also buggy as it does not always show the correct iteration.

image
@dafeda dafeda added qt improvement Something nice to have, that will make life easier for developers or users or both. labels Aug 19, 2024
@andreas-el andreas-el self-assigned this Aug 19, 2024
@andreas-el andreas-el mentioned this issue Aug 19, 2024
Open
9 tasks
@larsevj
Copy link
Contributor

larsevj commented Aug 19, 2024

I do not agree that is is redundant information, as currently there is no immediate way of seeing which exact realization you have clicked on in the gui. It could be realization 0 from any iteration?

@andreas-el andreas-el mentioned this issue Aug 19, 2024
Merged
9 tasks
@andreas-el
Copy link
Contributor

I do not agree that is is redundant information, as currently there is no immediate way of seeing which exact realization you have clicked on in the gui. It could be realization 0 from any iteration?

I've made a second attempt to resolve this, where I address the bug where if the same indice is clicked in different tabs, the job_label does not update.
Also moved back the job_label to its original position.

@dafeda
Copy link
Contributor Author

dafeda commented Aug 19, 2024

I do not agree that is is redundant information, as currently there is no immediate way of seeing which exact realization you have clicked on in the gui. It could be realization 0 from any iteration?

Good point!
Is this bug specified in a different issue as well @andreas-el or should I repurpose this one?

@andreas-el
Copy link
Contributor

I do not agree that is is redundant information, as currently there is no immediate way of seeing which exact realization you have clicked on in the gui. It could be realization 0 from any iteration?

Good point! Is this bug specified in a different issue as well @andreas-el or should I repurpose this one?

I've addressed a bug where clicking the same index but in different iterations would not update the labels already, and moved the label back to its original position.
Relates to #8512

Maybe we should close this one as resolved?

@dafeda dafeda closed this as completed Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andreas-el andreas-el

Labels
improvement Something nice to have, that will make life easier for developers or users or both. qt
Projects
SCOUT
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove job_label from run_dialog andreas-el/ert
3 participants
@dafeda @larsevj @andreas-el