nos launcher lcd screen made in china

This guide will give you full insight into how to use all the features of Automatic LCDs 2. You will find out what are the commands, what are the arguments of the commands and how to use them. It also contains full list of all commands with detailed description along with examples of use.

Open your programmable block, click Edit, click Browse Workshop, select Automatic LCDs 2, click OK, Check code, Click Ok. Done. Your script is now updated.

This is very useful if you connect ships to your station or ship and you don"t want to see blocks of the connected ships on station LCDs. You can also use this script on multiple ships that connect together without worries that they will conflict once connected.

Script now only updates LCDs which are part of the same grid as programmable block. If you would like to change this please take look at What is LCD_TAG? section to learn how to change LCD_TAG.

LCDs that are connected using rotors, pistons or connectors are not updating?By default the script only updates LCDs that are part of the same grid as programmable block.

LCD_TAG is used to tell the script which LCDs are managed by the script. As all of you know the script looks for LCDs that have [LCD] in their name by default.

You can however change this to whatever you like. You can tell the script to manage LCDs in certain group or even tell it to manage all LCDs regardless of name.

How to change the LCD_TAG?You can change the LCD_TAG by editing the Custom Data of programmable block that runs the script. Let"s explain it by example:

Note: If you already use Custom Data to display stuff on Programmable block screens (check "How to use with cockpits?" section of the guide to understand how):

How to tell the script to manage all LCDs regardless of name?LCD_TAG follows the same name filtering rules as commands. So you can set the Custom Data to:

You also can"t change the LCD_TAG during run. You need to recompile the script every time you change the LCD_TAG otherwise the script will still look for old tag.

It is now possible to join multiple LCDs together so they will look and work like single panel. Because of the limitations of text alignment it is only possible to join LCDs up and down. Not left to right. So the widest LCD you can have is Wide LCD. But you can have many of them under each other to form single big one.

NUMBER is position of LCD in array of LCDs. It doesn"t matter what number you choose. They just need to go one after another. So the topmost LCD will have the lowest number. For example 1. LCD under it will have 2, etc.

You can use this script on cockpit screens as well as screens of other blocks. In order to do that you have to mark the cockpit (or other block) with the LCD_TAG as you did with LCDs. So by default you add [LCD] to the name of the cockpit in order for the cockpit to be recognized by the script.

As soon as you do that the first screen on the cockpit will be controlled by the Automatic LCDs 2 and should display the usual message that you should write commands to custom data of the panel. If you need only this screen, you can write commands to Custom Data of the cockpit just as you do with LCDs.

In order to use other screens you have to tell the script which screen you want to write to. Here is example of how the Custom Data of cockpit can look like:

Where is the index of the screen you want to write to. 0 is the first screen, 1 is the second screen, etc. The "AutoLCD" part just needs to be there.

Easy way to know the index of the screen is when you look at the control panel of the cockpit, find the list of the LCD panels and pick one. For example "Keyboard" screen is 4th in the list of the LCD panels which means its index is 3 (because first one is 0). So if you would want to write only to the Keyboard screen your custom data would look like this:

You can use this on any block that has LCD panel screens. Script will not touch screens that you haven"t specified so you can use this with other scripts too. Read "Compatibility with other scripts" if you want to know how Automatic LCDs can share Custom Data with other scripts.

Script now only updates LCDs which are part of the same gridThis means that LCDs which are connected using connectors, pistons or rotors will not be updated to prevent conflicts between docked ships. This does not apply when ships are connected using merge block because in that case they behave like single ship in game.

LCDs are updating much slower when more ships are docked using merge blockIf there are more ships using this script docked together using merge block then the programmable blocks will not split the work efficently automatically.

I recommend using different LCD_TAG for each ship and station. Look at Tips and Tricks section of this guide to learn how to do that. This will ensure that programmable blocks always update only LCDs on the ship/station they are intended for.

LCDs are showing items, power, cargo, etc of all docked shipsThis will happen if you use no arguments to commands or if you use * or if you use same names for groups / blocks on both ships. Make sure you read Same ship blocks filtering section to learn how to filter only blocks of the same ship.

reactor, thruster, container, refinery, assembler, solar, battery, beacon, antenna, gyro, sensor, connector, spotlight, interlight, landgear, program, timer, rotor, piston, projector, merge, sound, collector, door, spheregrav, gravgen, drill, grinder, welder, gatlingturret, missileturret, interiorturret, gatlinggun, reloadlauncher, launcher, mass, warhead, light, control, cockpit, medi, remote, button, camera, detector, laserantenna, airvent, oxygenerator, sorter, oxyfarm, cryo, jumpdrive, tank (both hydrogen and oxygen), parachute, windturbine, hydrogenengine

