NATURAL INPUT FOR SPREADSHEET ACTIONS

[0001] Many people utilize spreadsheets to interact with data. Generally, users interact with spreadsheets through input devices, such as mice, touch screens, graphical user interfaces and keyboards. Sometimes this interaction can be frustrating. For example, interacting with and manipulating a large spreadsheet on a small screen device (e.g. cell phone, tablet) can be difficult and tedious.

[0002] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

[0003] Different gestures and actions are used to interact with spreadsheets. The gestures are used in manipulating the spreadsheet and performing other actions in the spreadsheet. For example, gestures may be used to move within the spreadsheet, select data, filter, sort, drill down/up, zoom, split rows/columns, perform undo/redo actions, and the like. Sensors that are associated with a device may also be used in interacting with spreadsheets. For example, an accelerometer may be used for moving and performing operations within the spreadsheet.

[0017] Referring now to the drawings, in which like numerals represent like elements, various embodiments will be described. In particular, FIG. 1 and the corresponding discussion are intended to provide a brief, general description of a suitable computing environment in which embodiments may be implemented.

[0018] Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Other computer system configurations may also be used, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. Distributed computing environments may also be used where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0019] Referring now to FIG. 1, an illustrative computer architecture for a computer 100 utilized in the various embodiments will be described. The computer architecture shown in FIG. 1 may be configured as a mobile or a desktop computer and includes a central processing unit 5 (“CPU”), a system memory 7, including a random access memory 9 (“RAM”) and a read-only memory (“ROM”) 10, and a system bus 12 that couples the memory to the central processing unit (“CPU”) 5. According to embodiments, computer 100 is a handheld computing device such as a mobile phone, tablet, laptop, net book, PDA, and the like.

[0020] A basic input/output system containing the basic routines that help to transfer information between elements within the computer, such as during startup, is stored in the ROM 10. The computer 100 further includes a mass storage device 14 for storing an operating system 16, application program(s) 24, and other program modules 25, and gesture manager 26 which will be described in greater detail below.

[0021] The mass storage device 14 is connected to the CPU 5 through a mass storage controller (not shown) connected to the bus 12. The mass storage device 14 and its associated computer-readable media provide non-volatile storage for the computer 100. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, the computer-readable media can be any available physical media that can be accessed by the computer 100.

[0022] By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes physical volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, Erasable Programmable Read Only Memory (“EPROM”), Electrically Erasable Programmable Read Only Memory (“EEPROM”), flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer 100.

[0023] According to various embodiments, computer 100 may operate in a networked environment using logical connections to remote computers through a network 18, such as the Internet. The computer 100 may connect to the network 18 through a network interface unit 20 connected to the bus 12. The network connection may be wireless and/or wired. The network interface unit 20 may also be utilized to connect to other types of networks and remote computer systems. The computer 100 may also include an input/output controller 22 for receiving and processing input from a number of other devices, including a display/touch input device 28. The touch input device may utilize any technology that allows touch input to be recognized at a time. For example, the technologies may include, but are not limited to: heat, finger pressure, high capture rate cameras, infrared light, optic capture, tuned electromagnetic induction, ultrasonic receivers, transducer microphones, laser rangefinders, shadow capture, and the like. An exemplary touch input device is shown in FIG. 2. The touch input device 28 may also be separate from the display. The input/output controller 22 may also provide output to one or more display screens, a printer, or other type of output device.

[0024] Computer 100 may also include one or more sensors 21. According to an embodiment, computer 100 includes an accelerometer for sensing acceleration of the computer or a portion of the computer. For example, the accelerometer may detect movement of display 28. The accelerometer may be a single axis or multi-axis accelerometer that is used to sense orientation, acceleration, vibration, and other types of actions that may be sensed by an accelerometer. Other sensors may also be included, such as location sensors (i.e. GPS), audio sensors, infrared sensors, other types of tilt sensors, and the like. Information received by sensor 21 may be used to interact with an application program. For example, when a user moves the computing device, different parts of a spreadsheet may be shown in response to the movement.

