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

Redesign hardware configuration and selection #281

Closed
bengtmartensson opened this issue Jun 16, 2019 · 0 comments
Closed

Redesign hardware configuration and selection #281

bengtmartensson opened this issue Jun 16, 2019 · 0 comments

Comments

@bengtmartensson
Copy link
Owner

bengtmartensson commented Jun 16, 2019

Present design is confusing and non-intuitive. Particularly non-intuitive is that the selection of a subpane of Sending HW and Capturing HW selects sending and capturing hardware respectively.

Having "only one instance of each HW class" (prohibiting e.g. sending and capturing with different instances of the same class) is acceptable, due to the nature of the program. (It would not be acceptable in a server-type program, like JGirs.)

Idea: Combine "Sending HW" and "Capturing HW" into one (top-level) pane, "Hardware". The subpanes thereof only opens/closes/configures, they do not select. For selecting there is already Options -> Transmitting hardware and Options -> Capturing hardware, which do the job. They can possibly be doubled by two pull-down combo-boxes under the future Hardware pane.

Related: #246.

Also: allowing the user to select a not-opened device without warning can be confusing.

@bengtmartensson bengtmartensson added this to the Milestone 3 milestone Jun 16, 2019
@bengtmartensson bengtmartensson modified the milestones: Milestone 3, No action Dec 8, 2019
@bengtmartensson bengtmartensson added this to the Milestone 5 milestone Aug 15, 2020
bengtmartensson added a commit that referenced this issue Aug 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant