-
Notifications
You must be signed in to change notification settings - Fork 108
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
Use dropdown list instead of editbox for box classes #103
Use dropdown list instead of editbox for box classes #103
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice PR.
I think the class definition will change with the pending PR but I would just adapt it, if you are fine with it.
Please see the comments and consider the styling adaptions for the dropdown (not sure what is possible thereof).
Ah, before I forget. Please squash your commits before you merge. So to make rebasing easier ;) |
* Use dropdown list instead of editbox for box classes * not ignore labels/schema * mypy and black * change to_open3d_point_cloud, to_point_cloud to staticmethod-s * remove print * change stylesheet for QComboVox#current_class_dropdown
* Use dropdown list instead of editbox for box classes * not ignore labels/schema * mypy and black * change to_open3d_point_cloud, to_point_cloud to staticmethod-s * remove print * change stylesheet for QComboVox#current_class_dropdown
* Use dropdown list instead of editbox for box classes * not ignore labels/schema * mypy and black * change to_open3d_point_cloud, to_point_cloud to staticmethod-s * remove print * change stylesheet for QComboVox#current_class_dropdown
* Use dropdown list instead of editbox for box classes * not ignore labels/schema * mypy and black * change to_open3d_point_cloud, to_point_cloud to staticmethod-s * remove print * change stylesheet for QComboVox#current_class_dropdown
My original plan was to put this together with the PR that assigning box labels to point labels but I realise that it's a logically separated functionality, so I split it to this PR so it's easier to review component-by-component.
This PR replace the class edit box to class drop down box to force the user to have a restricted set of options when setting the box classes as well as the point classes. Because of the nature of it, the class definition in
config.ini
is removed. Ideally,std_object_class
should be removed as well but because there is another PR addressing that, it is retained for now.The label_definition concept is therefore shared across two modes. This also paves the way for the label definition
setup
idea.Expected behaviours:
std_object_class