[0025] As mentioned briefly above, a number of program modules and data files may be stored in the mass storage device 14 and RAM 9 of the computer 100, including an operating system 16 suitable for controlling the operation of a networked personal computer, such as the WINDOWS® 7® operating system from MICROSOFT CORPORATION of Redmond, Wash. According to one embodiment, the operating system is configured to include support for touch input device 23. According to another embodiment, a gesture manager 26 may be utilized to process some/all of the touch input that is received from touch input device 23.

[0026] The mass storage device 14 and RAM 9 may also store one or more program modules. In particular, the mass storage device 14 and the RAM 9 may store one or more application programs 24, such as a spreadsheet application. According to an embodiment, the spreadsheet application is the MICROSOFT EXCEL spreadsheet application. Other spreadsheet applications may also be used.

[0027] In conjunction with the operation of the application, gesture manager 26 is configured to detect gestures that are received by the touch input device 28. Generally, gesture manager 26 is configured to sense when a gesture is received that is related to performing an operation in conjunction with an application program, such as a spreadsheet application. Different types of gestures may be received. For example, a swipe gesture, a cut/paste gesture, an insert gesture, a vortex gesture, a grip gesture, a chart gesture, a trend line gesture, a comment gesture, a zoom gesture, a sort gesture, an undo/redo gesture, and the like may be received.

[0028] Gesture manager 26 is also configured to receive input from one or more sensors. The information received from the sensor(s) may be used alone and/or in combination with a received gesture. For example, tilting the device may cause a spreadsheet to scroll/pan in the tilted direction. Shaking the device may be used to clear a filter, reset a state, perform an undo and the like. Jerking the device may cause an acceleration in scrolling or a jump in the scroll position. Tilting the device steeply (i.e. greater then 30 degrees or some other predetermined angle) may cause the spreadsheet objects contained within spreadsheet 23 to appear as if they are spilling to the top of the spreadsheet thereby allowing the user to select one of the spreadsheet objects. Upon selection, the spreadsheet objects can return to their original location and the view may center on the chosen object. The gestures and sensor information may be used to change a display of information, activate/deactivate functions, and/or perform some other type of operation associated with application 24 or some other function and/or program. Additional details regarding the gestures and sensor information will be provided below.

[0029] FIG. 2 illustrates an exemplary touch input system. Touch input system 200 as illustrated comprises a touch panel 202 that has several sensors 204 integrated therein. According to one embodiment, the sensors 204 are Infrared (IR) sensors. The touch input system 200 is configured to detect objects that either in contact with the touchable surface 206 or are close to but not in actual contact with (“adjacent”) touchable surface 206. The objects that are sensed may be many different types of objects such as finger, hands, or other physical objects. Infrared sensors 204 are distributed throughout touch panel 202 and are disposed parallel to touchable surface 206. One or more of the infrared sensors 204 may detect infrared radiation reflected from objects, such as hand 208, as indicated by the arrow. Although the term “above” is used in this description, it should be understood that the orientation of the touch panel system is irrelevant. As shown in FIG. 2, touchable surface 206 is horizontal, but in a different embodiment generated by rotating system 200 clockwise by 90 degrees, touchable surface 206 could be vertical. In that embodiment, the objects from which reflected IR radiation is detected are to the side of touchable surface 206. The term “above” is intended to be applicable to all such orientations. Touchable surface 206 may also be changed to other orientations.

[0030] Touch panel 202 may comprise filters 212 that absorbs visible light and transmits infrared radiation and are located between touchable surface 206 and IR sensors 204 in order to shield IR sensors 204 from visible light incident on touchable surface 206 in the case where IR sensors 204 are sensitive to a broader range of wavelengths of light other than purely infrared wavelengths.

[0031] Touch panel 202 may comprise a display that is configured to display images that are viewable via touchable surface 206. For example, the displayed image may be images relating to an application, such as a spreadsheet. The display may be, for example, an LCD, an organic light emitting diode (OLED) display, a flexible display such as electronic paper, or any other suitable display in which an IR sensor can be integrated.

