hydrusnetwork / hydrusnetwork/hydrus

Radio buttons with comparison operators can be confusing, please consider dropdowns

Open
#896 5 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request system:user-interface
Dominant language
Python
Stars
3.2k
Forks
207
PR merge metrics
No merged PRs in 30d

Description

Several options that check a numeric or date range in the input predicate dialog use a radio button to select a comparison operator:

  • less than
  • ≈ (approximate?)
  • equals
  • greater than

The choices are very small and it's quite easy to confuse which one belongs to which radio button. (I mix these up almost every day)

Please consider using a dropdown list here, similar to iTunes Smart Playlists: https://support.apple.com/guide/itunes/create-delete-and-use-smart-playlists-itns3001/windows

A dropdown would allow things to look something like this, removing the ambiguity:

  • greater than
  • equals =
  • ≈ (approximate, "near" or something)
  • less than

Or for dates:

  • before
  • after
  • is
  • ≈ ("around"? I'm not sure what this actually does in Hydrus)

Something similar might be helpful for other places that use a horizontal line of radio buttons, such as the ratings input predicates.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the input predicate dialog and other horizontal radio-button groups, including the ratings input predicates. Review how numeric and date comparison operators are represented, especially the approximate option, before deciding the dropdown labels. Done means the relevant controls no longer make operators easy to confuse and their existing predicate behavior remains clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.