Hot answers tagged cursor
To add to DA01's great answer, here's the history of cursor arrow. The link also links to a well known document from Xerox with further explanation, from which I took the image below. However, this document doesn't explain the reason behind the tail. This being said, the reasons for tilting explain why tilting was needed. Now I'll take the same image ...
It's an arrow: pictograms of arrows have mostly always had at least the arrow head and the shaft: Whoever drew the cursor as we know it was drawing an arrow. It became the default standard. You are right, it probably would work without the shaft (or tail) just as well. It's just that it's not what the UI designer chose when it was created and we've ...
I think you've answered your own question. The special cursors demonstrated on that web site are rarely needed, whether in a browser or outside of one. Of the 31 cursors, 14 of them are for resizing elements, which isn't really a common task.
I see Progress and Help used fairly regularly. Other than that, the rest of them are mostly situational... there's no need to use them out of specific tasks and environments. Using cursors where not absolutely necessary violates the rule of don't confuse your users, ever. If you can use a normal cursor, do.
"Default", "Pointer" and "Text" are defaults in browsers. Others we forget to specify for developer — because we paint static images. But if we work with interaction our-self, we will remember to use "Not available" cursor for disabled elements for example.
Move objects to rearrange them, grab objects to perform operations on them The move cursor should be used when objects are just being rearranged (translated) without any alteration to their properties other than position. For example: Rearranging shapes on a canvas Rearranging items in a list The grab cursor is usually used for drag and drop operations ...
look at how your finger points it could also be a wrist. people also see based on shapes and the cursor as is has more breaks and easily stands out on top of pages than a triangle. Also a right handed person pointing explains the direction of the cursor. Read more about it from the question why the cursor is tilted and not straight
Think about what your users need The magnifying glass is a very well understood idiom for zoom, so it's probably the right cursor to use. The use of inset (plus on the inside) vs offset (plus to the right) will depend on the size and use of the cursor. For example: For large cursors the inset cursor is visually simpler than the offset cursor, so option ...
In many drawing programs, grab is used to move the drawing surface (canvas) around, i.e., to show a different part of it. This is called panning. Move is used to move the selected object around within the canvas.
From my experience, the grab and grabbing cursor behaviour works when you need an explicit hover and click & hold behaviour for movable UI elements, which makes sense for desktop applications because these are standard cursor interactions. The move cursor tends to be used when there is no particular need to differentiate between the hover and click & ...
The I-beam is just a descriptive term, as it resembles a construction I-beam, the correct term would be 'a caret'. - https://en.wikipedia.org/wiki/I-beam Apparantly it has several uses, first of all, the idea is that it doesn't resemble an existing character. This means that it's first real uses where on graphical displays and not so much on character based ...
it depends on what kind of interactivity. as each will be best represented with a different cursor icon when hovering over it. So it depends what kind of interactivity does your chart have. looking at the collection of icons i can see a few interactions relevant to some of them. -editable text field. -adjustable column, row width, height. -scalable ...
In most cases the cursor primarily is to SELECT, POINT or CLICK. Extra actions such as GRAB, CROSSHAIRS are handy for other more specific type applications like picture uploads, crop and resizing.
This is a design choice by Google and you should ask them about it to be sure. Good chance they thought the hover elements on the chart are enough to make clear that interaction is possible. If you have doubts and think it isn’t clear enough, do some tests with people around you. Here's my advice: For a web application I would recommend to stick with the ...
Facebook, tumblr, soup.io and Gerrit and surely several other services use "j" and "k" keys for moving down / up.
Only top voted, non community-wiki answers of a minimum length are eligible