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

Group adjacent ranges of component refs in the BOM table #94

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

JJJollyjim
Copy link
Contributor

Resolves #20.

The component lookup box behaves just as before.

If you enter a ref that isn't from the end of a range into the filter box, it will still match the row, but with no highlight. I can improve this behaviour if you wish (highlight the range? expand out the relevant range and highlight the relevant part?)


From the motherboard demo:

After:

2019-04-15-021708_948x828_scrot

Before:

2019-04-15-021655_958x509_scrot

@qu1ck
Copy link
Member

qu1ck commented Apr 14, 2019

The reason I have not done this yet is that I want to finish wishlist from #17 first. There definitely is utility in controlling individually which ref was placed and having visual feedback for that.

Once that is implemented grouping would have to take into account the state of the ref.
Also there should be an option to disable grouping, just persisted html checkbox is enough, no need to update python side.
UX regarding highlighting and grouping is tricky. Highlighting the group sounds good but I'll have to think this through.

Either way please hold off on this functionality until #17 and #52 are closed.

@wraybowling
Copy link

Wait... are the images for Before and After labelled backwards?

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.

R1,R2,R3 could become R1-R3
3 participants