[0032] System 200 may comprise a backlight 216 for the display. Backlight 216 may comprise at least one IR source 218 that is configured to illuminate objects in contact with or adjacent to touchable surface 206 with infrared radiation through touchable surface 206, as indicated by the arrows. IR sensors 204 are sensitive to radiation incident from above, so IR radiation traveling directly from backlight 216 to IR sensors 204 is not detected.

[0033] The output of sensors 204 may be processed by gesture manager 26 and/or functionality included within an operating system or some other application to detect when a physical object (e.g., a hand, a bottle, a glass, a finger, a hat, etc.) has come into physical contact with a portion of the touch input surface 206 and/or a physical object is in close proximity to the surface. For example, sensors 204 can detect when a portion of hand 208, such as one or more fingers, has come in contact with or is near to the touch input display surface 206. Additional sensors can be embedded in the touch input display surface 206 and can include for example, accelerometers, pressure sensors, temperature sensors, image scanners, barcode scanners, etc., to detect multiple simultaneous inputs.

[0034] When the sensors 204 are IR sensors, the IR radiation reflected from the objects may be reflected from a user's hands, fingers, reflective ink patterns on the objects, metal designs on the objects or any other suitable reflector. Fingers reflect enough of the near IR to detect that a finger or hand is located at a particular location on or adjacent the touchable surface. A higher resolution of IR sensors may be used to scan objects in order to achieve higher resolution.

[0035] Sensors 204 can be included (e.g., embedded) in a plurality of locations. The density of sensors 204 can be sufficient such that contact across the entirety of touch input surface 206 can be detected. Sensors 204 are configured to sample the surface of touch input display surface 206 at specified intervals, such as, for example, 1 ms, 5 ms, etc. for detected contact and/or near contact. The sensor data received from sensors 204 changes between sampling intervals as detected objects move on the touch surface; detected objects are no longer within range of detection; and when new objects come in range of detection. For example, gesture manager 26 can determine that contact was first detected at a first location and then contact was subsequently moved to other locations. In response, the gesture manager 26 may determine when a gesture is received and what type of gesture is received.

[0036] FIG. 2 provides just one example of a touch input system. In other exemplary touch systems, the backlight may not comprise any IR sources and the surface 206 may include a frontlight which comprises at least one IR source. In such an example, the touchable surface 206 of the system is a surface of the frontlight. The frontlight may comprise a light guide, so that IR radiation emitted from IR source travels through the light guide and is directed towards touchable surface and any objects in contact with or adjacent to it. In other touch panel systems, both the backlight and frontlight may comprise IR sources. In yet other touch panel systems, there is no backlight and the frontlight comprises both IR sources and visible light sources. In further examples, the system may not comprise a frontlight or a backlight, but instead the IR sources may be integrated within the touch panel. In an implementation, the touch input system 200 may comprise an OLED display which comprises IR OLED emitters and IR-sensitive organic photosensors (which may comprise reverse-biased OLEDs). In some touch systems, a display may not be included. Even if the touch system comprises one or more components or elements of a display, the touch system may be configured to not display images. For example, this may be the case when the touch input tablet is separate from a display. Other examples include a touchpad, a gesture pad, and similar non-display devices and components.

[0037] For some applications, it may be desirable to detect an object only if it is in actual contact with the touchable surface of the touch panel system. For example, according to one embodiment, a gesture may not be recognized when the gesture is not performed touching the surface. Similarly, a gesture may be recognized when performed above the surface. The IR source of the touch input system may be turned on only if the touchable surface is touched. Alternatively, the IR source may be turned on regardless of whether the touchable surface is touched, and detection of whether actual contact between the touchable surface and the object occurred is processed along with the output of the IR sensor. Actual contact between the touchable surface and the object may be detected by any suitable means, including, for example, by a vibration sensor or microphone coupled to the touch panel. A non-exhaustive list of examples for sensors to detect contact includes pressure-based mechanisms, micro-machined accelerometers, piezoelectric devices, capacitive sensors, resistive sensors, inductive sensors, laser vibrometers, and LED vibrometers.

