Input: [UIReturnKeyType] UIReturnKeyGoogle [German text] Suchen [English text]

Output: Search


Input: [UIReturnKeyType] UIReturnKeyJoin [German text] Verbinden [English text]

Output: Join


Input: [UIReturnKeyType] UIReturnKeyNext [German text] Weiter [English text]

Output: Next


Input: [UIReturnKeyType] UIReturnKeyRoute [German text] Route [English text]

Output: Route


Input: [UIReturnKeyType] UIReturnKeySearch [German text] Suchen [English text]

Output: Search


Input: [UIReturnKeyType] UIReturnKeySend [German text] Senden [English text]

Output: Send


Input: [UIReturnKeyType] UIReturnKeyYahoo [German text] Suchen [English text]

Output: Search


Input: [UIReturnKeyType] UIReturnKeyDone [German text] Fertig [English text]

Output: Done


Input: [UIReturnKeyType] UIReturnKeyEmergencyCall [German text] Notruf [English text]

Output: Emergency Call


Input: [Returns] Check Constraints [Name]

Output: CHECK_CONSTRAINTS

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every column that has a user-defined data type. [Name]

Output: COLUMN_DOMAIN_USAGE

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every column with a privilege granted to or by the current user in the current database. [Name]

Output: COLUMN_PRIVILEGES

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Lists every column in the system [Name]

Output: COLUMNS

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every column that has a constraint defined on it. [Name]

Output: CONSTRAINT_COLUMN_USAGE

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every table that has a constraint defined on it. [Name]

Output: CONSTRAINT_TABLE_USAGE

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every user-defined data type with a rule bound to it. [Name]

Output: DOMAIN_CONSTRAINTS

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every user-defined data type. [Name]

Output: DOMAINS

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every column that is constrained as a key [Name]

Output: KEY_COLUMN_USAGE

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every parameter for every user-defined function or stored procedure in the datbase. For functions this returns one row with return value information. [Name]

Output: PARAMETERS

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every foreign constraint in the system. [Name]

Output: REFERENTIAL_CONSTRAINTS

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every column returned by table-valued functions. [Name]

Output: ROUTINE_COLUMNS

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every stored procedure and function in the database. [Name]

Output: ROUTINES

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every database in the system. [Name]

Output: SCHEMATA

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every table constraint. [Name]

Output: TABLE_CONSTRAINTS

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every table privilege granted to or by the current user. [Name]

Output: TABLE_PRIVILEGES

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every table in the system. [Name]

Output: TABLES

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every column used in a view definition. [Name]

Output: VIEW_COLUMN_USAGE

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every table used in a view definition. [Name]

Output: VIEW_TABLE_USAGE

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [Returns] Every View [Name]

Output: VIEWS

Bulletproof Sql Change Scripts Using INFORMATION_SCHEMA Views - You've Been Haacked


Input: [DC element] title [Evergreen index]

Output: title


Input: [DC element] creator [Evergreen index]

Output: author


Input: [DC element] contributor [Evergreen index]

Output: author


Input: [DC element] publisher [Evergreen index]

Output: keyword


Input: [DC element] subject [Evergreen index]

Output: subject


Input: [DC element] identifier [Evergreen index]

Output: keyword


Input: [DC element] type [Evergreen index]


Input: [DC element] format [Evergreen index]


Input: [DC element] language [Evergreen index]

Output: lang


Input: setBigDecimal Send as DECIMAL

Output: Send as NUMBER

Teradata JDBC Driver User Guide Chapter 2

Teradata Database 14.0 and later, with NUMBER Data Type


Input: setObject with BigDecimal data value and no targetSqlType argument Send as DECIMAL

Output: Send as NUMBER

Teradata JDBC Driver User Guide Chapter 2

Teradata Database 14.0 and later, with NUMBER Data Type


Input: setObject with BigDecimal data value and targetSqlType argument Types.NUMERIC Send as DECIMAL

Output: Send as NUMBER

Teradata JDBC Driver User Guide Chapter 2

Teradata Database 14.0 and later, with NUMBER Data Type


Input: setObject with BigDecimal data value and targetSqlType argument Types.DECIMAL Send as DECIMAL

Output: Send as DECIMAL

Teradata JDBC Driver User Guide Chapter 2

Teradata Database 14.0 and later, with NUMBER Data Type


Input: setNull with targetSqlType argument Types.NUMERIC Send as DECIMAL

Output: Send as NUMBER

Teradata JDBC Driver User Guide Chapter 2

Teradata Database 14.0 and later, with NUMBER Data Type


Input: setNull with targetSqlType argument Types.DECIMAL Send as DECIMAL

Output: Send as DECIMAL

Teradata JDBC Driver User Guide Chapter 2

Teradata Database 14.0 and later, with NUMBER Data Type


Input: [Keyboard and Mouse] Mouse 1 [Xbox controller] Right Trigger [Function]

Output: Primary Attacker

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] Mouse 2 [Xbox controller] Left Trigger [Function]

Output: Alternate Attack

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] Left Shift [Xbox controller] Right Bumper [Function]

Output: Action Wheel

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] W [Xbox controller] Left Thumstick Up [Function]

Output: Move Forward

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] A [Xbox controller] Left Thumstick Left [Function]

Output: Strafe Left

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] S [Xbox controller] Left Thumstick Down [Function]

Output: Move Backward

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] D [Xbox controller] Left Thumstick Right [Function]

Output: Strafe Right

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] X [Xbox controller] Left Thumbstick(Push) [Function]

Output: Swap weapons (Series EV)

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] E [Xbox controller] X [Function]

Output: Activate

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] F [Xbox controller] Y [Function]

Output: Alternate Activate

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] C [Xbox controller] B [Function]

Output: Call Out and Mark Location

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] R [Function]

Output: Alternate Attack

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] I [Xbox controller] Select [Function]

Output: Hero Info

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] M [Function]

Output: Drop All Mana

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] G [Function]

Output: Activate crystal

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] Space [Xbox controller] A [Function]

Output: Jump

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] Ctrl [Xbox controller] Left Bumper [Function]

Output: Move Camera

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Xbox controller] Right Thumbstick [Function]

Output: Adjust Camera

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] + [Xbox controller] = [Function]

Output: Increase Radius

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] - [Xbox controller] _ [Function]

Output: Decrease Radius

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] Mouse Wheel Up/Down [Xbox controller] Right Thumbstick(Push) [Function]

Output: Change Zoom

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] Esc [Xbox controller] Start [Function]

Output: Pause

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] F1 or ~(tilde) [Function]

Output: Chat Log

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] 1 [Xbox controller] DPad Left [Function]

Output: Heal

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] 2 [Xbox controller] DPad Down [Function]

Output: Skill 1

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] 3 [Xbox controller] DPad Up [Function]

Output: Skill 2

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] 4 [Xbox controller] Dpad Right [Function]

Output: Repair

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] 5 [Function]

Output: Upgrade

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] 6 [Function]

Output: Defense 1

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] 7 [Function]

Output: Defense 2

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] 8 [Function]

Output: Defense 3

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] 9 [Function]

Output: Defense 4

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] 0 [Function]

Output: Defense 5

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] H [Function]

Output: Toggle HUD

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Keyboard and Mouse] Q [Function]

Output: Free Look

Controls and Keybindings for PC - Dungeon Defenders Wiki


Input: [Option] -c [Description] Compiles to .OBJ, no link [Details]

Output: Compiles and assembles the named .C, .CPP, and .ASM files, but does not execute a link on the resulting .OBJ files.


Input: [Option] -e [Description] Specify executable filename [Details]

Output: Link file using as the name of the executable file. If you do not specify an executable name with this option, the linker creates an executable file based on the name of the first source file or object file listed in the command.


Input: [Option] -l [Description] Pass option to linker. [Details]

Output: Use this command-line option to pass option(s) to the linker from a compile command. Use the command-line option -l-x to disable a specific linker option.


Input: [Option] -M [Description] Create a MAP file [Details]

Output: Use this compiler option to instruct the linker to create a map file.


Input: [Option] -o [Description] Compike .OBJ to [Details]

Output: Compiles the specified source file to .OBJ


Input: [Option] -P [Description] C++ compile [Details]

Output: Causes the compiler to compile all source files as C++ files, regardless of their extension. Use ‑P‑ to compile all .CPP files as C++ source files and all other files as C source files. The command-line option -Pext causes the compiler to compile all source files as C++ files and it changes the default extension to whatever you specify with ext. This option is provided because some programmers use different extensions as their default extension for C++ code. The option -P-ext compiles files based on their extension (.CPP compiles to C++, all other extensions compile to C) and sets the default extension (other than .CPP).


Input: [Option] -tWM [Description] Generate a multi-threaded target [Details]

Output: Creates a multi-threaded .EXE or .DLL. This option is not needed if you include a module definition file (.DEF file) in your compile and link commands which specify the type of 32-bit application you intend to build.


Input: [Action] Query parse [When]

Output: PREPARE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Action] Negation elimination [When]

Output: PREPARE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Action] Subquery re-writes [When]

Output: PREPARE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Action] Nested JOIN simplification [When]

Output: First EXECUTE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Action] OUTER->INNER JOIN conversions [When]

Output: First EXECUTE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Action] Partition pruning [When]

Output: Every EXECUTE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Action] COUNT/MIN/MAX elimination [When]

Output: Every EXECUTE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Action] Constant subexpression removal [When]

Output: Every EXECUTE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Action] Equality propagation [When]

Output: Every EXECUTE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Action] Constant table detection [When]

Output: Every EXECUTE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Action] ref access analysis [When]

Output: Every EXECUTE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Action] range/index_merge analysis and optimization [When]

Output: Every EXECUTE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Action] Join optimization [When]

Output: Every EXECUTE

Sergey Petrunia’s blog » MySQL Optimizer and Prepared Statements


Input: [Strategy] timestamp-up [Explanations]

Output: Sort by any timestamp, early first


Input: [Strategy] timestamp-down [Explanations]

Output: Sort by any timestamp, late first


Input: [Strategy] scheduled-up [Explanations]

Output: Sort by scheduled timestamp, early first


Input: [Strategy] scheduled-down [Explanations]

Output: Sort by scheduled timestamp, late first


