Tag Info

Hot answers tagged

23

There are too many issues with overlaying two different dragable items on the same control. For one - if you want both values to be the same then it's going to be hard to see that there are two indicators, or if you then want to adjust one of them it's difficult to make sure you're grabbing the correct item. If there are only two drag points, then why not ...


5

Try using a modified version of the first one, perhaps like so: What this essentially is is the first one, but with a box above to give an elegant preview of what you are currently pointing at. It will be above the user's fingers, and therefore out of their way. The reason I chose the first slider is because it has a bar, which is definitely the best way ...


4

Observations The difference in performance between touch keyboards and mechanical keyboards is clear and well studied. This paper shows that mechanical keyboards not only perform measurably better in speed and accuracy... ...but are also perceived better by users: Even pressure sensitive keyboards (with slightly more mechanical feel than touchscreens) ...


2

I solved a similar requirement by providing multiple sliders and linking them together, so that they "validate" against each other (UI to configure shifts - which ultimately comes down to start times). Right pictures indicate boundary conditions (min and max, so to speak): Shift 1: --|--------------------- 02:00 |----------- ---------|-- Shift 2: ...


1

You could have (apologies as this is crude): Switches: download bmml source – Wireframes created with Balsamiq Mockups or Suggest 'Hit Area' around the item: download bmml source


1

Obviously the definitive answer would come from building such a keyboard and doing suitable tests. I don't believe that comparisons between conventional keyboards and either touchscreen or Surface-type touch keyboards are necessarily instructive here, for two reasons: If all the keys other than the spacebar can be distinguished by touch, then the main ...


1

As I understand it (correct me if I'm wrong) pressing the upper region of the trackpad will be interpreted as a pressing of a spacebar button on standard keyboards. If a user touches the upper region but doesn't press it then this will be interpreted as a movement on trackpad. I can see a couple of potential issues that would be worth testing and I am sure ...


1

In my opinion the presentation of information and the interaction design needs to be based on the data as well as the user context, so unless you are able to somehow find research that fits exactly with your use case I would be weary about drawing conclusions from it. To guide you in the thinking process, perhaps consider it from a couple of different ...


1

Another alternative. Move the "active" points on your thumbs from the middle of the thumb to the right side of the left thumb and the left slide of the right thumb similar to what Android does with it's text cut/copy functionality. This has the advantage that both thumbs are on the same side, reducing the amount of vertical space needed and make it ...


1

I like JonW's solution better, but another possibility is that once the two thumbs are sufficiently close, you could halve the clickable regions of each thumb so that the left thumb's clickable region is its left half and the right thumb's clickable region is its right half. (Or you could continuously adjust the clickable regions as the distance between them ...



Only top voted, non community-wiki answers of a minimum length are eligible