[0038] FIG. 3 shows a system for using gestures and sensor information to interact with an application. As illustrated, system 300 includes spreadsheet application 302, callback code 312, sensor(s) 304, gesture manager 26, spreadsheet 310 and touch input device/display 340. According to an embodiment, the functionality of system 300 is included within a mobile computing device.

[0039] In order to facilitate communication with the gesture manager 26, one or more callback routines, illustrated in FIG. 3 as callback code 312 may be implemented. According to one embodiment, gesture manager 26 is configured to receive input from a touch-sensitive input device 340 and sensor(s) 304. For example, gesture manager 26 may provide an indication to application 302 when a user's hand (i.e. hand 312) or some other object performs a gesture that is used in interacting with spreadsheet 310. Sensor information may also be received by gesture manager 26 to interact with spreadsheet 310. For example, a user may tilt or tap the side of the computing device to scroll the display of spreadsheet 310.

[0040] Gesture manager 26 is configured to recognize many different types of gestures. Some of the gestures may be context dependent, be specific to an application and/or be used within many different types of applications. For example, gestures may be used to interact with a spreadsheet 310 that is associated with a spreadsheet application 302. Gestures may be received in many different locations relating to touch input device/display 340. For example, a gesture may be received within a display of spreadsheet 310, within a gesture box 314 and/or at some other location on display 340.

[0041] Gestures may be predetermined and/or specified in different ways. For example, some gestures may be predetermined to be associated with a particular action whereas other gestures may be associated with one or more actions by a user. For instance, a user could specify that when a particular gesture is received then one or more spreadsheet operations are to occur. The operation may be specified in many different ways. For example, programming code may be used, a macro may be created, a formula may be configured, and the like.

[0042] There are many different examples of actions that may occur. For example, certain gestures when recognized may reverse the polarity of conditional formatting (i.e. change from high-to-low to low-to-high formatting). Performing a gesture may change formatting of the data (i.e high values were originally formatted to be green and now are red after the user performs a certain gesture). One or more gestures may result in reversing the orientation of charts. For example, a chart was originally displaying data from January to March and after a gesture is performed, the chart reverses and display data from March to January. One or more gestures may expose more information. For example, suppose that a chart currently is displaying data between January 2009 to March 2009. When a gesture is received, the display of the chart shifts and shows data from February 2009 to June 2009. Exemplary gestures and interactions with a spreadsheet are described below with reference to FIGS. 4-12.

[0043] Sensor information received by gesture manager 26 may be used to interact with spreadsheet 310. For example, the relative position of the computing device/display may be used to determine the portion of the spreadsheet to display. For example, moving the device to the left may scroll/pan the display of spreadsheet to the left whereas moving the device to the right may scroll/pan the display of the spreadsheet to the right. The scrolling/panning of the display may be a combination of a horizontal and vertical scrolling/panning. For example, moving the device diagonally may result in an equal amount of horizontal and vertical scroll/pan. The terms “scroll” and “pan” as used herein may be used interchangeably. Moving the device upwards or downwards may also affect the display of spreadsheet 310. For example, moving the device down may perform a zoom out operation such that more of the spreadsheet is displayed whereas moving the device in an upwards direction may be a zoom in operation such that a more detailed view of the spreadsheet is displayed. According to an embodiment, a zoom out operation displays a thumbnail view for each sheet of the spreadsheet workbook when the zoom exceeds a predetermined zoom level. Moving the spreadsheet upwards/downwards may also cause drilling operations to be performed on the spreadsheet. For example, moving the device in an upwards direction may perform a drilling up operation to less detail in the spreadsheet whereas moving the device in a downwards may perform a drilling down operation to show more detail.

