User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an application I'm working on where a portion of the interface is very mouse-centric. You drag the mouse to create/manipulate regions, then assign properties to those regions. Below is an example of a current prototype.

Defining Regions

The problem I'm facing, though, is that after dragging to define the region, the user then would typically want to define the properties. This means moving the mouse to the upper left, clicking on the box they want to edit, then typing in the relevant information. To make this more streamlined, I'm trying to come up with a clean way to let the user immediately type the information without any additional clicking. I'm thinking of maybe bringing up a 'pop over' edit box immediately where the mouse cursor is, with focus to begin typing. They can then enter things like '100' or '50 to 130' and either press Enter or click elsewhere to close the text entry.

I have limited UX experience, though (I'm a software engineer by trade), so I'm curious to get feedback on a few items:

  1. Will bringing up a text box automatically like this be perceived as disruptive by the user? A sub-set of users might prefer to define all regions ahead of time, then select them and edit the properties later, for instance. This is a brand new part of the UI (multi-region was not previously supported), so I don't have any data to know how they'll react yet.

  2. How do I make it easy for the user to discover that they can type the values immediately rather than having to click elsewhere first?

  3. When the text box is up, how do I make it easy for the user to discover that they can type not only numbers, but also ranges like '50 to 100' (automatically creating a 'gradient' rather than a 'constant' fill)?

  4. I'm also considering letting the user type something like 'file' to bring up a dialog and load data from a file, for instance (corresponds to the little file icon button in the upper left.) Would it be too disruptive to have a dialog pop up immediately after typing? Should I require they press Enter first?

Some clarifications:

  1. The large yellow rectangle is a 'region'.
  2. The properties you enter apply to the entire 'region' (all boxes inside it.)
  3. My thought is that you can enter the values for the most relevant properties by typing a single line of text.
  4. You can ignore the well selector on the right (that's a way to switch between 'layers' and isn't relevant to this task.)


Here is a candidate 'pop-up' entry box. The gray text is a 'water mark' that goes away when the user starts typing. I'm thinking if the user presses Escape or mouses too far without typing, the popup goes away. They can get it back by clicking on the region again.

enter image description here

share|improve this question
what does the drag-selection accomplish? Does it allow them to enter one text field and have it applied to all 6 selected items at once? – DA01 Mar 21 '14 at 16:54
@DA01, the drag-selection creates the rectangular 'region' to which the particular properties will be applied. Typical flow I envision would be 'drag to create region, set properties, drag to create next region, set properties, etc.' – Dan Bryant Mar 21 '14 at 16:56
So, if a user selects those 6 as a 'region' are they then typing in 6 properties, or just one property that applies to all six? – DA01 Mar 21 '14 at 16:57
@DA01, I only allow creating/selecting a single 'region' at a time. The large yellow rectangle is a 'region' above. The text entry I'm imagining would apply to the newly created region only. – Dan Bryant Mar 21 '14 at 16:59
Ah. Well, I think your 'show a text box upon selection' idea is perhaps the direction to go in. Some of your other ideas, though, appear to be turning the text box into more of a command-line UI. This isn't necessarily bad, but success may be highly contingent on the type of users using your app. – DA01 Mar 21 '14 at 17:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.