Input: [Strategy] deadline-up [Explanations]

Output: Sort by deadline timestamp, early first


Input: [Strategy] deadline-down [Explanations]

Output: Sort by deadline timestamp, late first


Input: [Strategy] ts-up [Explanations]

Output: Sort by active timestamp, early first


Input: [Strategy] ts-down [Explanations]

Output: Sort by active timestamp, late first


Input: [Strategy] tsia-up [Explanations]

Output: Sort by inactive timestamp, early first


Input: [Strategy] tsia-down [Explanations]

Output: Sort by inactive timestamp, late first


Input: [VALUE] APIV [EXPLANATION] Current ImHuman API version which ImHuman API runs on. Just for debugging [TYPE]

Output: Double


Input: [VALUE] MAPIV [EXPLANATION] Currently required Minimum Client Library version to connect to API [TYPE]

Output: Double


Input: [VALUE] CLAPIV [EXPLANATION] Currently connected client's library version. (debugging) [TYPE]

Output: Double


Input: [VALUE] ERROR [EXPLANATION] Error Identification Number which returns 0 on ne error and starts from 100 on errors [TYPE]

Output: Integer


Input: [VALUE] RSP [EXPLANATION] If an error occured returns the explanation of the error code If not, returns the contents of Response [TYPE]

Output: String


Input: [VALUE] RSP::WORD [EXPLANATION] The word | tag needs to be selected through humanizers [TYPE]

Output: String


Input: [VALUE] RSP::ANSWER [EXPLANATION] Answer for the correct humanizer selection. [TYPE]

Output: String


Input: [VALUE] RSP::GRID [EXPLANATION] Consists or [row * col] by [3] array. [row * col ][ i ] :: [ src = humanizer source ][ name = humanizer unique name][ value= humanizer unique value ] [TYPE]

Output: Array|Object


Input: [Test Area] App Authentication [Result] Pass/Fail [Description]

Output: Use the Hootsuite SDK Single Sign On authentication when connecting the app to Hootsuite. User authentication with your app can be done using the authentication flows of your choice (OAuth recommended). Authentication should be persistent from one session to another and will not expire until the user selects to “Disconnect”


Input: [Test Area] Multiple Account Support [Result] Pass/Fail [Description]

Output: User can logout and login as another user and can add multiple streams and authenticate each with a different account.


Input: [Test Area] Retain User Settings [Result] Pass/Fail [Description]

Output: The App will retain any user settings saved in the stream from one session to another. Our preference is that you use the hsp.saveData and hsp.getData methods.


Input: [Test Area] Suppress refresh during user interaction [Result] Pass/Fail [Description]

Output: Suppress reloading of messages through refresh handlers (via hsp.bind) while the user interacts with the stream (e.g. posting messages, expanded details, possibly scroll position not near the top).


Input: [Test Area] Fully HTTPS Compliant [Result] Pass/Fail [Description]

Output: The Hootsuite dashboard is a forced SSL connection. The app will be fully HTTPS compliant and will not generate any security breaking errors or warnings. Hootsuite can provide an image proxy service on request.


Input: [Test Area] Infinite Scroll [Result] Pass/Fail [Description]

Output: Provide the next set of messages/updates when user scrolls down.


Input: [Test Area] UI and Design Assets [Result] Pass/Fail [Description]

Output: Please use the CSS and HTML assets from the sample code as your starting point when building an app. The menu bar will contain at a minimum two icons: Settings (shows logged in account and option to logout) and the ‘More’ dropdown (with Help, Feedback and Developer links, URLs for first two provided by Hootsuite).


Input: [Test Area] Stream Refresh [Result] Pass/Fail [Description]

Output: Fires when app column is refreshed by user in-stream, or as part of a dashboard refresh.


Input: [Test Area] App Logo [Result] Pass/Fail [Description]

Output: Use a vector based image with transparent backgrounds for the 16x16, 30x30, and 256x256 icons. Hosted from a HTTPS address.


Input: [Test Area] Browser Compatibility [Result] Pass/Fail [Description]

Output: Latest versions of Google Chrome, Firefox, Safari, IE 9+


Input: [Control Name] Button [Description]

Output: A Button that supports a Confirmation message before submitting a form.


Input: [Control Name] Image [Description]

Output: An Image that allows you to set the MouseOverImageUrl property.


Input: [Control Name] ImageButton [Description]

Output: An ImageButton that supports a Confirmation message before submitting a form and a MouseOverImageUrl.


Input: [Control Name] ImageCheckBox [Description]

Output: A CheckBox that renders itself as an image either checked or unchecked. It also supports MouseOverImageUrl for both states.


Input: [Control Name] MyObjectDataSource [Description]

Output: An ObjectDataSource that supports build in sorting and filtering of returned objects.


Input: [Control Name] CompareValidator [Description]

Output: A CompareValidator that supports displaying error messages as an image.


Input: [Control Name] RequiredFieldValidator [Description]

Output: A RequiredFieldValidator that supports displaying error messages as an image.


Input: [Control Name] PageParameter [Description]

Output: A parameter that can be used in DataSource controls parameter collections such as SelectParameters. It allows you to get parameters from properties of a page.


Input: [Control Name] TemplateControlParameter [Description]

Output: A parameter that can be used in DataSource controls parameter collections such as SelectParameters. It allows you to get parameters from properties of a nearest TemplateControl.


Input: [Term] dcterms:title [Purpose]

Output: The name of the dataset.

Describing Linked Datasets with the voiD Vocabulary

Using Dublin Core Metadata Terms in VoID for general dataset metadata


Input: [Term] dcterms:description [Purpose]

Output: A textual description of the dataset.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:creator [Purpose]

Output: An entity, such as a person, organisation, or service, that is primarily responsible for creating the dataset. The creator should be described as an RDF resource, rather than just providing the name as a literal.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:publisher [Purpose]

Output: An entity, such as a person, organisation, or service, that is responsible for making the dataset available. The publisher should be described as an RDF resource, rather than just providing the name as a literal.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:contributor [Purpose]

Output: An entity, such as a person, organisation, or service, that is responsible for making contributions to the dataset. The contributor should be described as an RDF resource, rather than just providing the name as a literal.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:source [Purpose]

Output: A related resource from which the dataset is derived. The source should be described as an RDF resource, rather than as a literal.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:date [Purpose]

Output: A point or period of time associated with an event in the life-cycle of the resource. The value should be formatted and data-typed as an xsd:date.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:created [Purpose]

Output: Date of creation of the dataset. The value should be formatted and data-typed as an xsd:date.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:issued [Purpose]

Output: Date of formal issuance (e.g., publication) of the dataset. The value should be formatted and datatyped as an xsd:date.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:modified [Purpose]

Output: Date on which the dataset was changed. The value should be formatted and datatyped as an xsd:date.

Describing Linked Datasets with the voiD Vocabulary


Input: [Element] name [Description]

Output: The name element contains the username of the user. This is a short, usually less than 16 character "handle" of the user, not the real, full name. This should be the same as the username parameter used when calling the function, and hence redundant.

The user information array


Input: [Element] passwd [Description]

Output: The passwd element contains the user's password in an encrypted format. Often, for example on a system employing "shadow" passwords, an asterisk is returned instead.

The user information array


Input: [Element] uid [Description]

Output: User ID of the user in numeric form.

The user information array


Input: [Element] gid [Description]

Output: The group ID of the user. Use the function posix_getgrgid() to resolve the group name and a list of its members.

The user information array


Input: [Element] gecos [Description]

Output: GECOS is an obsolete term that refers to the finger information field on a Honeywell batch processing system. The field, however, lives on, and its contents have been formalized by POSIX. The field contains a comma separated list containing the user's full name, office phone, office number, and home phone number. On most systems, only the user's full name is available.

The user information array


Input: [Element] dir [Description]

Output: This element contains the absolute path to the home directory of the user.

The user information array


Input: [Element] shell [Description]

Output: The shell element contains the absolute path to the executable of the user's default shell.

The user information array


Input: [Offset] 23A8 [Description]

Output: GHZ level palette


Input: [Offset] 6DDE [Description]

Output: GHZ dynamic screen resizing


Input: [Offset] 1C054 [Description]

Output: GHZ animated pattern load cue


Input: [Offset] 1D17C [Description]

Output: GHZ object debug list


Input: [Offset] 3BCF2 [Description]

Output: GHZ 16x16 block mappings


Input: [Offset] 3C692 [Description]

Output: GHZ Primary pattern block


Input: [Offset] 3DCF2 [Description]

Output: GHZ secondary pattern block


Input: [Offset] 3F09A [Description]

Output: GHZ 256x256 block mappings


Input: [Offset] 64A00 [Description]

Output: GHZ 16x16 collision index


Input: [Offset] 68C7E [Description]

Output: GHZ act 1 foreground


Input: [Offset] 68D74 [Description]

Output: GHZ act 2 foreground


Input: [Offset] 68E40 [Description]

Output: GHZ act 3 foreground


Input: [Offset] 68F62 [Description]

Output: GHZ act 1/2/3/ending sequence background


Input: [Offset] 6B096 [Description]

Output: GHZ act 1/4 sprite locations


Input: [Offset] 6B5A0 [Description]

Output: GHZ act 2 sprite locations


Input: [Offset] 6BB5E [Description]

Output: GHZ act 3 sprite locations


Input: [Key] Scrl Lock (Ins in (SDL)MESS) [Function]

Output: Switch MESS to partial keyboard emulation which lets you use keys like Tab to access UI, p to pause, Esc to quit, etc.


Input: [Key] S-Scrl Lock [Function]

Output: Paste copied text into the emulated computer


Input: [Key] Tab [Function]

Output: Access MESS Internal UI


Input: [Key] p [Function]

Output: Pause the emulation


Input: [Key] S-p [Function]

Output: Skip one frame forward if paused


Input: [Key] Esc [Function]

Output: Quit the emulation


Input: [Key] F3 [Function]

Output: Reset the emulated system


Input: [Key] S-F3 [Function]

Output: Performs a “hard reset”, which tears everything down and re-creates it from scratch. This is a more thorough and complete reset than an F3 pressure


Input: [Key] F6 [Function]

Output: Toggle cheat mode (if started with “-cheat”)