[0044] The speed of the movement of the spreadsheet/computing device may also be used in determining a speed of the scrolling and/or zooming. For example, a sudden movement in a direction may increase the speed of the scrolling and/or zooming action. According to an embodiment, scrolling may slow/stop when it comes near a predetermined location (“speed bump”) within the spreadsheet. The location of the speed bumps may be placed at different locations within the spreadsheet. They may be automatically determined and/or manually located. A speed bump may be automatically placed whenever there is a gap in the data within the spreadsheet. For example, suppose that a spreadsheet has content from rows 1-3 and 10-20 and no content from rows 4-10. A speed bump may be placed at row 4 (318). When the user pans to row 4, the panning stops as if it hit the end of the spreadsheet. The panning may also slow as it nears the end of the data before the speed bump. To continue panning, the user just performs the panning operation again. Speed bumps may also be placed periodically throughout the grid of the spreadsheet (i.e. every 100 rows, 200 rows, 1000 rows, and the like). Different actions may also be associated with the speed bumps. For example, the movement of the spreadsheet may stop when it hits a speed bump, slow when it hits a speed bump and then speed up as it moves away from the speed bump, and the like.

[0045] The orientation of the spreadsheet/computing device may also be monitored. Tilting the display of the spreadsheet causes the display of the spreadsheet to scroll/pan in the tilted direction. An amount of tilt and/or a speed of the tilt may also be used to perform operations. For example, tilting the device steeply in the vertical direction may cause all the spreadsheet objects within spreadsheet 310 to appear as if they are spilling to the top of the spreadsheet (See FIG. 12). The titling may also be interpreted to navigate different data within an object. For example, tilting the device may navigate across the data series in a chart.

[0046] Rotating the device may be used to change views that are associated with the spreadsheet. For example, rotating the display of the spreadsheet may cause the view to change from a sheets view to a Named Object View that displays each object that is associated with spreadsheet 310. Similarly, when a user is viewing an object, the view may be changed based on the object. For example, when a user is viewing a pie chart, rotating the spreadsheet may cause the view to change to some other type of chart (e.g. bar chart).

[0047] Shaking the device may also be determined to perform operations relating to the spreadsheet. For example, shaking the device may be used to clear filters that are set on a table or pivot table within a spreadsheet, reset a state, perform and undo operation, and the like.

[0048] FIGS. 4-12 illustrate exemplary gestures and actions to interact with a spreadsheet.

[0049] FIG. 4 shows a zooming gesture within a spreadsheet. As illustrated, FIG. 4 shows a spreadsheet view 410 before zooming and a zoomed view 420 after performing a zoom out operation. According to an embodiment, a zoom gesture is detected when a user spreads two of their fingers apart as indicated by gesture 445. A zoom in gesture may be detected when a user closes two of their fingers. The zoomed out view 420 may be shown when a user zooms out beyond a certain point (i.e. <5%) and/or based on a speed of the movement between the two fingers of the gesture. For example, a very quick separation of the fingers may cause the thumbnail zoomed view 420 to be shown. As illustrated, zoomed view 420 is a thumbnail view of each sheet within the spreadsheet workbook. Other zoomed views may also be provided. For example, before zooming to the thumbnail view of each sheet within the spreadsheet, a Named Object View of the current may be displayed at a predetermined zoom level (e.g. at a zoom level 15-20%).

[0050] FIG. 5 illustrates the use of a gesture box. As illustrated, FIG. 5 illustrates display 530 that shows spreadsheet 540, selection 512, and gesture box 518. According to an embodiment, the gesture box 518 is drawn near a corner of the display. A gesture 516 may be drawn into the gesture box 518. Each gesture is associated with a particular command. For example, some exemplary commands are illustrated by gesture box commands 520. For example: drawing S could save the spreadsheet, drawing B could bold text, drawing a + sign could write a sum formula drawing a − sign could write a subtraction formula, drawing an up arrow could sort upwards, drawing a down arrow could sort downwards, drawing a circle could write an average formula. Other gesture commands may be used within gesture box 518. For example, a user could create custom gestures and/or modify existing gestures. These gestures could be recorded and associated with programming code, commands, and/or macros.