Due to game limitations some blocks do NOT automatically update the details text until you look at them in control panel. This is VERY important as you always need to look at the block in control panel if you want the LCD to show updated text. This does not apply to all blocks!

Note: If you would like to display only leaking air vents you can use Working command and filter only LCDs that show LEAK using filtering described in Working command.

This is very useful when using different mods / scripts that write something to Custom Data of block and you would like to append it to your Automatic LCDs displays.

This is very useful when using different mods / scripts that type something on LCD and you would like to append it to your Automatic LCDs displays. This way you can have one LCD hidden that will be used by your mod / script and use TextLCD command to read that text and write it to one of the Automatic LCDs. Example: TextLCD {Other LCD} will append contents of first LCD named Other LCD.

You can also add this to button panel and setup action on button to Run the programmable block with argument. It needs to be the same programmable block that runs the script that shows the text on the screen on that particular LCD.

If you use custom font scroll down to the bottom of script, then scroll a bit up until you find AddCharsSize lines. Monospace font name and size definition is above those.

LCD clear functionWhen you Run the programmable block with argument "clear" (without quotes) it will clear all LCDs. You can use this to turn off your LCDs without having to actually turn them off where they would say "OFFLINE".

LCDs boot screensUnfortunately there is no easy way to find out that you turned off/on your ship so the script doesn"t automatically display boot screens after turn the power sources off and on. You can however use the LCD clear function to reset the LCDs when you turn on your ship/station. There is also special "boot" argument to start the boot sequence whenever you need it. Just Run the programmable block with "boot" (without quotes) as argument.

If you are a bit more advanced, you can customize the boot screens:To customize the boot texts (except for progress bar part) open the script in programmable block and scroll down a bit, where you will find this:

Automatic LCDs 2 is not a mod so you don"t need to do anything in dedicated server setup to use it except for having enabled in-game scripts in your world.

How to use LCDs that are connected using rotors, pistons or connectors?By default the script only updates LCDs that are part of the same grid as programmable block. First, I do recommend reading about "Same grid filtering" in separate section of this guide.

Keen has added MyIni format that scripters can use to parse Custom Data. This was added explicitly to make life easier for scripters when they need to use Custom Data and share it with other scripts. This was written by Malware (the creator of MDK framework for Space Engineers in-game scripting and father of Programmable Block) and I"ve been discussing with him how to make it compatible with Automatic LCDs without people having to learn new syntax so he came up with great solution.

If people also want to write Automatic LCDs commands to the same block where the Custom Data is already used by script that uses MyIni format then they can simply add 3 dashes on its own line and continue with Automatic LCDs commands like this:

Anything under the --- is ignored by the MyIni parser that other scripts use. Anything before the --- is completely ignored by the Automatic LCDs so this way Automatic LCDs can share Custom Data with other scripts and coexist peacefully :)

NOTE: Some scripts overwrite the Custom Data and if you already have some Automatic LCDs commands there they will remove them. If those scripts support the MyIni format then you can write your commands like this to make them not remove the commands (or set them up first and then use the format like explained above):

You can have 100 scripts running on your server with 1.0 sim speed. If you would like to see the performance test it starts at 1:56 of the showcase video which is the first one in the screenshots on the main script page or here:

Programmable Block Edit button is greyed out. What should I do?You need to enable in-game scripts in Advanced World settings. You can find them on Load screen, when you select your save and click Edit Settings button, then Advanced button and scroll down you will find lots of check boxes, one of them says In-game scripts - make sure it is enabled.

*** Check your ownership ***Always make sure that the programmable block and LCDs have the same ownership as the blocks you want to show on the LCDs. I highly recommend you own all the blocks unless you know how ownership works. Just open the control panel, select one of the blocks on your ship, press CTRL+A and change the ownership on the right side to "Me".

I can"t stop it. Its techinically impossible because of how the script limiter works. The script is independent on number of screens or number of commands .. it always uses the same number of instructions and instead slows down the updates of the screens.

1. If your LCDs are on separate grid (behind rotor, piston, connector) they will not be updated. Read LCDs that are connected using rotors, pistons or connectors are not updating? section of Troubleshooting section of the guide.

LCDs that are connected using rotors, pistons or connectors are not updating?By default the script only updates LCDs that are part of the same grid as programmable block. First, I do recommend reading about "Same grid filtering" in separate section of this guide.

If some of your LCDs are sometimes offline:it"s probably a game bug and it"s happening to more people. Someone said that loading game, returning to main menu and loading again helps.

If you can"t see more than one screen at time and if you turn off a screen, the other one starts workingIt"s a game bug. Restart game/server. Try answers for offline bug above.

Does your LCD just say ONLINE instead of showing things?Make sure that you named your LCD so it contains [LCD] . If you did, you are most probably using german client which has problems with [] characters that you type in game. You can use copy-paste to overcome it or simply use alternate built-in tag I made for you !LCD!