Input: [Key] F7 [Function]

Output: Load a saved system state from a slot number (Only few systems support Save States at the moment)


Input: [Key] S-F7 [Function]

Output: Save system state to 1 of 10 slots (Only few systems support Save States at the moment)


Input: [Key] F8 [Function]

Output: Decrease frame skip during emulation


Input: [Key] F9 [Function]

Output: Increase frame skip during emulation


Input: [Key] F10 [Function]

Output: Speed Throttle (Makes system overspeed)


Input: [Key] F11 [Function]

Output: Frames Per Second and Frameskip information


Input: [Key] F12 [Function]

Output: Saves image of system screen to snaps directory (the name of the saved snap can be configured in mess.ini)


Input: [Key] Ins [Function]

Output: Fast forward. While held, runs the game with throttling disabled and with the maximum frameskip


Input: [Description] Calculate the surface distance in kilometres from this LatLng to the given LatLng. [Name]

Output: Distance


Input: [Description] Calculate the surface distance in miles from this LatLng to the given LatLng. [Name]

Output: DistanceMiles


Input: [Description] Determines whether the specified Object is equal to the current Object. (Inherited from Object.) [Name]

Output: Equals


Input: [Description] Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.) [Name]

Output: Finalize


Input: [Description] Serves as a hash function for a particular type. (Inherited from Object.) [Name]

Output: GetHashCode


Input: [Description] Gets the Type of the current instance. (Inherited from Object.) [Name]

Output: GetType


Input: [Description] Determines whether the specified latitude is valid. [Name]

Output: IsValidLatitude


Input: [Description] Determines whether the specified longitude is valid longitude. [Name]

Output: IsValidLongitude


Input: [Description] Creates a shallow copy of the current Object. (Inherited from Object.) [Name]

Output: MemberwiseClone


Input: [Description] Converts this LatLng to another datum. [Name]

Output: ToDatum


Input: [Description] Return a String representation of this LatLng object in degrees-minutes-seconds format. The returned format will be like this: DD MM SS.SSS N DD MM SS.SSS E where DD is the number of degrees, MM is the number of minutes, SS.SSS is the number of seconds, N is either N or S to indicate north or south of the equator and E is either E or W to indicate east or west of the prime meridian. [Name]

Output: ToDMSString


Input: [Description] Convert this latitude and longitude to an MGRS reference. [Name]

Output: ToMGRSRef


Input: [Description] Convert this LatLng from the WGS84 datum to the OSGB36 datum using an approximate Helmert transformation. [Name]

Output: ToOSGB36


Input: [Description] Convert this latitude and longitude into an OSGB (Ordnance Survey of Great Britain) grid reference. [Name]

Output: ToOSRef


Input: [Description] Returns a String that represents the current LatLng object. (Overrides Object..::..ToString()()()().) [Name]

Output: ToString


Input: [Description] Convert this latitude and longitude to a UTM reference. [Name]

Output: ToUtmRef


Input: [Description] Convert this LatLng from the OSGB36 datum to the WGS84 datum using an approximate Helmert transformation. [Name]

Output: ToWGS84


Input: [File] components.hda [Description] Specifies the components that are enabled and the location of the corresponding Component Definition File. It is located in the /config directory. [Name]

Output: Component File

WebCenter Content | TEAM Informatics blog


Input: [File] *.hda [Description] A glue file or component definition file. Points to custom resources defined for a file. The glue file for a component is typically named ComponentName.hda. It is located in the root component directory. [Name]

Output: Component Definition File (Glue File)

WebCenter Content | TEAM Informatics blog


Input: [File] manifest.hda [Description] This lists the files that make up the component and specifies their locations. It points to resources through the Glue File. The file is always located in the root directory when present, but does not appear until the Component is built. This is because this file is used for installation of the component. [Name]

Output: Manifest File

WebCenter Content | TEAM Informatics blog


Input: [File] *_environment.cfg [Description] File defines configuration setting for Content Server. Located in the root component directory. [Name]

Output: Environment Resource

WebCenter Content | TEAM Informatics blog


Input: [File] *_resource.htm [Description] Resource file contains includes, strings, static tables, and dynamic tables. It is located in the resources directory. [Name]

Output: Resource Resource

WebCenter Content | TEAM Informatics blog


Input: [File] *_template.hda [Description] A template definition file that points to the custom template resource files defined for a component. Typically located in the templates directory. [Name]

Output: Template Resource

WebCenter Content | TEAM Informatics blog


Input: [File] *_template.htm [Description] A resource file that defines a function or procedure that is performed by the content server. Typically located in the resources directory. [Name]

Output: Template Page

WebCenter Content | TEAM Informatics blog


Input: [File] *_service.htm [Description] Defines a function or procedure that is performed by the content server. [Name]

Output: Service Resource

WebCenter Content | TEAM Informatics blog


Input: [File] *_query.htm [Description] Defines SQL queries. These can be specified in a service resource directly but this allows for reusability. [Name]

Output: Query Resource

WebCenter Content | TEAM Informatics blog


Input: [Name] union [Required handler(s)] guf, iuf [Description]

Output: Taking the union of N elements in a specific manner


Input: [Name] fib [Required handler(s)] fib [Description]

Output: Calculates the first N Fibonacci numbers


Input: [Name] primes [Required handler(s)] primes [Description]

Output: Calculates prime numbers up to N


Input: [Name] leq [Required handler(s)] leq [Description]

Output: Solves a circular chain of N lesser-than-or-equal variables


Input: [Name] bool [Required handler(s)] bool [Description]

Output: N-digit binary addition


Input: [Name] mergesort [Required handler(s)] mergesort [Description]

Output: Sorts an array N times using a mergesort algorithm


Input: [Name] dijkstra [Required handler(s)] dijkstra (and fib_heap) [Description]

Output: Calculates the shortest path in several Hamiltonian cycles. For more information, please consult the paper by Jon Sneyers et al. [extented report]


Input: [Name] ram [Required handler(s)] ram [Description]

Output: Counts from 1 to N on a simulated RAM machine


Input: [Field Name] FP Project Type [Entity] Project [Type] Text [Lookup Table]

Output: FP Project Type

Microsoft Project Server 2010 / 2013 / Online Implementer


Input: [Field Name] Portfolio [Entity] Project [Type] Text [Lookup Table]

Output: Portfolio

Microsoft Project Server 2010 / 2013 / Online Implementer


Input: [Field Name] Program [Entity] Project [Type] Text [Lookup Table]

Output: Program

Microsoft Project Server 2010 / 2013 / Online Implementer


Input: [Field Name] Resource Role [Entity] Resource [Type] Text [Lookup Table]

Output: Resource Role

Microsoft Project Server 2010 / 2013 / Online Implementer


Input: [Field Name] Status - Budget [Entity] Project [Type] Text [Lookup Table]

Output: FP Indicator

Microsoft Project Server 2010 / 2013 / Online Implementer


Input: [Field Name] Status - Quality [Entity] Project [Type] Text [Lookup Table]

Output: FP Indicator

Microsoft Project Server 2010 / 2013 / Online Implementer


Input: [Field Name] Status - Resources [Entity] Project [Type] Text [Lookup Table]

Output: FP Indicator

Microsoft Project Server 2010 / 2013 / Online Implementer


Input: [Field Name] Status - Schedule [Entity] Project [Type] Text [Lookup Table]

Output: FP Indicator

Microsoft Project Server 2010 / 2013 / Online Implementer


Input: [Field Name] Status - Scope [Entity] Project [Type] Text [Lookup Table]

Output: FP Indicator

Microsoft Project Server 2010 / 2013 / Online Implementer


Input: [Name] accessibilityFeatures [Since] 37 [Description]

Output: Use the chrome.accessibilityFeatures API to manage Chrome's accessibility features. This API relies on the ChromeSetting prototype of the type API for getting and setting individual accessibility features. In order to get feature states the extension must request accessibilityFeatures.read permission. For modifying feature state, the extension needs accessibilityFeatures.modify permission. Note that accessibilityFeatures.modify does not imply accessibilityFeatures.read permission.


Input: [Name] alarms [Since] 22 [Description]

Output: Use the chrome.alarms API to schedule code to run periodically or at a specified time in the future.


Input: [Name] app.runtime [Since] 23 [Description]

Output: Use the chrome.app.runtime API to manage the app lifecycle. The app runtime manages app installation, controls the event page, and can shut down the app at anytime.


Input: [Name] app.window [Since] 23 [Description]

Output: Use the chrome.app.window API to create windows. Windows have an optional frame with title bar and size controls. They are not associated with any Chrome browser windows. See the Window State Sample for a demonstration of these options.


Input: [Name] bluetooth [Since] 37 [Description]

Output: Use the chrome.bluetooth API to connect to a Bluetooth device. All functions report failures via chrome.runtime.lastError.


Input: [Name] bluetoothLowEnergy [Since] 37 [Description]

Output: The chrome.bluetoothLowEnergy API is used to communicate with Bluetooth Smart (Low Energy) devices using the Generic Attribute Profile (GATT).


Input: [Name] bluetoothSocket [Since] 37 [Description]

Output: Use the chrome.bluetoothSocket API to send and receive data to Bluetooth devices using RFCOMM and L2CAP connections.


Input: [Name] browser [Since] 42 [Description]

Output: Use the chrome.browser API to interact with the Chrome browser associated with the current application and Chrome profile.


Input: [Name] commands [Since] 35 [Description]

Output: Use the commands API to add keyboard shortcuts that trigger actions in your extension, for example, an action to open the browser action or send a command to the extension.


Input: [Name] contextMenus [Since] 6 [Description]

Output: Use the chrome.contextMenus API to add items to Google Chrome's context menu. You can choose what types of objects your context menu additions apply to, such as images, hyperlinks, and pages.


Input: [Name] documentScan [Since] 44 [Description]

Output: Use the chrome.documentScan API to discover and retrieve images from attached paper document scanners.


Input: [Name] events [Since] 21 [Description]

Output: The chrome.events namespace contains common types used by APIs dispatching events to notify you when something interesting happens.


Input: [Name] extensionTypes [Since] 39 [Description]

Output: The chrome.extensionTypes API contains type declarations for Chrome extensions.


