Skip to content
This repository was archived by the owner on Aug 31, 2021. It is now read-only.

Commit 6db3e5d

Browse files
livecodesebastienlivecodesebastien
committed
[[ RunRevReferences ]] Properly update '<>' entries with Revolution / Revolution custom library
1 parent 6258710 commit 6db3e5d

File tree

233 files changed

+244
-244
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

233 files changed

+244
-244
lines changed

‎docs/dictionary/command/constant.lcdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ If you place the <constant> <statement> in a <handler>, you can use the <constan
3636

3737
Once you have defined a constant, you cannot redefine it in the same handler; doing so causes an execution error.
3838

39-
You can use the <constant> <command> to redefine <Revolution|LiveCode's> built-in <constant(glossary)|constants> within a <script> or <handler>, but doing so makes your code harder to read and maintain. To find out whether a word is already defined as a built-in <constant(command)>, use the <constantNames> <function>.
39+
You can use the <constant> <command> to redefine <LiveCode|LiveCode's> built-in <constant(glossary)|constants> within a <script> or <handler>, but doing so makes your code harder to read and maintain. To find out whether a word is already defined as a built-in <constant(command)>, use the <constantNames> <function>.
4040

4141
>*Tip:* To see a list of built-in constants, open the Documentation window, click LiveCode Dictionary, and choose "Constants" from the menu at the top of the window.
4242

‎docs/dictionary/command/define.lcdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Type: command
44

55
Syntax: define <property> of <object>
66

7-
Summary: Has no effect and is included in <Revolution|LiveCode> for compatibility with imported <SuperCard> projects.
7+
Summary: Has no effect and is included in <LiveCode|LiveCode> for compatibility with imported <SuperCard> projects.
88

99
Introduced: 1.0
1010

‎docs/dictionary/command/delete-URL.lcdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Normally, FTP servers do not allow anonymous users to delete files, for obvious
4343

4444
>*Note:* When used with an <ftp> or <http> <URL>, the <delete URL> <command> is <blocking> : that is, the <handler> pauses until LiveCode is finished deleting the <URL>. Since deleting a file from a server may take some time due to network lag, the <delete URL> <command> may take long enough to be noticeable to the user.
4545

46-
>*Important:* The <delete URL> <command> is part of the <Internet library>. To ensure that the <command> works in a <standalone application>, you must include this <Revolution custom library|custom library> when you create your <standalone application|standalone>. In the Inclusions section of the <Standalone Application Settings> window, make sure "Internet Library" is selected in the list of script libraries.
46+
>*Important:* The <delete URL> <command> is part of the <Internet library>. To ensure that the <command> works in a <standalone application>, you must include this <LiveCode custom library|custom library> when you create your <standalone application|standalone>. In the Inclusions section of the <Standalone Application Settings> window, make sure "Internet Library" is selected in the list of script libraries.
4747

4848
>*Note:* When included in a <standalone application>, the <Internet library> is implemented as a hidden <group> and made available when the <group> receives its first <openBackground> message. During the first part of the <application|application's> startup process, before this <message> is sent, the <delete URL> <command> is not yet available. This may affect attempts to use this <command> in <startup>, <preOpenStack>, <openStack>, or <preOpenCard> <handler|handlers> in the <main stack>. Once the <application> has finished starting up, the <library> is available and the <delete URL> <command> can be used in any <handler>.
4949

‎docs/dictionary/command/do.lcdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,6 @@ To see how to create a numbered set of variables see the dictionary entry for th
5050
The ability to specify an <alternateLanguageName> on Windows systems was added in LiveCode 2.9.
5151

5252
Changes:
53-
The <alternateLanguageName> option was introduced in version 1.1. In previous versions, it was not possible to include AppleScript or other <Open Scripting Architecture (OSA)|OSA> languages in a <Revolution|LiveCode> <handler>.
53+
The <alternateLanguageName> option was introduced in version 1.1. In previous versions, it was not possible to include AppleScript or other <Open Scripting Architecture (OSA)|OSA> languages in a <LiveCode|LiveCode> <handler>.
5454

5555
References: message box (keyword), as (keyword), debugDo (command), breakpoint (command), local (command), call (command), local command (command), result (function), alternateLanguages (function), system (glossary), Revolution (glossary), handler (glossary), execute (glossary), statement (glossary), Unix (glossary), compile (glossary), command (glossary), Open Scripting Architecture (OSA) (glossary)