It"s just blank screen?Your command is wrong or there is simply nothing to show. Check your command syntax in full guide, try examples. Make sure that there is nothing in front of the command in LCD Public Title (game sometimes likes to hide the "Public title" text). Always press Home before entering command to make sure there is no text at the beginning of LCD Public Title that you don"t want to have there.

Programmable block reports "Index out of bounds".Make sure that you updated the script to latest version with all the fixes. Check that script has permissions to write to LCDs!

I need to see what assembler/refinery is producing like on your screenshotIt is not possible to find out what assembler or refinery is doing from the script. What you see on screenshot are names of assemblers and refineries. I use scripts Crafting Component Quotas and Selective Refining. Crafting Components Quotas can rename your assemblers like you see on screenshot.

Nitrous Oxide Systems is proud to present the Launcher. It combines all the functions a Nitrous racer could ever want into a single, easy–to–use controller. This handy device can be programmed to independently control up to 4 stages of Nitrous.

Information such as mission log, friendlist, level, exprerience points, money and weapon proficiency stats can be displayed on the LCD panel or smartphone application.

Allows you to set a custom screen resolution to a value other than what is offered in the Video Options menu. H is the horizontal resolution. V is the verical resolution (for example, "setres 1024x768").

Smith also said the Marines had successfully tested a new shorter-range anti-ship weapon, the Naval Strike Missile, from a ground launcher and would conduct another test in June. He said if that test was successful, the Marines intended to order 36 of these missiles in 2022. The U.S. Army is also testing a new long-range, land-based missile that can target warships. This missile would have been prohibited under the INF treaty.

Current and retired U.S. Navy officers have been urging the Pentagon to equip American warships with longer-range anti-ship missiles that would allow them to compete with the latest, heavily armed Chinese cruisers, destroyers and frigates. Lockheed has said it successfully test-fired one of the new Long Range Anti-Ship Missiles from the type of launcher used on U.S. and allied warships.

This application claims priority to U.S. Provisional Patent Application Nos. 60/937,993, “Portable Multifunction Device,” filed Jun. 29, 2007; 60/946,715, “Portable Electronic Device, Method, And Graphical User Interface For Displaying Structured Electronic Documents,” filed Jun. 27, 2007; 60/879,469, “Portable Multifunction Device,” filed Jan. 8, 2007; 60/879,253, “Portable Multifunction Device,” filed Jan. 7, 2007; and 60/824,769, “Portable Multifunction Device,” filed Sep. 6, 2006. All of these applications are incorporated by referenced herein in their entirety.

This application is related to the following applications: (1) U.S. patent application Ser. No. 10/188,182, “Touch Pad For Handheld Device,” filed Jul. 1, 2002; (2) U.S. patent application Ser. No. 10/722,948, “Touch Pad For Handheld Device,” filed Nov. 25, 2003; (3) U.S. patent application Ser. No. 10/643,256, “Movable Touch Pad With Added Functionality,” filed Aug. 18, 2003; (4) U.S. patent application Ser. No. 10/654,108, “Ambidextrous Mouse,” filed Sep. 2, 2003; (5) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (6) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (7) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices” filed Jan. 18, 2005; (8) U.S. patent application Ser. No. 11/057,050, “Display Actuator,” filed Feb. 11, 2005; (9) U.S. Provisional Patent Application No. 60/658,777, “Multi-Functional Hand-Held Device,” filed Mar. 4, 2005; (10) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006; and (11) U.S. Provisional Patent Application No. 60/947,155, “Portable Electronic Device, Method, And Graphical User Interface For Displaying Inline Multimedia Content”, filed Jun. 29, 2007. All of these applications are incorporated by reference herein in their entirety.

The disclosed embodiments relate generally to portable electronic devices, and more particularly, to portable electronic devices that display structured electronic documents such as web pages on a touch screen display.

As portable electronic devices become more compact, and the number of functions performed by a given device increase, it has become a significant challenge to design a user interface that allows users to easily interact with a multifunction device. This challenge is particular significant for handheld portable devices, which have much smaller screens than desktop or laptop computers. This situation is unfortunate because the user interface is the gateway through which users receive not only content but also responses to user actions or behaviors, including user attempts to access a device"s features, tools, and functions. Some portable communication devices (e.g., mobile telephones, sometimes called mobile phones, cell phones, cellular telephones, and the like) have resorted to adding more pushbuttons, increasing the density of push buttons, overloading the functions of pushbuttons, or using complex menu systems to allow a user to access, store and manipulate data. These conventional user interfaces often result in complicated key sequences and menu hierarchies that must be memorized by the user.