Input: [Name] fileSystem [Since] 23 [Description]

Output: Use the chrome.fileSystem API to create, read, navigate, and write to the user's local file system. With this API, Chrome Apps can read and write to a user-selected location. For example, a text editor app can use the API to read and write local documents. All failures are notified via chrome.runtime.lastError.


Input: [Name] fileSystemProvider [Since] 40 [Description]

Output: Use the chrome.fileSystemProvider API to create file systems, that can be accessible from the file manager on Chrome OS.


Input: [Name] gcm [Since] 35 [Description]

Output: Use chrome.gcm to enable apps and extensions to send and receive messages through the Google Cloud Messaging Service.


Input: [Name] hid [Since] 38 [Description]

Output: Use the chrome.hid API to interact with connected HID devices. This API provides access to HID operations from within the context of an app. Using this API, apps can function as drivers for hardware devices. Errors generated by this API are reported by setting runtime.lastError and executing the function's regular callback. The callback's regular parameters will be undefined in this case.


Input: [Name] i18n [Since] 5 [Description]

Output: Use the chrome.i18n infrastructure to implement internationalization across your whole app or extension.


Input: [Name] identity [Since] 29 [Description]

Output: Use the chrome.identity API to get OAuth2 access tokens.


Input: [Name] idle [Since] 6 [Description]

Output: Use the chrome.idle API to detect when the machine's idle state changes.


Input: [Name] mdns [Since] 31 [Description]

Output: Use the chrome.mdns API to discover services over mDNS. This comprises a subset of the features of the NSD spec: http://www.w3.org/TR/discovery-api/


Input: [Name] mediaGalleries [Since] 23 [Description]

Output: Use the chrome.mediaGalleries API to access media files (audio, images, video) from the user's local disks (with the user's consent).


Input: [Name] notifications [Since] 28 [Description]

Output: Use the chrome.notifications API to create rich notifications using templates and show these notifications to users in the system tray.


Input: [Name] permissions [Since] 16 [Description]

Output: Use the chrome.permissions API to request declared optional permissions at run time rather than install time, so users understand why the permissions are needed and grant only those that are necessary.


Input: [Name] power [Since] 27 [Description]

Output: Use the chrome.power API to override the system's power management features.


Input: [Name] printerProvider [Since] 44 [Description]

Output: The chrome.printerProvider API exposes events used by print manager to query printers controlled by extensions, to query their capabilities and to submit print jobs to these printers.


Input: [Name] runtime [Since] 22 [Description]

Output: Use the chrome.runtime API to retrieve the background page, return details about the manifest, and listen for and respond to events in the app or extension lifecycle. You can also use this API to convert the relative path of URLs to fully-qualified URLs.


Input: [Name] serial [Since] 23 [Description]

Output: Use the chrome.serial API to read from and write to a device connected to a serial port.


Input: [Name] socket [Since] 24 [Description]

Output: Use the chrome.socket API to send and receive data over the network using TCP and UDP connections. Note: Starting with Chrome 33, this API is deprecated in favor of the sockets.udp, sockets.tcp and sockets.tcpServer APIs.


Input: [Name] sockets.tcp [Since] 33 [Description]

Output: Use the chrome.sockets.tcp API to send and receive data over the network using TCP connections. This API supersedes the TCP functionality previously found in the chrome.socket API.


Input: [Name] sockets.tcpServer [Since] 33 [Description]

Output: Use the chrome.sockets.tcpServer API to create server applications using TCP connections. This API supersedes the TCP functionality previously found in the chrome.socket API.


Input: [Name] sockets.udp [Since] 33 [Description]

Output: Use the chrome.sockets.udp API to send and receive data over the network using UDP connections. This API supersedes the UDP functionality previously found in the "socket" API.


Input: [Name] storage [Since] 20 [Description]

Output: Use the chrome.storage API to store, retrieve, and track changes to user data.


Input: [Name] syncFileSystem [Since] 27 [Description]

Output: Use the chrome.syncFileSystem API to save and synchronize data on Google Drive. This API is NOT for accessing arbitrary user docs stored in Google Drive. It provides app-specific syncable storage for offline and caching usage so that the same data can be available across different clients. Read Manage Data for more on using this API.


Input: [Name] system.cpu [Since] 32 [Description]

Output: Use the system.cpu API to query CPU metadata.


Input: [Name] system.display [Since] 30 [Description]

Output: Use the system.display API to query display metadata.


Input: [Name] system.memory [Since] 32 [Description]

Output: The chrome.system.memory API.


Input: [Name] system.network [Since] 33 [Description]

Output: Use the chrome.system.network API.


Input: [Name] system.storage [Since] 30 [Description]

Output: Use the chrome.system.storage API to query storage device information and be notified when a removable storage device is attached and detached.


Input: [Name] tts [Since] 14 [Description]

Output: Use the chrome.tts API to play synthesized text-to-speech (TTS). See also the related ttsEngine API, which allows an extension to implement a speech engine.


Input: [Name] types [Since] 13 [Description]

Output: The chrome.types API contains type declarations for Chrome.


Input: [Name] usb [Since] 26 [Description]

Output: Use the chrome.usb API to interact with connected USB devices. This API provides access to USB operations from within the context of an app. Using this API, apps can function as drivers for hardware devices. Errors generated by this API are reported by setting runtime.lastError and executing the function's regular callback. The callback's regular parameters will be undefined in this case.


Input: [Name] vpnProvider [Since] 43 [Description]

Output: Use the chrome.vpnProvider API to implement a VPN client.


Input: [Name] wallpaper [Since] 43 [Description]

Output: Use the chrome.wallpaper API to change the ChromeOS wallpaper.


Input: [Bit set] 0 [Increment] 1 [Severity] Information [Comments] Image perfectly round [Event]

Output: Orientation calculation failed


Input: [Bit set] 1 [Increment] 2 [Severity] Information [Comments] Image perfectly straight [Event]

Output: Ellipticity calculation failed


Input: [Bit set] 2 [Increment] 4 [Severity] Warning [Comments] Image split into too many fragments [Event]

Output: Image too multiple for deblending


Input: [Bit set] 4 [Increment] 16 [Severity] Information [Comments] Image has pixels brighter than highest areal profile level [Event]

Output: Bright image


Input: [Bit set] 6 [Increment] 64 [Severity] Warning [Comments] Image has area greater than maximum specified for deblending [Event]

Output: Large image


Input: [Bit set] 7 [Increment] 128 [Severity] Warning [Comments] Image is in step-wedge/label region [Event]

Output: Possible bad image


Input: [Bit set] 10 [Increment] 1024 [Severity] Warning [Comments] Image may be spurious due to bright star artifact [Event]

Output: Image near very bright star


Input: [Bit set] 11 [Increment] 2048 [Severity] Strong warning [Comments] Image is likely spurious result of bright star halo [Event]

Output: Halo artifact


Input: [Bit set] 13 [Increment] 8192 [Severity] Strong warning [Comments] Image is likely spurious result of a bright star diffraction spike [Event]

Output: Diffraction spike artifact


Input: [Bit set] 14 [Increment] 16384 [Severity] Strong warning [Comments] Image is likely spurious result of satellite/'plane/scratch track [Event]

Output: Track artifact


Input: [Bit set] 16 [Increment] 65536 [Severity] Severe defect [Comments] Image pixels partially missing [Event]

Output: Image touches boundary


Input: [Name] name [Values] string [Required] Yes [Default] None [Description]

Output: Hostname of client. This needs to be the name (probably FQDN) returned by a reverse lookup on the connecting IP address.


Input: [Name] profile [Values] string [Required] Yes [Default] None [Description]

Output: Profile group name to associate this client with.


Input: [Name] address [Values] string [Required] No [Default] None [Description]

Output: Establishes an extra IP address that resolves to this client.


Input: [Name] auth [Values] cert+password | bootstrap | cert [Required] No [Default] cert+password [Description]

Output: Authentication mode for the client. See Authentication for details on the values available.


Input: [Name] floating [Values] true | false [Required] No [Default] false [Description]

Output: Allows requests to come from any IP address, rather than requiring requests to come from an IP associated with this client. Note that, since this forces the Bcfg2 server to trust any connection that claims to be from this hostname, it can introduce security issues.


Input: [Name] location [Values] string [Required] No [Default] None [Description]

Output: Deprecated. Use floating instead.


Input: [Name] password [Values] string [Required] No [Default] None [Description]

Output: Establishes a per-client password that can be used instead of the global password.


Input: [Name] pingable [Values] string [Required] No [Default] None [Description]

Output: Deprecated.


Input: [Name] pingtime [Values] string [Required] No [Default] None [Description]

Output: Deprecated.


Input: [Name] secure [Values] true | false [Required] No [Default] false [Description]

Output: Requires the use of password for this client.


Input: [Name] uuid [Values] string [Required] No [Default] None [Description]

Output: Establishes a name for this cilent that can be used to bypass dns-based client resolution.


Input: [Name] version [Values] token [Required] No [Default] None [Description]

Output: The version of the Bcfg2 client running on this machine. You should not have to set this manually, but can let the Bcfg2 server set it automatically.


Input: [Command] CMD_FLUSH [Command Operation]

Output: Remove all queued requests for the printer device. Does not affect active requests.

Printer Device - AmigaOS Documentation Wiki


Input: [Command] CMD_RESET [Command Operation]

Output: Reset the printer device to its initialized state. All active and queued I/O requests will be aborted.

Printer Device - AmigaOS Documentation Wiki


Input: [Command] CMD_START [Command Operation]

Output: Restart all paused I/O requests

Printer Device - AmigaOS Documentation Wiki


Input: [Command] CMD_STOP [Command Operation]

Output: Pause all active and queued I/O requests.

Printer Device - AmigaOS Documentation Wiki


Input: [Command] CMD_WRITE [Command Operation]

Output: Write out a stream of characters to the printer device. The number of characters can be specified or a NULL-terminated string can be sent.

Printer Device - AmigaOS Documentation Wiki


Input: [Command] PRD_DUMPRPORT [Command Operation]

Output: Dump the specified RastPort to a graphics printer.

Printer Device - AmigaOS Documentation Wiki


Input: [Command] PRD_PRTCOMMAND [Command Operation]

