GNOME Bugzilla – Bug 649637
Unexpected dynamic resizing of window due to conversions
Last modified: 2018-05-22 11:45:50 UTC
While using Advanced mode and typing numbers lets say 6 digits and more then window start resizing itself to be able to display a result of conversion. In my opinion its distracting, because user has to slightly change position where they are looking.
I have idea for 3 possible fixes:
- simply set larger initial width of label that displays result so that it can hold for example number*10^three_digits_number without being resizing
- add checkbox to activate/inactivate conversions
- add "No conversion" to selector of conversion which disables conversion
I say scrap the conversion interface entirely. The unconventional selectors for units should be a clue to the programmer that something is not right about the design. (Such menus do not ordinarily have submenus, and submenus do not ordinarily have titles.)
Take the feature out and don't put it back in until there is a good design.
What about an option to hide the conversion bar? You really don't need it ALWAYS, but you need it SOMETIMES.
A dconf option would be enough (for me), there's no need for en UI change.
Looks like the bug has already been fixed. I cannot reproduce it as the default converstion interface from ounces to grams shows the result in scientific notation, which fits in the allocated space.
Created attachment 339290 [details]
Screenshot of the advanced mode
Here is a screenshot for the above comment.
No, it's not fixed. Just watch the steps before it switches to scientific notation. For me, it switches its size after the 6th, 7th, 8th and 9th entered digit. Then the transition to scientific notation is finished and it doesn't change its size anymore.
PS: workaround: Switch to standard conversion nanometer to lightyears --> output is always 0, no size changing anymore.
-- GitLab Migration Automatic Message --
This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-calculator/issues/17.