In particular, it is slow and tedious to navigate in structured electronic documents (e.g., web pages) in portable electronic devices with small screens using conventional input devices (e.g., 5-way toggle switches). Moreover, it is cumbersome to control and view multimedia content within such documents on portable electronic devices.

The above deficiencies and other problems associated with user interfaces for portable devices are reduced or eliminated by the disclosed portable multifunction device. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen”) with a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through finger contacts and gestures on the touch-sensitive display. In some embodiments, the functions may include telephoning, video conferencing, e-mailing, instant messaging, blogging, digital photographing, digital videoing, web browsing, digital music playing, and/or digital video playing. Instructions for performing these functions may be included in a computer readable storage medium or other computer program product configured for execution by one or more processors.

In one aspect of the invention, a computer-implemented method, for use in conjunction with a portable electronic device with a touch screen display, comprises: displaying at least a portion of a structured electronic document on the touch screen display, wherein the structured electronic document comprises a plurality of boxes of content; detecting a first gesture at a location on the displayed portion of the structured electronic document; determining a first box in the plurality of boxes at the location of the first gesture; and enlarging and substantially centering the first box on the touch screen display.

In another aspect of the invention, a graphical user interface on a portable electronic device with a touch screen display comprises: at least a portion of a structured electronic document, wherein the structured electronic document comprises a plurality of boxes of content. In response to detecting a first gesture at a location on the portion of the structured electronic document, a first box in the plurality of boxes at the location of the first gesture is determined and the first box is enlarged and substantially centered on the touch screen display.

In another aspect of the invention, a portable electronic device comprises: a touch screen display, one or more processors, memory, and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for displaying at least a portion of a structured electronic document on the touch screen display, wherein the structured electronic document comprises a plurality of boxes of content. The one or more programs also include: instructions for detecting a first gesture at a location on the displayed portion of the structured electronic document; instructions for determining a first box in the plurality of boxes at the location of the first gesture; and instructions for enlarging and substantially centering the first box on the touch screen display.

In another aspect of the invention, a computer-program product comprises a computer readable storage medium and a computer program mechanism (e.g., one or more computer programs) embedded therein. The computer program mechanism comprises instructions, which when executed by a portable electronic device with a touch screen display, cause the device: to display at least a portion of a structured electronic document on the touch screen display, wherein the structured electronic document comprises a plurality of boxes of content; to detect a first gesture at a location on the displayed portion of the structured electronic document; to determine a first box in the plurality of boxes at the location of the first gesture; and to enlarge and substantially center the first box on the touch screen display.

In another aspect of the invention, a portable electronic device with a touch screen display comprises: means for displaying at least a portion of a structured electronic document on the touch screen display, wherein the structured electronic document comprises a plurality of boxes of content; means for detecting a first gesture at a location on the displayed portion of the structured electronic document; means for determining a first box in the plurality of boxes at the location of the first gesture; and means for enlarging and substantially centering the first box on the touch screen display.

FIGS. 6A-6C are flow diagrams illustrating a process for displaying structured electronic documents such as web pages on a portable electronic device with a touch screen display in accordance with some embodiments.

FIG. 8 is a flow diagram illustrating a process for displaying inline multimedia content on a portable electronic device with a touch screen display in accordance with some embodiments.

The user interface may include a physical click wheel in addition to a touch screen or a virtual click wheel displayed on the touch screen. A click wheel is a user-interface device that may provide navigation commands based on an angular displacement of the wheel or a point of contact with the wheel by a user of the device. A click wheel may also be used to provide a user command corresponding to selection of one or more items, for example, when the user of the device presses down on at least a portion of the wheel or the center of the wheel. Alternatively, breaking contact with a click wheel image on a touch screen surface may indicate a user command corresponding to selection. For simplicity, in the discussion that follows, a portable multifunction device that includes a touch screen is used as an exemplary embodiment. It should be understood, however, that some of the user interfaces and associated processes may be applied to other devices, such as personal computers and laptop computers, which may include one or more other physical user-interface devices, such as a physical click wheel, a physical keyboard, a mouse and/or a joystick.

The various applications that may be executed on the device may use at least one common physical user-interface device, such as the touch screen. One or more functions of the touch screen as well as corresponding information displayed on the device may be adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch screen) of the device may support the variety of applications with user interfaces that are intuitive and transparent.