Output: Send a command to the printer.

Printer Device - AmigaOS Documentation Wiki


Input: [Command] PRD_QUERY [Command Operation]

Output: Return the status of the printer port’s lines and registers.

Printer Device - AmigaOS Documentation Wiki


Input: [Command] PRD_RAWWRITE [Command Operation]

Output: Send unprocessed output to the the printer.

Printer Device - AmigaOS Documentation Wiki


Input: [j/k] space/shift-space moves the page down/up [item down/up]

Output: page down/up


Input: [j/k] n/p in list view, selects the next item without opening it [item down/up]

Output: scan down/up


Input: [j/k] o in list view, expands or collapses the selected item [item down/up]

Output: open/close item


Input: [j/k] enter in list view, expands or collapses the selected item [item down/up]

Output: open/close item


Input: [j/k] s stars the selected item [item down/up]

Output: toggle star


Input: [j/k] shift-s shares the selected item [item down/up]

Output: toggle share


Input: [j/k] m switches the read state of the selected item [item down/up]

Output: mark as read/unread


Input: [j/k] t opens the tagging field for the selected item [item down/up]

Output: tag an item


Input: [j/k] v opens the original source for this article in a new window [item down/up]

Output: view original


Input: [j/k] shift-a marks all items in the current view as read [item down/up]

Output: mark all as read


Input: [j/k] 1 displays the subscription as expanded items [item down/up]

Output: expanded view


Input: [j/k] 2 displays the subscription as a list of headlines [item down/up]

Output: list view


Input: [j/k] r refreshes the unread counts in the navigation [item down/up]

Output: refresh


Input: [j/k] shift-n/p selects the next/previous subscription or folder in the navigation [item down/up]

Output: navigation down/up


Input: [j/k] shift-x expand or collapse a folder selected in the navigation [item down/up]

Output: navigation expand/collapse


Input: [j/k] shift-o opens the item currently selected in the navigation [item down/up]

Output: navigation open subscription


Input: [j/k] gh goes to the Google Reader homepage [item down/up]

Output: go to home


Input: [j/k] ga goes to the “All items” view [item down/up]

Output: go to all items


Input: [j/k] gs goes to the “Starred items” view [item down/up]

Output: go to starred items


Input: [j/k] gt allows you to navigate to a tag by entering the tag name [item down/up]

Output: go to tag


Input: [j/k] gu allows you to navigate to a subscription by entering the subscription name [item down/up]

Output: go to subscription


Input: [j/k] u hides and shows the list of subscriptions [item down/up]

Output: toggle full screen mode


Input: [j/k] ? displays a quick guide to all of Reader’s shortcuts [item down/up]

Output: keyboard shortcuts help


Input: [0] 1. [Shortcut] Code Formatting [Eclipse] Ctrl + Shift + F [JDeveloper]

Output: Ctrl + Alt + L

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 2. [Shortcut] Go to line [Eclipse] CTRL + L [JDeveloper]

Output: Ctrl + G

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 3. [Shortcut] Navigation [Eclipse] Alt + left and Alt + Right [JDeveloper]

Output: Alt + left and Alt + Right

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 4. [Shortcut] Open Resource [Eclipse] Ctrl + Shift + R [JDeveloper]

Output: Menu Navigate -> View Type Hierarchy

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 5. [Shortcut] Organize imports [Eclipse] Ctrl + Shift + O [JDeveloper]

Output: Alt + Enter (One at a time) and Ctrl + Alt + O (All at once)

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 6. [Shortcut] Open Type Hierarchy [Eclipse] Ctrl + T [JDeveloper]

Output: Menu Navigate -> View Type Hierarchy

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 7. [Shortcut] Close all Opened documents [Eclipse] Ctrl + Shift + F4 [JDeveloper]

Output: Ctrl + Shift + F4

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 8. [Shortcut] Open declarations [Eclipse] Ctrl + O [JDeveloper]

Output: Don’t know

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 9. [Shortcut] Open Editor [Eclipse] Ctrl + E [JDeveloper]

Output: Don’t know

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 10. [Shortcut] Line Comment [Eclipse] Ctrl + / [JDeveloper]

Output: Ctrl + / Note Ctrl + / without selection will move cursor to the next line

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 11. [Shortcut] Comment your selection using /* and */ [Eclipse] Ctrl + Shift + / [JDeveloper]

Output: Don’t know

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 12. [Shortcut] Rename [Eclipse] Alt + Shift + R [JDeveloper]

Output: Ctrl + Alt + R

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 13. [Shortcut] extract to Local Variable [Eclipse] Alt + Shift + L [JDeveloper]

Output: Ctrl + Alt V or Ctrl + Alt + F

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 14. [Shortcut] extract to Method [Eclipse] Alt + Shift + M [JDeveloper]

Output: Ctrl + Alt + X

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 15. [Shortcut] Open Declaration [Eclipse] F3 [JDeveloper]

Output: Context menu -> Go to Declaration

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 16. [Shortcut] Save your document [Eclipse] Ctrl + S [JDeveloper]

Output: Ctrl + S

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 17. [Shortcut] Reload your project [Eclipse] F5 [JDeveloper]

Output: Press the refresh button

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 18. [Shortcut] Indent your line or selection [Eclipse] Tab or Shift Tab [JDeveloper]

Output: Tab or Shift Tab

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 19. [Shortcut] Code assistence [Eclipse] Ctrl + Space [JDeveloper]

Output: Ctrl + Space

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [0] 20. [Shortcut] list all the shortcuts [Eclipse] Ctrl + Shift + L [JDeveloper]

Output: Don’t know

JDeveloper and Eclipse shortcuts compared « Ikool’s Blogbed


Input: [Keyboard Shortcut] Enter [Mouse Shortcut] left double click middle click [Command]

Output: Write message to primary email address

Contacts Sidebar - Thunderbird extension


Input: [Keyboard Shortcut] Ctrl+Enter [Mouse Shortcut] Ctrl+double left click Ctrl+middle click [Command]

Output: Write message to additional email address

Contacts Sidebar - Thunderbird extension


Input: [Keyboard Shortcut] Shift+Enter [Mouse Shortcut] Shift+left double click Shift+middle click [Command]

Output: Write message in inverted HTML/Plain Text format to primary email address

Contacts Sidebar - Thunderbird extension


Input: [Keyboard Shortcut] Shift+Ctrl+Enter [Mouse Shortcut] Shift+Ctrl+double left click Shift+Ctrl+middle click [Command]

Output: Write message in inverted HTML/Plain Text format to additional email address

Contacts Sidebar - Thunderbird extension


Input: [Keyboard Shortcut] Alt+Enter [Mouse Shortcut] Alt+double left click Alt+middle click [Command]

Output: View properties contacts card

Contacts Sidebar - Thunderbird extension


Input: [Keyboard Shortcut] Delete [Command]

Output: Delete selected contacts

Contacts Sidebar - Thunderbird extension


Input: [Keyboard Shortcut] Insert [Command]

Output: Add new card to address book

Contacts Sidebar - Thunderbird extension


Input: [Meta-character] . (period) [Meaning]

Output: Matches any one character no matter what the character is

Match beginning and end of the filename using meta characters and regex


Input: [Meta-character] ? [Meaning]

Output: Matches the character immediately before it either zero times or one time

Match beginning and end of the filename using meta characters and regex


Input: [Meta-character] * [Meaning]

Output: Matches the character immediately before it any number of times including zero (the character may not be in the string at all)

Match beginning and end of the filename using meta characters and regex


Input: [Meta-character] + [Meaning]

Output: Matches the character immediately before it one or more times (the character must be in the string at least once)

Match beginning and end of the filename using meta characters and regex


Input: [Meta-character] ^ [Meaning]

Output: Indicates that the characters which follow are at the start of the string only

Match beginning and end of the filename using meta characters and regex


Input: [Meta-character] $ [Meaning]

Output: Indicates that the characters which precede it are at the end of the string

Match beginning and end of the filename using meta characters and regex


Input: [Meta-character] \d [Meaning]

Output: Matches any decimal digit

Match beginning and end of the filename using meta characters and regex


Input: [Meta-character] \D [Meaning]

Output: Matches any character that is not a decimal digit

Match beginning and end of the filename using meta characters and regex


Input: [Meta-character] \s [Meaning]

Output: Matches a tab or space character

Match beginning and end of the filename using meta characters and regex


Input: [Meta-character] \S [Meaning]

Output: Matches any character that is not a tab or a space

Match beginning and end of the filename using meta characters and regex


Input: [Meta-character] \w [Meaning]

Output: Matches any letter, any digit, or the underscore character

Match beginning and end of the filename using meta characters and regex


Input: [Meta-character] \W [Meaning]

Output: Matches any character which is not a letter, a digit, or the underscore

Match beginning and end of the filename using meta characters and regex


Input: [Meta-character] \ [Meaning]

Output: Escape character allowing the use of any of the metacharacters with their regular keyboard meaning. For instance, \. matches a period (.) in a regular expression. A period (.) matches any one character no matter what the character is.

Match beginning and end of the filename using meta characters and regex


Input: [0] Supported [Element Name] Cues ¶ [Description]

Output: A top-level element to speed seeking access. All entries are local to the segment.

The WebM Project | WebM Container Guidelines


Input: [0] Supported [Element Name] CuePoint ¶ [Description]

Output: Contains all information relative to a seek point in the segment.

The WebM Project | WebM Container Guidelines


Input: [0] Supported [Element Name] CueTime ¶ [Description]

Output: Absolute timecode according to the segment time base.

The WebM Project | WebM Container Guidelines


Input: [0] Supported [Element Name] CueTrackPositions ¶ [Description]

Output: Contain positions for different tracks corresponding to the timecode.

The WebM Project | WebM Container Guidelines


Input: [0] Supported [Element Name] CueTrack ¶ [Description]

Output: The track for which a position is given.

The WebM Project | WebM Container Guidelines


Input: [0] Supported [Element Name] CueClusterPosition ¶ [Description]

Output: The position of the Cluster containing the required Block.

The WebM Project | WebM Container Guidelines


Input: [0] Supported [Element Name] CueRelativePosition ¶ [Description]

Output: The relative position of the referenced block inside the cluster with 0 being the first possible position for an element inside that cluster.

The WebM Project | WebM Container Guidelines


Input: [0] Supported [Element Name] CueDuration ¶ [Description]

Output: The duration of the block according to the segment time base. If missing the track's DefaultDuration does not apply and no duration information is available in terms of the cues.

The WebM Project | WebM Container Guidelines


Input: [0] Supported [Element Name] CueBlockNumber ¶ [Description]

Output: Number of the Block in the specified Cluster.

The WebM Project | WebM Container Guidelines


Input: [0] Unsupported [Element Name] CueCodecState ¶ [Description]

Output: The position of the Codec State corresponding to this Cue element. 0 means that the data is taken from the initial Track Entry.

The WebM Project | WebM Container Guidelines


Input: [0] Unsupported [Element Name] CueReference ¶ [Description]

Output: The Clusters containing the required referenced Blocks.

The WebM Project | WebM Container Guidelines


Input: [0] Unsupported [Element Name] CueRefTime ¶ [Description]

Output: Timecode of the referenced Block.

The WebM Project | WebM Container Guidelines


Input: [0] Unsupported [Element Name] CueRefCluster ¶ [Description]

Output: Position of the Cluster containing the referenced Block.

The WebM Project | WebM Container Guidelines


Input: [0] Unsupported [Element Name] CueRefNumber ¶ [Description]

Output: Number of the referenced Block of Track X in the specified Cluster.

The WebM Project | WebM Container Guidelines


Input: [0] Unsupported [Element Name] CueRefCodecState ¶ [Description]

Output: The position of the Codec State corresponding to this referenced element. 0 means that the data is taken from the initial Track Entry.

The WebM Project | WebM Container Guidelines


Input: [field name] s_inodes_count [type] ULONG [comment]

Output: Count of inodes in the filesystem


Input: [field name] s_blocks_count [type] ULONG [comment]

Output: Count of blocks in the filesystem


Input: [field name] s_r_blocks_count [type] ULONG [comment]

Output: Count of the number of reserved blocks


Input: [field name] s_free_blocks_count [type] ULONG [comment]

Output: Count of the number of free blocks


Input: [field name] s_free_inodes_count [type] ULONG [comment]

Output: Count of the number of free inodes


Input: [field name] s_first_data_block [type] ULONG [comment]

Output: The first block which contains data


Input: [field name] s_log_block_size [type] ULONG [comment]

Output: Indicator of the block size


Input: [field name] s_log_frag_size [type] LONG [comment]

Output: Indicator of the size of the fragments


Input: [field name] s_blocks_per_group [type] ULONG [comment]

Output: Count of the number of blocks in each block group


Input: [field name] s_frags_per_group [type] ULONG [comment]

Output: Count of the number of fragments in each block group


Input: [field name] s_inodes_per_group [type] ULONG [comment]

Output: Count of the number of inodes in each block group


Input: [field name] s_mtime [type] ULONG [comment]

Output: The time that the filesystem was last mounted


Input: [field name] s_wtime [type] ULONG [comment]

Output: The time that the filesystem was last written to


Input: [field name] s_mnt_count [type] USHORT [comment]

Output: The number of times the file system has been mounted


Input: [field name] s_max_mnt_count [type] SHORT [comment]

Output: The number of times the file system can be mounted


Input: [field name] s_magic [type] USHORT [comment]

Output: Magic number indicating ex2fs


Input: [field name] s_state [type] USHORT [comment]

Output: Flags indicating the current state of the filesystem


Input: [field name] s_errors [type] USHORT [comment]

Output: Flags indicating the procedures for error reporting


Input: [field name] s_pad [type] USHORT [comment]

Output: padding


Input: [field name] s_lastcheck [type] ULONG [comment]

Output: The time that the filesystem was last checked


Input: [field name] s_checkinterval [type] ULONG [comment]

Output: The maximum time permissible between checks


Input: [field name] s_creator_os [type] ULONG [comment]

Output: Indicator of which OS created the filesystem


Input: [field name] s_rev_level [type] ULONG [comment]

Output: The revision level of the filesystem


Input: [field name] s_reserved [type] ULONG[235] [comment]

Output: padding to 1024 bytes


Input: [Item] Value: [Value]

Output: 13,272


Input: [Item] Indicator: [Value]

Output: Number of new notified cases of incapacity for work


Input: [Item] Subject specification: [Value]

Output: Aggregation: Total


Input: [Item] Unit of measure: [Value]

Output: not applicable


Input: [Item] Type of release: [Value]

Output: Final with no further revision


Input: [Item] Region: [Value]

Output: Žďár nad Sázavou


Input: [Item] Period: [Value]

Output: Year 2010


Input: [Parameter] Uninstall [Description]

Output: Name of the program; .exe is implied. You may have to use a fully qualified file path if Uninstall.exe is located in a folder that does not appear in your PATH environment variable. Use the appropriate version for a specific system: one of UninstallA.exe, UninstallW.exe, or UninstallX64.exe. See the notes at the beginning of this page.

Uninstall - Uninstall a program from the command line


Input: [Parameter] /a [Description]

Output: Show all registrations, including hidden ones. Without this parameter, only uninstaller registrations that are visible in the Add/Remove Programs control panel are shown.

Uninstall - Uninstall a program from the command line


Input: [Parameter] /c [Description]

Output: Check and display the uninstall command, but don't run anything. In conjunction with a keyname, this option will display the uninstall command or the quiet uninstall command (see /q option, below) for that uninstall key; without a keyname, the uninstall commands for all registered entries are shown.

Uninstall - Uninstall a program from the command line


Input: [Parameter] /f [Description]

Output: Show full registration entries instead of a summary. By default, Uninstall will show a one-line summary for each registered uninstaller; with the /f option, Uninstall displays all information available for each registered uninstaller.

Uninstall - Uninstall a program from the command line


Input: [Parameter] /l [Description]

Output: List the uninstall information for the given keyname registration. By default, this only displays the associated display name and version; if you also specify the /f option, then all uninstall information for keyname is displayed.

Uninstall - Uninstall a program from the command line


Input: [Parameter] /q [Description]

Output: Display or run the quiet uninstall command (without user interaction). By default, Uninstall will run or display the interactive uninstaller command for the given keyname; with the /q parameter, the "quiet" command is used instead. Note: Uninstall will use the registered "quiet" uninstall command if available. If not, then Uninstall will add the appropriate command line option for non-interactive uninstallation to MSI, Tarma, or Inno Setup uninstaller command lines. For other uninstallers, Uninstall will fail if no quiet command is registered.

Uninstall - Uninstall a program from the command line


Input: [Parameter] /w [Description]

Output: Wait for uninstaller to terminate. By default, Uninstall starts an uninstaller and then abandons it; with the /w option, Uninstall will wait for the uninstaller process to terminate. Note: Uninstall only waits for the original uninstaller process to terminate. If the uninstaller starts a secondary process, then this will not be detected by Uninstall.

Uninstall - Uninstall a program from the command line


Input: [Parameter] keyname... [Description]

Output: Specifies the uninstaller's registry key name for the application you wish to uninstall. The key name is usually a GUID like {CE2CDD62-0124-36CA-84D3-9F4DCF5C5BD9}, or sometimes a symbolic name like Microsoft Document Explorer 2008. If the key name contains spaces, it must be "quoted". You may specify more than one key name; Uninstall will run or display each one in turn.

Uninstall - Uninstall a program from the command line


Input: [Type #] 1 [LSA Name] Router [Description]

Output: A router sends this to describe neighbors and its own interfaces.

Types of link-state advertisements (LSAs) used in Open Shortest Path First (OSPF)


Input: [Type #] 2 [LSA Name] Network [Description]

Output: For broadcast networks only; the designated router for the broadcast segment uses this to list all the routers connected to the segment directly.

Types of link-state advertisements (LSAs) used in Open Shortest Path First (OSPF)


Input: [Type #] 3 [LSA Name] Summary [Description]

Output: A router touching multiple areas of the network uses this to summarize information about one of those areas to update the other areas.

Types of link-state advertisements (LSAs) used in Open Shortest Path First (OSPF)


Input: [Type #] 4 [LSA Name] ASBR-summary [Description]

Output: Sent by a border router that has sent a Type 5 LSA to describe how to get to that border router via the internal network.

Types of link-state advertisements (LSAs) used in Open Shortest Path First (OSPF)


Input: [Type #] 5 [LSA Name] AS-external [Description]

Output: Sent by a border router to describe external routes through itself. Can be used to advertise "this is the way to (all or part of) the Internet."

Types of link-state advertisements (LSAs) used in Open Shortest Path First (OSPF)


Input: [Type #] 6 [LSA Name] Group membership [Description]

Output: Used in a now obsolete multicast version of Multicast Open Shortest Path First (MOSPF). Most routers no longer support MOSPF; this LSA may be reassigned in the future.

Types of link-state advertisements (LSAs) used in Open Shortest Path First (OSPF)


Input: [Type #] 7 [LSA Name] NSSA External [Description]

Output: OSPF stub areas are those without a direct path to the outside; they do not allow Type 5 LSAs in, and all externally bound traffic is just routed out through the stub area’s boundary router. A “not so stubby area” (NSSA) has some limited external routes available; they are advertised within the NSSA using Type 7 LSAs. The NSSA’s boundary routers translated Type 7 LSAs into Type 5 LSAs to flood into adjacent areas.

Types of link-state advertisements (LSAs) used in Open Shortest Path First (OSPF)


Input: [Type #] 8 [LSA Name] External Attributes [Description]

Output: In OSPFv2, this was used to convey BGP link attributes into an OSPF network, but it was rarely implemented. In OSPFv3, it has been repurposed to send information about all of the IPv6 address information associated with the local link.

Types of link-state advertisements (LSAs) used in Open Shortest Path First (OSPF)


Input: [Type #] 9 [LSA Name] Intra-Area-Prefix (was Link-local Opaque) [Description]

Output: Communicates prefixes for stub areas and for transit networks, in OSPFv3. (In OSPFv2, it was a link-local “opaque” field, conveying information passed on by OSPF routers but not used for OSPF routing.)

Types of link-state advertisements (LSAs) used in Open Shortest Path First (OSPF)


Input: [Type #] 10 [LSA Name] Area-Local Opaque [Description]

Output: Flooded to area routers even if the router doesn’t understand the information within. Used by applications to extend OSPF functionality, e.g. for MPLS traffic engineering.

Types of link-state advertisements (LSAs) used in Open Shortest Path First (OSPF)


Input: [Type #] 11 [LSA Name] AS Opaque [Description]

Output: Like a Type 10, is not flooded into stubs, as with Type 5 LSAs.

Types of link-state advertisements (LSAs) used in Open Shortest Path First (OSPF)


Input: [Variable] SCON [Description]

Output: Solar constant

Near-modern climate simulations | Atmosphere | CESM | Community Earth System Model


Input: [Variable] CO2VM2 [Description]

Output: CO2 volume mixing ratio

Near-modern climate simulations | Atmosphere | CESM | Community Earth System Model


Input: [Variable] CH4VMR [Description]

Output: CH4 volume mixing ratio

Near-modern climate simulations | Atmosphere | CESM | Community Earth System Model


Input: [Variable] N20VMR [Description]

Output: N2O volume mixing ratio

Near-modern climate simulations | Atmosphere | CESM | Community Earth System Model


Input: [Variable] F11VMR1 [Description]

Output: CFC11 volume mixing ratio

Near-modern climate simulations | Atmosphere | CESM | Community Earth System Model


Input: [Variable] F12VMR1 [Description]

Output: CFC12 volume mixing ration

Near-modern climate simulations | Atmosphere | CESM | Community Earth System Model


Input: [Mode] Any mode, use low frequency like 3-4Hz [Task]

Output: Blinking LED


Input: [Mode] Any mode, use frequency greater then 50Hz [Task]

Output: Control brightness of light


Input: [Mode] Phase Correct [Task]

Output: Servo


Input: [Mode] Phase Correct, higher frequency better, limited by external components. [Task]

Output: Motor speed


Input: [Mode] Phase and Frequency Correct or CTC (for timer0/2), change frequency to generate different notes. [Task]

Output: Generate sounds


Input: [Mode] Fast PWM, higher frequency better. [Task]

Output: Digital to Analog converters


Input: [Column definition option] id [Default] – [Description]

Output: Column ID.


Input: [Column definition option] name [Default] – [Description]

Output: Column name to put in the header.


Input: [Column definition option] field [Default] – [Description]

Output: Property of the data context to bind to.


Input: [Column definition option] formatter [Default] defaultFormatter [Description]

Output: Function responsible for rendering the contents of a cell.


Input: [Column definition option] editor [Default] – [Description]

Output: An Editor class responsible for editing the value of a cell.


Input: [Column definition option] validator [Default] – [Description]

Output: An extra validation function to be passed to the editor.


Input: [Column definition option] unselectable [Default] false [Description]

Output: If true, the cell cannot be selected (and therefore edited).


Input: [Column definition option] cannotTriggerInsert [Default] false [Description]

Output: If true, a new row cannot be created from just the value of this cell.


Input: [Column definition option] setValueHandler [Default] – [Description]

Output: A custom function to be called to set field value instead of setting contextfield


Input: [Column definition option] width [Default] Options.defaultColumnWidth [Description]

Output: Width of the column in pixels.


Input: [Column definition option] resizable [Default] true [Description]

Output: If false, the column cannot be resized.


Input: [Column definition option] minWidth [Default] – [Description]

Output: Minimum allowed column width for resizing.


Input: [Column definition option] maxWidth [Default] – [Description]

Output: Maximum allowed column width for resizing.


Input: [Column definition option] cssClass [Default] – [Description]

Output: A CSS class to add to the cell.


Input: [Column definition option] rerenderOnResize [Default] false [Description]

Output: Rerender the column when it is resized (useful for columns relying on cell width or adaptive formatters).


Input: [position] right upper [color] blue [function]

Output: electrical,biomedical and communication connector

Apollo Space Suit(A7LB PGA) | APOLLO MANIACS


Input: [position] right middle [color] blue [function]

Output: oxygen inlet

Apollo Space Suit(A7LB PGA) | APOLLO MANIACS


Input: [position] right lower [color] red [function]

Output: exhaust outlet

Apollo Space Suit(A7LB PGA) | APOLLO MANIACS


Input: [position] left upper [color] blue [function]

Output: double water connector

Apollo Space Suit(A7LB PGA) | APOLLO MANIACS


Input: [position] left middle [color] blue [function]

Output: oxygen inlet

Apollo Space Suit(A7LB PGA) | APOLLO MANIACS


Input: [position] left lower [color] red [function]

Output: exhaust outlet

Apollo Space Suit(A7LB PGA) | APOLLO MANIACS


Input: [File Location] \Data\Local\ [File Name] BuffEffect.bmd [Description] Effects that are done by some Item or during some event [Why to edit?]

Output: Translation(Name and Description columns)

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] Credit.bmd [Description] Names of jobs and people that are created the game (In game if you click on credits you will see them) [Why to edit?]

Output: If you want your name also appear there :D

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] Dialog.bmd [Description] All Texts that NPC says to player(Like when talking about quests) [Why to edit?]

Output: Translation(Message and Event Messages columns) Also in 9 row there is Home Page name.

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] Filter.bmd [Description] All Words that client will not display in Game(like bad words) [Why to edit?]

Output: If you want to add more words that players will not see if someone write them

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] FilterName.bmd [Description] All not allowed character names to be created [Why to edit?]

Output: Add names that same as admins names - that players will not try to look like admin

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\ [File Name] Gate.bmd [Description] The gates that move player from one map to another map [Why to edit?]

Output: If you want to add new gates. After editing you should export it to server side gate.txt(usually in server data folder) that it will match.

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] Item.bmd [Description] Names and configuration of items in the game. [Why to edit?]

Output: Translation or adding new items. You also can edit item.txt in your server(usually in server data folder) and then import it to your clients item.bmd - that both server and client files will match. If you decide to edit item.bmd and export to server side item.txt - then you should follow guide of special export using missing values editors - because in item.bmd is not enough information for creating server side item.txt

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] ItemAddOption.bmd [Description] Stored configuration of Options for 380lvl Items, or Halloween and Cherry Blossoms event option or Partial charge option [Why to edit?]

Output: If you want to add more items options, I suggest to edit in server side ItemAddOption.txt file, and then to import to clients bmd file.

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] ItemSetOption.bmd [Description] Configuration of Ancient Sets that in the game(For each set what options available with what value) [Why to edit?]

Output: If you want to add more ancient sets or rename sets names. You need that server side itemsetoption.txt will be same(after editing you can exports for server side file)

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] ItemSetType.bmd [Description] Configuration of items that belong to ancient sets [Why to edit?]

Output: If you want to add\remove some items from ancient sets. The row number in that file matches to items row number in item.bmd. Set type number matches to ancitent set number in ItemSetOption file. You need that server side itemsettype.txt will be same(after editing you can export for server side file)

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] JewelOfHarmonyOption.bmd [Description] Configuration of option that are added with jewel of harmony [Why to edit?]

Output: Translation or configuation change(like price that needed to pay for level up) You need that server side JewelOfHarmonyOption.txt will be same(after editing you can export for server side file)

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] JewelOfHarmonySmelt.bmd [Description] Configuration of items that can have options of jewel of harmony. [Why to edit?]

Output: Adding items to have jewel of harmony options . The row number in that file matches to items row number in item.bmd. You need that server side JewelOfHarmonySmelt.txt will be same(after editing you can export for server side file)

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] Mix.bmd [Description] Configuration of Mixes [Why to edit?]

Output: Very complicated to edit.

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] MoveReq.bmd [Description] Movements of player by the M menu [Why to edit?]

Output: Change names, add new movements. You need that server side movereq.txt will be same(after editing you can export for server side file)

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] NPCDialogue.bmd [Description] Texts that NPC says [Why to edit?]

Output: Translation

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] Quest.bmd [Description] Configuration of quests [Why to edit?]

Output: Translate quest names. Quest configuration complicated to edit. but theoretical it is possible to add new quests like find item\kill monsters

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] QuestWords.bmd [Description] Texts from quests [Why to edit?]

Output: Translation

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] ServerList.bmd [Description] List with server names [Why to edit?]

Output: Changing displayed server names

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] ShopUI.bmd [Description] Configuation of interface of the shop [Why to edit?]

Output: Translation

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] Skill.bmd [Description] Configuation of skills [Why to edit?]

Output: Translation or changing configuration of skills

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] Slide.bmd [Description] Text that a running as slides in button of the screen(have some tips to new players) [Why to edit?]

Output: Translation or adding your own text

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] SocketItem.bmd [Description] Socket Item configuration [Why to edit?]

Output: Translation of socket items names\texts

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\Local\ [File Name] Text.bmd [Description] Have the most of the texts that are in the game, including server names that displayed to player in main screen or servers home page addresses [Why to edit?]

Output: Translation or change of some texts

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Name] message.wtf [Description] Have text that used by webzen mu.exe launcher [Why to edit?]

Output: If you use webzen mu.exe launcher that you can translate or change addresses of pages to yours.

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\World##\ [File Name] minimap.bmd [Description] Texts that shown on minimap [Why to edit?]

Output: Translation

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\World##\ [File Name] *.obj [Description] In that file are location and rotation of objects in the map [Why to edit?]

Output: Adding objects of your own to map

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\World##\ [File Name] *.map [Description] In that file are the look of the ground of each map(like grass,rocks,road, water) [Why to edit?]

Output: Changing the ground of the map

MuOnline Files Description - MuOnline Pentium Tools


Input: [File Location] \Data\World##\ [File Name] *.att [Description] In that file are where player allowed to walk, where it is a safe zone, or where player will see just nothing(black ground) [Why to edit?]

Output: Changing where player allowed to go or where is safe zone.

MuOnline Files Description - MuOnline Pentium Tools


Input: [Feature(s)] .any and Promise.any [Command line identifier]

Output: any

The following features can be disabled


Input: [Feature(s)] .race and Promise.race [Command line identifier]

Output: race

The following features can be disabled


Input: [Feature(s)] .call and .get [Command line identifier]

Output: call_get

The following features can be disabled