[0051] As illustrated, a user has created a selection 512 of the numbers 10, 12 and 5 with gesture 514 and then draws a “+” symbol within gesture box 518. In response to drawing the + symbol, a sum formula is written to grid location A4 that causes the value 27 to be displayed. A user may draw any gesture command into the box that was appropriate for selection 512. For example, a user may draw a circle within gesture box 518 that writes an average formula that would base 9 to be displayed at location A4.

[0052] While gesture box 518 is shown at the bottom left location of display 530, the gesture box may be displayed at other locations. For example, gesture box 518 may be displayed on top of spreadsheet 540, or at any other location on display 530.

[0053] FIG. 6 shows a karate chop gesture. As illustrated, FIG. 6 shows spreadsheet 610 receiving a horizontal karate type gesture 612 and a vertical karate type gesture 614. The karate type gesture is used to insert a row/column at a particular location within a spreadsheet. The karate chop gesture is detected when a karate chop motion is performed. For example, the edge of a user's hand may be detected or an edge of another physical object with an edge having similar characteristics to a user's hand may be detected to receive the karate type gesture. When a horizontal karate chop gesture 612 is received a new row is inserted at the location of the karate chop gesture. When a vertical karate chop gesture 614 is received a new column is inserted at the location of the karate chop gesture. In the current example, a new row is inserted between rows 2 and 3 and a new column is inserted after column 6 (see spreadsheet 620). According to another embodiment, the karate chop gesture is associated with other commands. For example, the karate chop gesture could trigger the automatic conversion of text-to-columns.

[0054] FIG. 7 shows a user selecting data and then drawing a chart gesture to change a view of the selected data. As illustrated, FIG. 7 shows a spreadsheet 710 comprising data 716. In the current example, a user has selected data 716 and then draws a chart gesture to create a display of a chart to represent the selected data.

[0055] Chart gesture 722 shows the user drawing a circle that represents a pie chart. When the user has completed chart gesture 722, a pie chart 712 is displayed. The chart may be displayed at different locations. For example, the chart may replace the selected data, the chart may be placed near the selected data or the chart may be placed at a user designated position. The chart may also be placed on another sheet of the spreadsheet workbook.

[0056] Chart gesture 724 shows a user drawing a chart gesture that is in the form of a line that creates a bar chart 714 for selected data 716. According to an embodiment, more than one type of chart may be displayed with selected data.

[0057] Chart gesture 726 shows a user drawing a chart gesture that is in the form of a semi-circle line that creates a scatter chart 718 for selected data 716. According to an embodiment, more than one type of chart may be displayed with selected data.

[0058] FIG. 8 shows a user drawing a chart gesture that is recognized as a trend line gesture on a chart. As illustrated, FIG. 8 shows a bar chart 810 bar chart 814 with a trend line, scatter chart 820 and scatter chart 824 with a logarithmic trend line. In the example of the bar chart, a user draws a trend line gesture 812 that is near the edges of the displayed chart elements data to create a display of a trend line with the bar chart (814). In the example of the scatter chart 820, a user draws a trend line gesture 822 that is a line near the middle of the data to create a display of a trend line with the scatter data 824.

[0059] FIG. 9 illustrates a comment gesture. A comment gesture creates a comment location near the beginning of the comment gesture. For example, in FIG. 9, a comment is located near the top of the last bar chart (920). The comment gesture is a line followed by a portion of a circle as illustrated by display 910. While the comment gesture is shown being performed on a chart, the comment gesture may be located anywhere within a display and be associated with different types of elements. For example, a comment gesture may be associated with a single cell, a group of selected cells, a chart, a table, or some other object. A comment box is displayed in response to receiving the comment gesture that allows a user to enter a comment.

