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.

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

Color TrackScheme Hierarchy according to the time point (Issue 213) #231

Closed
wants to merge 64 commits into from

Conversation

stefanhahmann
Copy link
Collaborator

Closes #213

maarzt and others added 18 commits March 21, 2023 13:58
* Use this class to display and update the current timepoint and the number of spots at that timepoint according to the current timepoint model
This unifies the way how: SelectModel, GraphColorGenerator and TimepointModel,
are initialized and used in the LineageTreeLayout class.
Extract method addScreenEdge form cropAndScale. This change reduces code
duplication between the two implementations of cropAndScale.
* Use these classes to perform fading in TrackSchemeHierachy view
Copy link
Contributor

@maarzt maarzt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are getting closer 👍

@stefanhahmann
Copy link
Collaborator Author

The PR somehow introduces a bug when rendering the the TrackScheme Branch. The bug is triggered by resorting the TrackScheme using one of the plugins in mastodon-tomancak. For example "Plugins > Trees Management > Flip Descendants".

GIF 05 05 2023 14-45-05 GIF 05 05 2023 14-45-05

This need to be clarified before merging.

Thanks for pointing this out.

This bug was unfortunately introduced by this commit: 7406066

It should now be resolved by this commit: 37717dc

@tinevez
Copy link
Contributor

tinevez commented May 11, 2023

Ready for review?

@stefanhahmann
Copy link
Collaborator Author

Ready for review?

Yes.
@maarzt reviewed already extensively, but since the changes are massive, a second review would be good.

@tinevez
Copy link
Contributor

tinevez commented May 17, 2023

Sorry I am late on this. Will work on it

…lues should be used with java.util.Color objects
@stefanhahmann
Copy link
Collaborator Author

Sorry I am late on this. Will work on it

@tinevez may we kindly remind you on this review? we would love to have this finished/merged.

…ings panel.

Its size was too big to accomodate the default width of TrackScheme
windows. Now we need to center and shrink the other widgets.
So that
- we have some space to display them all with the default
window width,
- their texts are all aligned vertically on the same baseline,
- the font used is the same everywhere.
@tinevez
Copy link
Contributor

tinevez commented Jun 29, 2023

I made a PR for your PR with minor changes, mainly sizing the opportunity to fix the look of the settings panel.
Take them if you feel like it.
To me otherwise it is good to be merged to dev.

stefanhahmann and others added 4 commits June 30, 2023 09:40
* Adds section label in TrackScheme settings editor
* Changes to the TrackScheme Toolbar UI
* Add a tooltip with some explanation of the function of the button
* On a windows machine the group lock ids (the numbers) where not shown, but "..." instead
* I think only preferred size is need to set the size
* I think it is better to avoid abbreviations in user interfaces. What might be clear to us (t = timepoint) may not be so clear for a newbie user.
@stefanhahmann
Copy link
Collaborator Author

Hi @tinevez,

I merged your PR stefanhahmann#17.

However after merging the toolbar of the trackscheme windows looked like this on my (windows) machine:

grafik

Thus, I increased the size of the Group Locks Panel again: 3162483

Also, I think, it is better to avoid abbreviations in user interfaces. Thus I made these changes:

which make the toolbar of trackscheme window look like this on my windows:

grafik

Hope you agree?

@tinevez
Copy link
Contributor

tinevez commented Jun 30, 2023

Go for it!

@stefanhahmann
Copy link
Collaborator Author

Go for it!

@maarzt may I ask you to merge (I do not have the rights to do so)? If you have questions regarding the remaining conflict, you may contact me.

@tinevez
Copy link
Contributor

tinevez commented Jun 30, 2023

Merged! But I had to do it via a local branch I had rights on.
This PR can be marked as merged and closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants