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

BHoM_UI: More advanced interface for BHoM Data #66

Open
IsakNaslundBh opened this issue Jan 17, 2019 · 2 comments
Open

BHoM_UI: More advanced interface for BHoM Data #66

IsakNaslundBh opened this issue Jan 17, 2019 · 2 comments
Assignees
Labels
severity:low Doesn't stop/slow current workflow type:feature New capability or enhancement

Comments

@IsakNaslundBh
Copy link
Contributor

Adding a small UI window that could help engineers pick any BHoM data based on various parameters would be of great benefit.

Something that could like explode out all the objects in a picked data set into a table and then allow you to scroll through all the data and select one item. Also in long run could start adding various filtering etc based on the various parameters.

@al-fisher al-fisher added severity:medium Slows progress, but workaround is possible type:feature New capability or enhancement and removed feature labels Mar 20, 2019
@adecler
Copy link
Member

adecler commented Sep 24, 2019

Fore example, the RHS sections for the UK_SteelSections. The dropdrown itself is taking 3 seconds to open and has far too many options.

@IsakNaslundBh, I have raise an issue regarding menu navigability in general (see #137 ). I think it covers most of your needs except for the pop-up window with a excel type table to select from. So I believe this could be implemented later than 3.1. If you think implementations detailed in #137 are enough, feel free to close this.

@IsakNaslundBh IsakNaslundBh added severity:low Doesn't stop/slow current workflow and removed severity:medium Slows progress, but workaround is possible labels Sep 24, 2019
@IsakNaslundBh
Copy link
Contributor Author

Thanks @adecler .

If it is ok with you, might as well keep this open, but not as a priority for now. I also dropped the severity to low for this. Happy for this to get pushed to 3.1 if no time is found for fixing this now.
Think the fixes suggested in #137 will be a massive boost and solve one of the main issues with picking up data (speed and navigation of the dropdown) while I see this issue as something slightly different (as you mentioned).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity:low Doesn't stop/slow current workflow type:feature New capability or enhancement
Projects
None yet
Development

No branches or pull requests

4 participants