The user interfaces may include one or more soft keyboard embodiments. The soft keyboard embodiments may include standard (QWERTY) and/or non-standard configurations of symbols on the displayed icons of the keyboard, such as those described in U.S. patent application Ser. Nos. 11/459,606, “Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, and 11/459,615, “Touch Screen Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, the contents of which are hereby incorporated by reference. The keyboard embodiments may include a reduced number of icons (or soft keys) relative to the number of keys in existing physical keyboards, such as that for a typewriter. This may make it easier for users to select one or more icons in the keyboard, and thus, one or more corresponding symbols. The keyboard embodiments may be adaptive. For example, displayed icons may be modified in accordance with user actions, such as selecting one or more icons and/or one or more corresponding symbols. One or more applications on the portable device may utilize common and/or different keyboard embodiments. Thus, the keyboard embodiment used may be tailored to at least some of the applications. In some embodiments, one or more keyboard embodiments may be tailored to a respective user. For example, one or more keyboard embodiments may be tailored to a respective user based on a word usage history (lexicography, slang, individual usage) of the respective user. Some of the keyboard embodiments may be adjusted to reduce a probability of a user error when selecting one or more icons, and thus one or more symbols, when using the soft keyboard embodiments.

Attention is now directed towards embodiments of the device. FIGS. 1A and 1B are block diagrams illustrating portable multifunction devices 100 with touch-sensitive displays 112 in accordance with some embodiments. The touch-sensitive display 112 is sometimes called a “touch screen” for convenience, and may also be known as or called a touch-sensitive display system. The device 100 may include a memory 102 (which may include one or more computer readable storage mediums), a memory controller 122, one or more processing units (CPU"s) 120, a peripherals interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input/output (I/O) subsystem 106, other input or control devices 116, and an external port 124. The device 100 may include one or more optical sensors 164. These components may communicate over one or more communication buses or signal lines 103.

The I/O subsystem 106 couples input/output peripherals on the device 100, such as the touch screen 112 and other input/control devices 116, to the peripherals interface 118. The I/O subsystem 106 may include a display controller 156 and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input/control devices 116 may include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 may be coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) may include an up/down button for volume control of the speaker 111 and/or the microphone 113. The one or more buttons may include a push button (e.g., 206, FIG. 2). A quick press of the push button may disengage a lock of the touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, which is hereby incorporated by reference. A longer press of the push button (e.g., 206) may turn power to the device 100 on or off. The user may be able to customize a functionality of one or more of the buttons. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

The touch-sensitive touch screen 112 provides an input interface and an output interface between the device and a user. The display controller 156 receives and/or sends electrical signals from/to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects, further details of which are described below.

A touch screen 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. The touch screen 112 and the display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on the touch screen 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on the touch screen. In an exemplary embodiment, a point of contact between a touch screen 112 and the user corresponds to a finger of the user.

The touch screen 112 may use LCD (liquid crystal display) technology, or LPD (light emitting polymer display) technology, although other display technologies may be used in other embodiments. The touch screen 112 and the display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with a touch screen 112.

A touch-sensitive display in some embodiments of the touch screen 112 may be analogous to the multi-touch sensitive tablets described in the following U.S. Pat. Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference. However, a touch screen 112 displays visual output from the portable device 100, whereas touch sensitive tablets do not provide visual output.

A touch-sensitive display in some embodiments of the touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein.

The touch screen 112 may have a resolution in excess of 100 dpi. In an exemplary embodiment, the touch screen has a resolution of approximately 160 dpi. The user may make contact with the touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which are much less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, the device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

In some embodiments, the device 100 may include a physical or virtual click wheel as an input control device 116. A user may navigate among and interact with one or more graphical objects (henceforth referred to as icons) displayed in the touch screen 112 by rotating the click wheel or by moving a point of contact with the click wheel (e.g., where the amount of movement of the point of contact is measured by its angular displacement with respect to a center point of the click wheel). The click wheel may also be used to select one or more of the displayed icons. For example, the user may press down on at least a portion of the click wheel or an associated button. User commands and navigation commands provided by the user via the click wheel may be processed by an input controller 160 as well as one or more of the modules and/or sets of instructions in memory 102. For a virtual click wheel, the click wheel and click wheel controller may be part of the touch screen 112 and the display controller 156, respectively. For a virtual click wheel, the click wheel may be either an opaque or semitransparent object that appears and disappears on the touch screen display in response to user interaction with the device. In some embodiments, a virtual click wheel is displayed on the touch screen of a portable multifunction device and operated by user contact with the touch screen.

The device 100 may also include one or more optical sensors 164. FIGS. 1A and 1B show an optical sensor coupled to an optical sensor controller 158 in I/O subsystem 106. The optical sensor 164 may include charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. The optical sensor 164 receives light from the environment, projected through one or more lens, and converts the light to data representing an image. In conjunction with an imaging module 143 (also called a camera module), the optical sensor 164 may capture still images or video. In some embodiments, an optical sensor is located on the back of the device 100, opposite the touch screen display 112 on the front of the device, so that the touch screen display may be used as a viewfinder for either still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user"s image may be obtained for videoconferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 164 may be used along with the touch screen display for both video conferencing and still and/or video image acquisition.