‎docs/dictionary/command/doMenu.lcdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ menuName: The name of the menu in which the menuItem appears.
2525
Description:
2626
Use the <doMenu> <command> to choose a <menu item>.
2727

28-
The <doMenu> <command> is not implemented for all <menu item|menu items>. This command is included in <Revolution|LiveCode> for compatibility with imported <HyperCard> stacks.
28+
The <doMenu> <command> is not implemented for all <menu item|menu items>. This command is included in <LiveCode|LiveCode> for compatibility with imported <HyperCard> stacks.
2929

3030
References: copy (command), enable menu (command), paste (command), menuItem (keyword), menu (keyword), Revolution (glossary), command (glossary), menu item (glossary), HyperCard (glossary)
3131

‎docs/dictionary/command/libURLDownloadToFile.lcdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ The <callbackMessage> is sent to the <object> whose <script> contains the <libUR
3636

3737
>*Tip:* On <Mac OS> and <OS X|OS X systems>, the new <file(glossary)|file's> <creator signature> and <type signature|file type> is set to the value specified in the <fileType> <property>.
3838

39-
>*Important:* The <libURLDownloadToFile> <command> is part of the <Internet library>. To ensure that the <command> works in a <standalone application>, you must include this <Revolution custom library|custom library> when you create your <standalone application|standalone>. In the Inclusions section of the <Standalone Application Settings> window, make sure "Internet Library" is selected in the list of script libraries.
39+
>*Important:* The <libURLDownloadToFile> <command> is part of the <Internet library>. To ensure that the <command> works in a <standalone application>, you must include this <LiveCode custom library|custom library> when you create your <standalone application|standalone>. In the Inclusions section of the <Standalone Application Settings> window, make sure "Internet Library" is selected in the list of script libraries.
4040

4141
>*Note:* When included in a <standalone application>, the <Internet library> is implemented as a hidden <group> and made available when the <group> receives its first <openBackground> message. During the first part of the <application|application's> startup process, before this <message> is sent, the <libURLDownloadToFile> <command> is not yet available. This may affect attempts to use this <command> in <startup>, <preOpenStack>, <openStack>, or <preOpenCard> <handler|handlers> in the <main stack>. Once the <application> has finished starting up, the <library> is available and the <libURLDownloadToFile> <command> can be used in any <handler>.
4242

‎docs/dictionary/command/libURLSetCustomHTTPHeaders.lcdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ The <libURLSetCustomHTTPHeaders> setting replaces the <Internet library|Internet
4444

4545
If you specify a set of headers using the <libURLSetCustomHTTPHeaders> <command>, the <Internet library|Internet library's> <default> headers and the setting of the <httpHeaders> property are ignored, and the headers set by <libURLSetCustomHTTPHeaders> are used instead.
4646

47-
>*Important:* The <libURLSetCustomHTTPHeaders> <command> is part of the <Internet library>. To ensure that the <command> works in a <standalone application>, you must include this <Revolution custom library|custom library> when you create your <standalone application|standalone>. In the Inclusions section of the <Standalone Application Settings> window, make sure "Internet Library" is selected in the list of script libraries.
47+
>*Important:* The <libURLSetCustomHTTPHeaders> <command> is part of the <Internet library>. To ensure that the <command> works in a <standalone application>, you must include this <LiveCode custom library|custom library> when you create your <standalone application|standalone>. In the Inclusions section of the <Standalone Application Settings> window, make sure "Internet Library" is selected in the list of script libraries.
4848

4949
>*Note:* When included in a <standalone application>, the <Internet library> is implemented as a hidden <group> and made available when the <group> receives its first <openBackground> message. During the first part of the <application|application's> startup process, before this <message> is sent, the <libURLSetCustomHTTPHeaders> <command> is not yet available. This may affect attempts to use this <command> in <startup>, <preOpenStack>, <openStack>, or <preOpenCard> <handler|handlers> in the <main stack>. Once the <application> has finished starting up, the <library> is available and the <libURLSetCustomHTTPHeaders> <command> can be used in any <handler>.
5050

‎docs/dictionary/command/libURLSetFTPListCommand.lcdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The list command is set to LIST when the application starts up.
3333

3434
>*Important:* <FTP> <server|servers> are not uniform in their response to a request for a directory listing. Some <server|servers> may format directory listings differently from these descriptions. These are the most common formats, but they are not universal.
3535

