OpenComputers Interface - Revision history

Montoyo at 15:26, 23 July 2019

2019-07-23T15:26:42Z

2019-07-23T15:18:25Z

‎typeAdvanced, WebDisplays 1.1

2019-07-23T15:18:14Z

‎typeAdvanced, WebDisplays 1.1

2019-07-23T14:56:51Z

‎Functions

2019-07-23T14:55:55Z

2019-07-23T14:54:20Z

2019-07-23T14:53:14Z

2018-02-13T21:39:07Z

2018-02-13T00:17:02Z

2018-02-13T00:14:52Z

‎Functions

← Older revision		Revision as of 15:26, 23 July 2019
Line 114:		Line 114:

	===typeAdvanced, WebDisplays 1.0===		===typeAdvanced, WebDisplays 1.0===
−	~~TODO~~	+	With WebDisplays 1.0, key events are stored in a string using the ASCII character 0x01 as separator. Each event must contain at least 2 characters. The first one is the event type ('p' for press, 'r' for release, and 't' for type), and the second is the pressed key character (i.e. for the F key, use the 'f' character). In case of a type event (first character is 't'), you can have several leters.
		+
		+	Note that if you want to write something, "press" and "release" events are not enough. You '''need''' to send the corresponding "type" event. Press & release events are only required for control keys (backspace, return, tab, etc...). If you only want to type something, you should use the "type" function; it's a lot faster and also easier.
		+
		+	Example code:
		+	<syntaxhighlight lang="lua" line='line'>
		+	SEPARATOR = string.char(1)
		+
		+	-- Press h key, release it, and then type "hello"
		+	wdScreen.typeAdvanced("ph" .. SEPARATOR .. "rh" .. SEPARATOR .. "thello")
		+	</syntaxhighlight>

@@ Line 102: / Line 102: @@
 Note that if you want to write something, "press" and "release" events are not enough. You '''need''' to send the corresponding "type" event. Press & release events are only required for control keys (backspace, return, tab, etc...). If you only want to type something, you should use the "type" function; it's a lot faster and also easier.
-For a list of key codes, check out [[Key_codes]].
+For a list of key codes, check out [[Key codes]].
 Example code:

← Older revision		Revision as of 15:18, 23 July 2019
Line 101:		Line 101:

	Note that if you want to write something, "press" and "release" events are not enough. You '''need''' to send the corresponding "type" event. Press & release events are only required for control keys (backspace, return, tab, etc...). If you only want to type something, you should use the "type" function; it's a lot faster and also easier.		Note that if you want to write something, "press" and "release" events are not enough. You '''need''' to send the corresponding "type" event. Press & release events are only required for control keys (backspace, return, tab, etc...). If you only want to type something, you should use the "type" function; it's a lot faster and also easier.
		+
		+	For a list of key codes, check out [[Key_codes]].

	Example code:		Example code:

@@ Line 72: / Line 72: @@
 |type||string||bool||||click
 |-
-|typeAdvanced||string/table||bool||Manually control key up/down events. Arguments depends the on WebDisplays version.||click
+|typeAdvanced||string/table||bool||Manually control key up/down events. Arguments depend the on WebDisplays version.||click
 |-
 |setURL||string||bool||||seturl

@@ Line 100: / Line 100: @@
 |}
-Note that if you want to write something, "press" and "release" events are not enough. You **need** to send the corresponding "type" event. Press & release events are only required for control keys (backspace, return, tab, etc...). If you only want to type something, you should use the "type" function; it's a lot faster and also easier.
+Note that if you want to write something, "press" and "release" events are not enough. You '''need''' to send the corresponding "type" event. Press & release events are only required for control keys (backspace, return, tab, etc...). If you only want to type something, you should use the "type" function; it's a lot faster and also easier.
 Example code:

@@ Line 93: / Line 93: @@
 !Value description
 |-
-|action||string||Can be "press", "release", or "type". This is case insensitive.||
+|action||string||Can be "press", "release", or "type". This is case insensitive.
 |-
-|code||number||The corresponding key code. Useless when action is "type".||
+|code||number||The corresponding key code. Useless when action is "type".
 |-
-|char||string||The character corresponding to that key.||
+|char||string||The character corresponding to that key.
 |}

← Older revision		Revision as of 21:39, 13 February 2018
Line 1:		Line 1:
	The OpenComputers Interface is a [[Screen#Peripheral\|peripheral]] which can be used by OpenComputers computers to interact with screens.		The OpenComputers Interface is a [[Screen#Peripheral\|peripheral]] which can be used by OpenComputers computers to interact with screens.
		+
		+	{{#widget:AdSense}}

	==Recipe==		==Recipe==

@@ Line 3: / Line 3: @@
 ==Recipe==
 [[File:Ocinterface.png]]
 ==How to use==

@@ Line 38: / Line 38: @@
 !Function name
 !Arguments
-!Return value
+!Return values
 !Comment
 !Permission