forked from livecode/livecode
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathdriverNames.xml
More file actions
41 lines (41 loc) · 2.61 KB
/
Copy pathdriverNames.xml
File metadata and controls
41 lines (41 loc) · 2.61 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
<doc>
<legacy_id>1229</legacy_id>
<name>driverNames</name>
<type>function</type>
<syntax>
<example>the driverNames</example>
<example>driverNames()</example>
</syntax>
<library></library>
<objects>
</objects>
<synonyms>
</synonyms>
<classification>
<category>Networks & Communication</category>
</classification>
<references>
<command tag="write to driver">write to driver Command</command>
</references>
<history>
<introduced version="2.0">Added.</introduced>
</history>
<platforms>
<mac/>
</platforms>
<classes>
<desktop/>
<server/>
<web/>
</classes>
<security>
<disk access="???"/>
</security>
<summary><glossary tag="return">Returns</glossary> a list of available serial <glossary tag="device driver">drivers</glossary>.</summary>
<examples>
<example>put firstItems(the driverNames) into menu "Choose a driver:"</example>
</examples>
<description>
<p>Use the <b>driverNames</b> <control_st tag="function">function</control_st> to find out which serial <glossary tag="device driver">drivers</glossary> can be used with the <command tag="open driver">open driver</command>, <command tag="read from driver">read from driver</command>, <command tag="write to driver">write to driver</command>, and <command tag="close driver">close driver</command> <glossary tag="command">commands</glossary>.</p><p/><p><b>Value:</b></p><p>The <b>driverNames</b> <control_st tag="function">function</control_st> <glossary tag="return">returns</glossary> a list of <glossary tag="device driver">drivers</glossary>, one per <keyword tag="line">line</keyword>. Each <keyword tag="line">line</keyword> consists of three <keyword tag="items">items</keyword>, separated by commas:</p><p/><p>1. The name of the driver.</p><p>2. The name and location of the TTY device file for the driver.</p><p>3. The name and location of the callout device (CU) file for the driver.</p><p/><p><b>Comments:</b></p><p>Usually, you use the callout file name--the third item in the line for the driver you want--with the <b>open driver</b>, <command tag="read from driver">read from driver</command>, <command tag="write to driver">write to driver</command>, and <command tag="close driver">close driver</command> <glossary tag="command">commands</glossary>.</p><p/><p>If the <b>driverNames</b> <control_st tag="function">function</control_st> is called on a <glossary tag="Mac OS">Mac OS</glossary>, <glossary tag="Unix">Unix</glossary>, or <glossary tag="Windows">Windows system</glossary>, it returns empty and the <function tag="result">result</function> returns "not supported".</p>
</description>
</doc>