[haiku-bugs] Re: [Haiku] #8883: Text inputs don't follow Haiku "live update" UI paradigm.
- From: "jstressman" <trac@xxxxxxxxxxxx>
- Date: Tue, 14 Aug 2012 11:54:58 -0000
#8883: Text inputs don't follow Haiku "live update" UI paradigm.
------------------------------+----------------------------
Reporter: jstressman | Owner: stippi
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: User Interface | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
------------------------------+----------------------------
Comment (by jstressman):
A bit more on that thought...
This seems to be the kind of mentality that is used partially in things
like the Backgrounds preferences.
For instance the preview mode. What you would intuitively want to happen
is that when you changed the numeric X or Y input, you would want to see
the little preview image change to show your location change. As soon as
you change that number, you also want to see the "Apply" button become
highlighted to show that you can now apply the changes you've made in your
preview to your actual desktop. The CPU intensive part of the process that
is being avoided until necessary by allowing a live update of the smaller
non-CPU-intensive preview.
The same kind of "live update" mentality would appear to apply to the
Color Picker as well... you go into the color picker, and enter a hex
number for instance... so you have it not update until all 6
letters/numbers are entered, but at that point, after all 6 are typed in,
it updates the numeric values for the RGB etc and also updates the changed
color preview. This way you can easily type, backspace, type etc... to get
the color just right without having to do extra work... and then when
you're ready you then click "OK" to actually apply that color change (and
do whatever potentially more CPU intensive changes need to be made).
In both these cases (and I'm sure many others), the intuitive desired
functionality is a live update of some sort based on changes to those
inputs. Not hitting enter, or having to change focus after each small
change etc.
Maybe the reason this isn't done by default is that you still
programmatically have to define what the live update actually does? Like I
said, not being a programmer myself I don't really understand the
underlying reason things are the way they are. I'm just speaking from a
user perspective.
--
Ticket URL: <http://dev.haiku-os.org/ticket/8883#comment:1>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