The device 100 may also include one or more proximity sensors 166. FIGS. 1A and 1B show a proximity sensor 166 coupled to the peripherals interface 118. Alternately, the proximity sensor 166 may be coupled to an input controller 160 in the I/O subsystem 106. The proximity sensor 166 may perform as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device,” filed Sep. 30, 2005; Ser. No. 11/240,788, “Proximity Detector In Handheld Device,” filed Sep. 30, 2005; Ser. No. 11/620,702, filed Jan. 7, 2007, “Using Ambient Light Sensor To Augment Proximity Sensor Output,” Ser. No. 11/586,862, filed Oct. 24, 2006, “Automated Response To And Sensing Of User Activity In Portable Devices,” and Ser. No. 11/638,251, filed Dec. 12, 2006, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user"s ear (e.g., when the user is making a phone call). In some embodiments, the proximity sensor keeps the screen off when the device is in the user"s pocket, purse, or other dark area to prevent unnecessary battery drainage when the device is a locked state.

The device 100 may also include one or more accelerometers 168. FIGS. 1A and 1B show an accelerometer 168 coupled to the peripherals interface 118. Alternately, the accelerometer 168 may be coupled to an input controller 160 in the I/O subsystem 106. The accelerometer 168 may perform as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are which are incorporated herein by reference. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers.

The contact/motion module 130 may detect contact with the touch screen 112 (in conjunction with the display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). The contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred, determining if there is movement of the contact and tracking the movement across the touch screen 112, and determining if the contact has been broken (i.e., if the contact has ceased). Determining movement of the point of contact may include determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations may be applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, the contact/motion module 130 and the display controller 156 also detects contact on a touchpad. In some embodiments, the contact/motion module 130 and the controller 160 detects contact on a click wheel.

The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112, including components for changing the intensity of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the contacts module 137 may be used to manage an address book or contact list, including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in the address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, the videoconferencing module 139 may be used to initiate, conduct, and terminate a video conference between a user and one or more other participants.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the e-mail client module 140 may be used to create, send, receive, and manage e-mail. In conjunction with image management module 144, the e-mail module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 may be used to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, image management module 144, and browsing module 147, the blogging module 142 may be used to send text, still images, video, and/or other graphics to a blog (e.g., the user"s blog).

In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, the camera module 143 may be used to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 may be used to arrange, modify or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, and speaker 111, the video player module 145 may be used to display, present or otherwise play back videos (e.g., on the touch screen or on an external, connected display via external port 124).

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, the music player module 146 allows the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files. In some embodiments, the device 100 may include the functionality of an MP3 player, such as an iPod (trademark of Apple Computer, Inc.).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, the browser module 147 may be used to browse the Internet, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages. Embodiments of user interfaces and associated processes using browser module 147 are described further below.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail module 140, and browser module 147, the calendar module 148 may be used to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget modules 149 are mini-applications that may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, the search module 151 may be used to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms).

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the notes module 153 may be used to create and manage notes, to do lists, and the like.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, the map module 154 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data).

In some embodiments, the device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen 112 and/or a touchpad. By using a touch screen and/or a touchpad as the primary input/control device for operation of the device 100, the number of physical input/control devices (such as push buttons, dials, and the like) on the device 100 may be reduced.

The predefined set of functions that may be performed exclusively through a touch screen and/or a touchpad include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main, home, or root menu from any user interface that may be displayed on the device 100. In such embodiments, the touchpad may be referred to as a “menu button.” In some other embodiments, the menu button may be a physical push button or other physical input/control device instead of a touchpad.

FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen may display one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user may select one or more of the graphics by making contact or touching the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the contact may include a gesture, such as one or more taps, one or more swipes (from left to right, right to left, upward and/or downward) and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with the device 100. In some embodiments, inadvertent contact with a graphic may not select the graphic. For example, a swipe gesture that sweeps over an application icon may not select the corresponding application when the gesture corresponding to selection is a tap.

The device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, the menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI in touch screen 112.

In one embodiment, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, a Subscriber Identity Module (SIM) card slot 210, a head set jack 212, and a docking/charging external port 124. The push button 206 may be used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, the device 100 also may accept verbal input for activation or deactivation of some functions through the microphone 113.

Conversely, the device maintains the user-interface lock state if the detected contact does not correspond to the predefined gesture. As noted above, processes that use gestures on the touch screen to unlock the device are described in U.S. patent application Ser. Nos. 11/322,549, “Unlocking A Device By Performing Gestures On An Unlock Image,” filed Dec. 23, 2005, and 11/322,550, “Indication Of Progress Towards Satisfaction Of A User Input Condition,” filed Dec. 23, 2005, which are hereby incorporated by reference.