Input: [Feature(s)] .filter and Promise.filter [Command line identifier]

Output: filter

The following features can be disabled


Input: [Feature(s)] .map and Promise.map [Command line identifier]

Output: map

The following features can be disabled


Input: [Feature(s)] .reduce and Promise.reduce [Command line identifier]

Output: reduce

The following features can be disabled


Input: [Feature(s)] .props and Promise.props [Command line identifier]

Output: props

The following features can be disabled


Input: [Feature(s)] .settle and Promise.settle [Command line identifier]

Output: settle

The following features can be disabled


Input: [Feature(s)] .some and Promise.some [Command line identifier]

Output: some

The following features can be disabled


Input: [Feature(s)] .nodeify [Command line identifier]

Output: nodeify

The following features can be disabled


Input: [Feature(s)] Promise.coroutine and Promise.spawn [Command line identifier]

Output: generators

The following features can be disabled


Input: [Feature(s)] Progression [Command line identifier]

Output: progress

The following features can be disabled


Input: [Feature(s)] Promisification [Command line identifier]

Output: promisify

The following features can be disabled


Input: [Feature(s)] Cancellation [Command line identifier]

Output: cancel

The following features can be disabled


Input: [Feature(s)] Timers [Command line identifier]

Output: timers

The following features can be disabled


Input: [Feature(s)] Resource management [Command line identifier]

Output: using

The following features can be disabled


Input: [“From” Record Type] I [“To” Record Type] I

Output: Situation can not exist in the system

STATE AGENCY MOVABLE PROPERTY SYSTEM (STAMPS)

Behind The Scene Action Taken By The System


Input: [“From” Record Type] I [“To” Record Type] F

Output: Situation can not exist in the system

STATE AGENCY MOVABLE PROPERTY SYSTEM (STAMPS)

Behind The Scene Action Taken By The System


Input: [“From” Record Type] I [“To” Record Type] U

Output: Situation can not exist in the system

STATE AGENCY MOVABLE PROPERTY SYSTEM (STAMPS)

Behind The Scene Action Taken By The System


Input: [“From” Record Type] I [“To” Record Type] N

Output: The square footage and calculated values will be transferred to the “to” record, causing the “to” record to become an “I” record. Non-calculated exposure values will be handled in accordance with row at the end of this table labeled NON-CALCULATED.

STATE AGENCY MOVABLE PROPERTY SYSTEM (STAMPS)

Behind The Scene Action Taken By The System


Input: [“From” Record Type] F [“To” Record Type] I

Output: Situation can not exist in the system.

STATE AGENCY MOVABLE PROPERTY SYSTEM (STAMPS)

Behind The Scene Action Taken By The System


Input: [“From” Record Type] F [“To” Record Type] F

Output: When the Location code on the REELS lease agency record(s) associated with the “from” record is changed to the “to” loca code, a recalculation will be done on the “to” record. Non-calculated exposure values will be handled in accordance with row at the end of this table labeled NON-CALCULATED.

STATE AGENCY MOVABLE PROPERTY SYSTEM (STAMPS)

Behind The Scene Action Taken By The System


Input: [“From” Record Type] F [“To” Record Type] U

Output: The location code will be deleted from the REELS lease agency record that created the “from” record and a notification will appear on the Workload Screen. (This is to allow you to decide if you want to retain the existing calculated fields on the “U” record or manually change the “U” record to an “N” record so that the REELS Lease Agency Record can initiated the calculated fields upon your manually entering a location code back into the lease record). Non-calculated exposure values will be handled in accordance with row at the end of this table labeled NON-CALCULATED.

STATE AGENCY MOVABLE PROPERTY SYSTEM (STAMPS)

Behind The Scene Action Taken By The System


Input: [Character] âŒ˜ [Unicode code point (hex)] U+2318 [Usage]

Output: Command

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] â‡§ [Unicode code point (hex)] U+21E7 [Usage]

Output: Shift

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] âŒ¥ [Unicode code point (hex)] U+2325 [Usage]

Output: Option

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] âŒ… [Unicode code point (hex)] U+2305 [Usage]

Output: Enter

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] â†© [Unicode code point (hex)] U+21A9 [Usage]

Output: Return

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] âŒƒ [Unicode code point (hex)] U+2303 [Usage]

Output: Control

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] â‡ž [Unicode code point (hex)] U+21DE [Usage]

Output: Page Up

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] â‡Ÿ [Unicode code point (hex)] U+21DF [Usage]

Output: Page Down

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] â†– [Unicode code point (hex)] U+2196 [Usage]

Output: Home

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] â†˜ [Unicode code point (hex)] U+2198 [Usage]

Output: End

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] âŽ‹ [Unicode code point (hex)] U+238B [Usage]

Output: Escape

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] âŒ« [Unicode code point (hex)] U+232B [Usage]

Output: Delete (Backspace)

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] âŒ¦ [Unicode code point (hex)] U+2326 [Usage]

Output: Forward Delete

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] â‡ª [Unicode code point (hex)] U+21EA [Usage]

Output: Caps Lock

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] â [Unicode code point (hex)] U+23CF [Usage]

Output: Eject Media

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] âŒ§ [Unicode code point (hex)] U+2327 [Usage]

Output: No idea.

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] ï£¿ [Unicode code point (hex)] U+F8FF (private use) [Usage]

Output: No idea.

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Character] âŽ‡ [Unicode code point (hex)] U+2387 [Usage]

Output: No idea.

techblog » Blog Archive » Apple keyboard symbols

Table of Apple keyboard symbols


Input: [Link name (provider)] Biography Resource Center Search for authors name and keywords in the title of the article. However, this is NOT the best source to use for finding full text articles since the database only includes some articles of specific journals, Try as last resort. [If screen displays:]

Output: Search screen with search options.

Finding Articles at the Lloyd Sealy Library


Input: [Link name (provider)] EJS - EBSCOhost Journal Services Find and Click on the phrase Available Full Text: Open in New Window. On next screen find and click on the phrase Full Text. On next screen find and click on Display pdf. Article will appear. [If screen displays:]

Output: Abstract only

Finding Articles at the Lloyd Sealy Library


Input: [Link name (provider)] Emerald Select volume and issue. Then find article in the list. Click on VIEW. Page will have the abstract. Scroll to bottom of page to the Choose Format box. Select PFD or HTML. Click on REQUEST DOCUMENT. FullText will appear. [If screen displays:]

Output: List of Volumes or abstract

Finding Articles at the Lloyd Sealy Library


Input: [Link name (provider)] LexisNexis Follow the links and the search will be preset to search the publication you picked. Use words from the title and the authors last name or the date of publication to locate the precise article. [If screen displays:]

Output: Search screen

Finding Articles at the Lloyd Sealy Library


Input: [Link name (provider)] Literature Resource Center NOT the best source to use for finding full text articles since the database only includes some articles from literary journals, depending on the subject. Try as last resort. [If screen displays:]

Output: Search screen

Finding Articles at the Lloyd Sealy Library


Input: [Link name (provider)] JSTOR Select the Browse option and the list of volumes and issues will appear. Select the Search option and you will have to select the specific journal title. You may need to click on EXPAND JOURNAL LIST, then select the journal, then the volume and issue you need. Select the title of the article. [If screen displays:]

Output: JSTOR home page

Finding Articles at the Lloyd Sealy Library


Input: [Link name (provider)] Kluwer Select the year, volume and issue. Then select the article. [If screen displays:]

Output: List of Volumes

Finding Articles at the Lloyd Sealy Library


Input: [Link name (provider)] Project Muse Look on the left side for list of volume numbers. Select the volume and issue number. Then select the article from the list of titles. Or you may be linked directly to correct volume and issue. [If screen displays:]

Output: Journal Description

Finding Articles at the Lloyd Sealy Library


Input: [Link name (provider)] Sage Sage always first shows the most current issue, so Click on VIEW ALL ISSUES on the right side of screen. Select volume and issue number you need. Then find your article in the list. [If screen displays:]

Output: Wrong Issue

Finding Articles at the Lloyd Sealy Library


Input: [Link name (provider)] Science Direct Select the volume you need, then the issue number, then the article title. Articles are listed in order of starting page numbers.If the issue does not have a green icon, then the full text of the articles will not be available through this link. No articles available in full text before 1997. [If screen displays:]

Output: List of volumes

Finding Articles at the Lloyd Sealy Library


Input: [Dynamic Pseudo Class] :link [Elements Affected] Links only [Description]

Output: Unvisited links


Input: [Dynamic Pseudo Class] :visited [Elements Affected] Links only [Description]

Output: Visited links


Input: [Dynamic Pseudo Class] :hover [Elements Affected] All elements [Description]

Output: Mouse cursor over element


Input: [Dynamic Pseudo Class] :active [Elements Affected] All elements [Description]

Output: Mouse clicks element


Input: [Dynamic Pseudo Class] :focus [Elements Affected] All elements that can be selected [Description]

Output: Element is selected


Input: [Dynamic Pseudo Class] None [Elements Affected] All elements [Description]

Output: Default state of all elements


Input: [Property name] DBMS_NAME [Description] The name of the database server to which you are connected. For DB2 servers this is a combination of DB2 followed by the operating system on which the database server is running. [Return type]

Output: string

db2_server_info : Returns an object with properties that describe the DB2 database server - Funciones de IBM DB2 | PHPManuals.net

Database server properties


Input: [Property name] DBMS_VER [Description] The version of the database server, in the form of a string "MM.mm.uuuu" where MM is the major version, mm is the minor version, and uuuu is the update. For example, "08.02.0001" represents major version 8, minor version 2, update 1. [Return type]

Output: string

db2_server_info : Returns an object with properties that describe the DB2 database server - Funciones de IBM DB2 | PHPManuals.net

Database server properties


Input: [Property name] DB_CODEPAGE [Description] The code page of the database to which you are connected. [Return type]

Output: int

db2_server_info : Returns an object with properties that describe the DB2 database server - Funciones de IBM DB2 | PHPManuals.net

Database server properties


Input: [Property name] DB_NAME [Description] The name of the database to which you are connected. [Return type]

Output: string

db2_server_info : Returns an object with properties that describe the DB2 database server - Funciones de IBM DB2 | PHPManuals.net

Database server properties