[0060] FIG. 10 shows a vortex effect in response to an action being performed on data. As illustrated, display 1010 shows a user cutting selected data. In response to the cut option being selected, an animation that looks like a “vortex” is displayed creating the illusion that the content that is cut is getting sucked into the finger (1012). According to an embodiment, content disappears to the point where the finger last contacted the screen.

[0061] Display 1020 shows a user pasting data. On a paste command, the content is drawn outward from the finger point of contact (1014) and the vortex animation creates the illusion that the pasted content is coming out of the finger.

[0062] FIG. 11 illustrates a display and interaction with a grip user interface element. A grip user interface element 1112 is displayed on top of a document, such as a spreadsheet 1110. According to an embodiment, the grip user interface element 1112 is placed on the side of the screen of the non-dominant hand (e.g. for right handed users on the left side and for left handed users on the right side). When the grip 1112 is not held down, a slide action by the dominant hand 1114 is interpreted as a pan.

[0063] When the grip is held down (e.g. by the non-dominant hand) as illustrated in display 1120, any slide action by the other hand 1124 is interpreted as selecting cells. Different effects may be applied with the display of grip 1112. For example, the grid of the spreadsheet can visually “bend” at the point of contact with the grip to provide visual feedback that the grip is being held down.

[0064] FIG. 12 shows spreadsheet objects being displayed based on a movement of the device.

[0065] Display 1220 shows spreadsheet objects spilling off of the display. For example, tilting the computing device in the vertical direction may cause the spreadsheet objects within spreadsheet 1210 to appear as if they are spilling to the top of the spreadsheet as shown in display 1220. Tilting the device horizontally may cause the spreadsheet objects to spill to the side of the device. Upon selection of an object, the spreadsheet is displayed with the view centered on the chosen object. This provides a faster way to navigate objects on a sheet.

[0066] Display 1230 shows spreadsheet objects being gravity sorted. For example, the user may tilt the computing device from landscape to portrait mode, and then shake the device. According to an embodiment, the combined actions sort the data so the largest items appear on the bottom. The data may be numbers, chart data, spreadsheet objects and the like. For example, when applied to a bar chart, it would appear that the heaviest bars of the chart are falling to the bottom.

[0067] Referring now to FIG. 13, an illustrative process 1300 for using gestures and sensors to interact with a spreadsheet will be described. When reading the discussion of the routines presented herein, it should be appreciated that the logical operations of various embodiments are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance requirements of the computing system implementing the invention. Accordingly, the logical operations illustrated and making up the embodiments described herein are referred to variously as operations, structural devices, acts or modules. These operations, structural devices, acts and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof.

[0068] After a start operation, the process flows to operation 1310, where a gesture is received and/or sensor information is received. The gesture may be any of the gestures described herein or other recognized gestures, such as a karate chop gesture, a grip gesture, a shape gesture, a trend line gesture, a comment gesture, a zoom gesture, a sort gesture, and the like may be received. According to one embodiment, the user places at least a portion of their hand (e.g. one or more fingers) on the touch surface. Additionally, according to some embodiments, the user may place their hand near the surface of the touch surface but not on the touch surface. The sensor information may relate to many different types of sensor information that may be used in interacting with a display. For example, the sensor information may relate to accelerometer data that may be used in determining an orientation of the computing device and a speed of the device,

[0069] Moving to operation 1320, the action to perform is determined. According to an embodiment, the action relates to interacting with a spreadsheet and comprises actions such as panning, tilting, sorting, zooming, drilling, and the like. While the actions described relate to interaction with spreadsheets, other applications may be utilized with the gestures described.

[0070] Flowing to operation 1330, the determined action is performed. Generally, the action relates to updating a spreadsheet. For example, a chart may be created, a trendline may be added, data may be sorted, summed, or some other operation may be performed on data, and the like.

[0071] Transitioning to operation 1440, the display is updated. The display is updated in response to the action received gesture/sensor information that is received.

[0072] The process then flows to an end operation and returns to processing other actions.

[0073] The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.