In some embodiments, UI 400A or 400B displays all of the available applications 136 on one screen so that there is no need to scroll through a list of applications (e.g., via a scroll bar). In some embodiments, as the number of applications increase, the icons corresponding to the applications may decrease in size so that all applications may be displayed on a single screen without scrolling. In some embodiments, having all applications on one screen and a menu button enables a user to access any desired application with at most two inputs, such as activating the menu button 204 and then activating the desired application (e.g., by a tap or other finger gesture on the icon corresponding to the application).

In some embodiments, in response to a predefined gesture by the user on a block 3914 (e.g., a single tap gesture or a double tap gesture), the block is enlarged and centered (or substantially centered) in the web page display. For example, in response to a single tap gesture 3923 on block 3914-5, block 3914-5 may be enlarged and centered in the display, as shown in UI 3900C, FIG. 5C. In some embodiments, the width of the block is scaled to fill the touch screen display. In some embodiments, the width of the block is scaled to fill the touch screen display with a predefined amount of padding along the sides of the display. In some embodiments, a zooming animation of the block is displayed during enlargement of the block. Similarly, in response to a single tap gesture 3925 on block 3914-2, block 3914-2 may be enlarged with a zooming animation and two-dimensionally scrolled to the center of the display (not shown).

FIGS. 6A-6C are flow diagrams illustrating a process 6000 for displaying structured electronic documents such as web pages on a portable electronic device with a touch screen display (e.g., device 100) in accordance with some embodiments. The portable electronic device displays at least a portion of a structured electronic document on the touch screen display. The structured electronic document comprises a plurality of boxes of content (e.g., blocks 3914, FIG. 5A) (6006).

In some embodiments, displaying at least a portion of the structured electronic document comprises scaling the document width to fit within the touch screen display width independent of the document length (6008).

In some embodiments, the touch screen display is rectangular with a short axis and a long axis (also called the minor axis and major axis); the display width corresponds to the short axis (or minor axis) when the structured electronic document is seen in portrait view (e.g., FIG. 5C); and the display width corresponds to the long axis (or major axis) when the structured electronic document is seen in landscape view (e.g., FIG. 5D).

In some embodiments, prior to displaying at least a portion of a structured electronic document, borders, margins, and/or paddings are determined for the plurality of boxes (6002) and adjusted for display on the touch screen display (6004). In some embodiments, all boxes in the plurality of boxes are adjusted. In some embodiments, just the first box is adjusted. In some embodiments, just the first box and boxes adjacent to the first box are adjusted.

The first box is enlarged and substantially centered on the touch screen display (e.g., Block 5 3914-5, FIG. 5C) (6020). In some embodiments, enlarging and substantially centering comprises simultaneously zooming and translating the first box on the touch screen display (6022). In some embodiments, enlarging comprises expanding the first box so that the width of the first box is substantially the same as the width of the touch screen display (6024).

In some embodiments, text in the enlarged first box is resized to meet or exceed a predetermined minimum text size on the touch screen display (6026). In some embodiments, the text resizing comprises: determining a scale factor by which the first box will be enlarged (6028); dividing the predetermined minimum text size on the touch screen display by the scaling factor to determine a minimum text size for text in the first box (6030); and if a text size for text in the first box is less than the determined minimum text size, increasing the text size for text in the first box to at least the determined minimum text size (6032). In some embodiments, the first box has a width; the display has a display width; and the scale factor is the display width divided by the width of the first box prior to enlarging. In some embodiments, the resizing occurs during the enlarging. In some embodiments, the resizing occurs after the enlarging.

In some embodiments, text in the structured electronic document is resized to meet or exceed a predetermined minimum text size on the touch screen display (6026; FIG. 6B). In some embodiments, the text resizing comprises: determining a scale factor by which the first box will be enlarged (6028); dividing the predetermined minimum text size on the touch screen display by the scaling factor to determine a minimum text size for text in the structured electronic document (6030); and if a text size for text in the structured electronic document is less than the determined minimum text size, increasing the text size for text in the structured electronic document to at least the determined minimum text size (6032). In some embodiments, the text resizing comprises: identifying boxes containing text in the plurality of boxes; determining a scale factor by which the first box will be enlarged; dividing the predetermined minimum text size on the touch screen display by the scaling factor to determine a minimum text size for text in the structured electronic document; and for each identified box containing text, if a text size for text in the identified box is less than the determined minimum text size, increasing the text size for text in the identified box to at least the determined minimum text size and adjusting the size of the identified box to accommodate the resized text.

In some embodiments, while the first box is enlarged, a third gesture (e.g., gesture 3927 or gesture 3935, FIG. 5C) is detected on a second box other than the first box (6040). In response to detecting the third gesture, the second box is substantially centered on the touch screen display (6042). In some embodiments, the third gesture and the first gesture are the same type of gesture. In some embodiments, the third gesture is a finger gesture. In some embodiments, the third gesture is a stylus gesture.