36-
>*Important:* The <libURLSetFTPListCommand> <command> is part of the <Internet library>. To ensure that the <command> works in a <standalone application>, you must include this <Revolution custom library|custom library> when you create your <standalone application|standalone>. In the Inclusions section of the <Standalone Application Settings> window, make sure "Internet Library" is selected in the list of script libraries.
36+
>*Important:* The <libURLSetFTPListCommand> <command> is part of the <Internet library>. To ensure that the <command> works in a <standalone application>, you must include this <LiveCode custom library|custom library> when you create your <standalone application|standalone>. In the Inclusions section of the <Standalone Application Settings> window, make sure "Internet Library" is selected in the list of script libraries.
3737

3838
>*Note:* When included in a <standalone application>, the <Internet library> is implemented as a hidden <group> and made available when the <group> receives its first <openBackground> message. During the first part of the <application|application's> startup process, before this <message> is sent, the <libURLSetFTPListCommand> <command> is not yet available. This may affect attempts to use this <command> in <startup>, <preOpenStack>, <openStack>, or <preOpenCard> <handler|handlers> in the <main stack>. Once the <application> has finished starting up, the <library> is available and the <libURLSetFTPListCommand> <command> can be used in any <handler>.
3939

‎docs/dictionary/command/libURLSetFTPMode.lcdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The FTP mode is set to passive when the application starts up. To use active mod
2929

3030
libURLSetFTPMode "active"
3131

32-
>*Important:* The <libURLSetFTPMode> <command> is part of the <Internet library>. To ensure that the <command> works in a <standalone application>, you must include this <Revolution custom library|custom library> when you create your <standalone application|standalone>. In the Inclusions section of the <Standalone Application Settings> window, make sure "Internet Library" is selected in the list of script libraries.
32+
>*Important:* The <libURLSetFTPMode> <command> is part of the <Internet library>. To ensure that the <command> works in a <standalone application>, you must include this <LiveCode custom library|custom library> when you create your <standalone application|standalone>. In the Inclusions section of the <Standalone Application Settings> window, make sure "Internet Library" is selected in the list of script libraries.
3333

3434
>*Note:* When included in a <standalone application>, the <Internet library> is implemented as a hidden <group> and made available when the <group> receives its first <openBackground> message. During the first part of the <application|application's> startup process, before this <message> is sent, the <libURLSetFTPMode> <command> is not yet available. This may affect attempts to use this <command> in <startup>, <preOpenStack>, <openStack>, or <preOpenCard> <handler|handlers> in the <main stack>. Once the <application> has finished starting up, the <library> is available and the <libURLSetFTPMode> <command> can be used in any <handler>.
3535

‎docs/dictionary/command/libURLSetFTPStopTime.lcdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ By default, the timeout value is 15 seconds.
3232

3333
>*Note:* If the <server> closes the connection, LiveCode does not attempt to keep it open. The <timeout> set by <libURLSetFTPStopTime> controls when LiveCode closes the connection from its end, but if the <server> closes the connection, a longer <timeout> has no effect.
3434

35-
>*Important:* The <libURLSetFTPStopTime> <command> is part of the <Internet library>. To ensure that the <command> works in a <standalone application>, you must include this <Revolution custom library|custom library> when you create your <standalone application|standalone>. In the Inclusions section of the <Standalone Application Settings> window, make sure "Internet Library" is selected in the list of script libraries.
35+
>*Important:* The <libURLSetFTPStopTime> <command> is part of the <Internet library>. To ensure that the <command> works in a <standalone application>, you must include this <LiveCode custom library|custom library> when you create your <standalone application|standalone>. In the Inclusions section of the <Standalone Application Settings> window, make sure "Internet Library" is selected in the list of script libraries.
3636

3737
>*Note:* When included in a <standalone application>, the <Internet library> is implemented as a hidden <group> and made available when the <group> receives its first <openBackground> message. During the first part of the <application|application's> startup process, before this <message> is sent, the <libURLSetFTPStopTime> <command> is not yet available. This may affect attempts to use this <command> in <startup>, <preOpenStack>, <openStack>, or <preOpenCard> <handler|handlers> in the <main stack>. Once the <application> has finished starting up, the <library> is available and the <libURLSetFTPStopTime> <command> can be used in any <handler>.
3838

0 commit comments

Comments
 (0)