In some embodiments, a swipe gesture (e.g., gesture 3937 or gesture 3939, FIG. 5C) is detected on the touch screen display (6044; FIG. 6C). In response to detecting the swipe gesture, the displayed portion of the structured electronic document is translated on the touch screen display (6046). In some embodiments, the translating comprises vertical, horizontal, or diagonal movement of the structured electronic document on the touch screen display (6048). In some embodiments, the swipe gesture is a finger gesture. In some embodiments, the swipe gesture is a stylus gesture.

In some embodiments, a fifth gesture (e.g., multi-touch gesture 3941/3943, FIG. 5C) is detected on the touch screen display (6050). In response to detecting the fifth gesture, the displayed portion of the structured electronic document is rotated on the touch screen display by 90° (6052). In some embodiments, the fifth gesture is a finger gesture. In some embodiments, the fifth gesture is a multifinger gesture. In some embodiments, the fifth gesture is a twisting gesture.

In some embodiments, a change in orientation of the device is detected (6054). For example, the one or more accelerometers 168 (FIGS. 1A-1B) detect a change in orientation of the device. In response to detecting the change in orientation of the device, the displayed portion of the structured electronic document is rotated on the touch screen display by 90° (6056).

In some embodiments, a multi-finger de-pinch gesture (e.g., multi-touch gesture 3931/3933, FIG. 5C) is detected on the touch screen display (6058). In response to detecting the multi-finger de-pinch gesture, a portion of the displayed portion of the structured electronic document is enlarged on the touch screen display in accordance with a position of the multi-finger de-pinch gesture and an amount of finger movement in the multi-finger de-pinch gesture (6060).

A graphical user interface (e.g., UI 3900A, FIG. 5A) on a portable electronic device with a touch screen display comprises at least a portion of a structured electronic document (e.g., web page 3912, FIG. 5A). The structured electronic document comprises a plurality of boxes of content (e.g., blocks 3914, FIG. 5A). In response to detecting a first gesture (e.g., gesture 3923, FIG. 5A) at a location on the portion of the structured electronic document, a first box (e.g., Block 5 3914-5, FIG. 5A) in the plurality of boxes at the location of the first gesture is determined and the first box is enlarged and substantially centered on the touch screen display (e.g., Block 5 3914-5, FIG. 5C).

In some embodiments, in response to a tap or other predefined user gesture on URL entry box 3908, the touch screen displays an enlarged entry box 3926 and a keyboard 616 (e.g., UI 3900B, FIG. 5B in portrait viewing and UI 3900E, FIG. 5E in landscape viewing). In some embodiments, the touch screen also displays: Contextual clear icon 3928 that when activated (e.g., by a finger tap on the icon) initiates deletion of all text in entry box 3926;

UI 3900G (FIG. 5G) is a UI for adding new windows to an application, such as the browser 147. UI 3900G displays an application (e.g., the browser 147), which includes a displayed window (e.g., web page 3912-2) and at least one hidden window (e.g., web pages 3912-1 and 3934-3 and possibly other web pages that are completely hidden off-screen). UI 3900G also displays an icon for adding windows to the application (e.g., new window or new page icon 3936). In response to detecting activation of the icon 3936 for adding windows, the browser adds a window to the application (e.g., a new window for a new web page 3912).

In response to detecting a gesture on the touch screen display, a displayed window in the application is moved off the display and a hidden window is moved onto the display. For example, in response to detecting a tap gesture 3949 on the left side of the screen, the window with web page 3912-2 is moved partially or fully off-screen to the right, the window with web page 3912-3 is moved completely off-screen, partially hidden window with web page 3912-1 is moved to the center of the display, and another completely hidden window with a web page (e.g., 3912-0) may be moved partially onto the display. Alternatively, detection of a left-to-right swipe gesture 3951 may achieve the same effect.

Conversely, in response to detecting a tap gesture 3953 on the right side of the screen, the window with web page 3912-2 is moved partially or fully off-screen to the left, the window with web page 3912-1 is moved completely off-screen, partially hidden window with web page 3912-3 is moved to the center of the display, and another completely hidden window with a web page (e.g., 3912-4) may be moved partially onto the display. Alternatively, detection of a right-to-left swipe gesture 3951 may achieve the same effect.

In some embodiments, in response to a tap or other predefined gesture on a delete icon 3934, the corresponding window 3912 is deleted. In some embodiments, in response to a tap or other predefined gesture on Done icon 3938, the window in the center of the display (e.g., 3912-2) is enlarged to fill the screen.

FIG. 8 is a flow diagram illustrating a process 8000 for displaying inline multimedia content on a portable electronic device with a touch screen display (e.g., device 100) in accordance with some embodiments. The portable electronic device displays at least a portion of a structured electronic document on the