Skip to content

Commit 5c2fee8

Browse files
committed
Fix unencapsulated true/false
1 parent 1b3e013 commit 5c2fee8

9 files changed

Lines changed: 17 additions & 17 deletions

File tree

‎docs/extendscript-toolkit/debugging-in-the-toolkit.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ When debugging a script, it is often helpful to make it stop at certain lines so
112112

113113
Some breakpoints need to be conditional. For example, if you set a breakpoint in a loop that is executed several thousand times, you would not want to have the program stop each time through the loop, but only on each 1000th iteration.
114114

115-
You can attach a condition to a breakpoint, in the form of a JavaScript expression. Every time execution reaches the breakpoint, it runs the JavaScript expression. If the expression evaluates to a nonzero number or true, execution stops.
115+
You can attach a condition to a breakpoint, in the form of a JavaScript expression. Every time execution reaches the breakpoint, it runs the JavaScript expression. If the expression evaluates to a nonzero number or `true`, execution stops.
116116

117117
To set a conditional breakpoint in a loop, for example, the conditional expression could be `"i >= 1000"`, which means that the program execution halts if the value of the iteration variable i is equal to or greater than 1000.
118118

@@ -126,18 +126,18 @@ You can edit a breakpoint by double-clicking it, or by selecting it and choosing
126126

127127
![Modify Breakpoints](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_modify-breakpoints.png)
128128

129-
When execution reaches this breakpoint after the specified number of hits, the debugger evaluates this condition. If it does not evaluate to true, the breakpoint is ignored and execution continues. This allows you to break only when certain conditions are met, such as a variable having a particular value.
129+
When execution reaches this breakpoint after the specified number of hits, the debugger evaluates this condition. If it does not evaluate to `true`, the breakpoint is ignored and execution continues. This allows you to break only when certain conditions are met, such as a variable having a particular value.
130130

131131
### Breakpoint icons
132132

133133
Each breakpoint is indicated by an icon to the left of the line number in the document window, and an icon and line number in the Breakpoints panel. Different icons are used in the document window and in the Breakpoints panel.
134134

135-
| Document window | Breakpoints panel | Description |
136-
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
137-
| ![unconditional-document](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_unconditional-document.jpg) | ![unconditional-bppanel](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_unconditional-bppanel.jpg) | Unconditional breakpoint. Execution stops here. |
138-
| ![unconditional-disabled-document](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_unconditional-disabled-document.jpg) | ![unconditional-disabled-bppanel](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_unconditional-disabled-bppanel.jpg) | Unconditional breakpoint, disabled. Execution does not stop. |
139-
| ![conditional-document](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_conditional-document.jpg) | ![conditional-bppanel](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_conditional-bppanel.jpg) | Conditional breakpoint. Execution stops if the attached JavaScript<br/>expression evaluates to true. |
140-
| ![conditional-disabled-document](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_conditional-disabled-document.jpg) | ![conditional-disabled-bppanel](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_conditional-disabled-bppanel.jpg) | Conditional breakpoint, disabled. Execution does not stop. |
135+
| Document window | Breakpoints panel | Description |
136+
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
137+
| ![unconditional-document](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_unconditional-document.jpg) | ![unconditional-bppanel](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_unconditional-bppanel.jpg) | Unconditional breakpoint. Execution stops here. |
138+
| ![unconditional-disabled-document](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_unconditional-disabled-document.jpg) | ![unconditional-disabled-bppanel](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_unconditional-disabled-bppanel.jpg) | Unconditional breakpoint, disabled. Execution does not stop. |
139+
| ![conditional-document](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_conditional-document.jpg) | ![conditional-bppanel](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_conditional-bppanel.jpg) | Conditional breakpoint. Execution stops if the attached JavaScript<br/>expression evaluates to `true`. |
140+
| ![conditional-disabled-document](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_conditional-disabled-document.jpg) | ![conditional-disabled-bppanel](./_static/02_the-extendscript-toolkit_debugging-in-the-toolkit_setting-breakpoints_breakpoint-icons_conditional-disabled-bppanel.jpg) | Conditional breakpoint, disabled. Execution does not stop. |
141141

142142
---
143143

‎docs/extendscript-tools-features/dollar-object.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -325,7 +325,7 @@ String
325325

326326
When `true`, any attempt to write to a read-only property causes a runtime error.
327327

328-
Some objects do not permit the creation of new properties when true.
328+
Some objects do not permit the creation of new properties when `true`.
329329

330330
#### Type
331331

‎docs/extendscript-tools-features/localizing-extendscript-strings.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ All these identifiers are case sensitive; for example, `EN_US` is not valid.
109109

110110
ExtendScript stores the current locale in the variable `$.locale`. This variable is updated whenever the locale of the hosting application changes.
111111

112-
To test your localized strings, you can temporarily reset the locale. To restore the original behavior, set the variable to `null`, false, 0, or the empty string. An example:
112+
To test your localized strings, you can temporarily reset the locale. To restore the original behavior, set the variable to `null`, `false`, `0`, or the empty string. An example:
113113

114114
```javascript
115115
$.locale = "ru"; // try your Russian messages

‎docs/external-communication/socket-object.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ if (conn.listen (80)) {
6161
}
6262
```
6363

64-
Often, the remote endpoint terminates the connection after transmitting data. Therefore, there is a connected property that contains true as long as the connection still exists. If the connected property returns false, the connection is closed automatically.
64+
Often, the remote endpoint terminates the connection after transmitting data. Therefore, there is a connected property that contains `true` as long as the connection still exists. If the connected property returns `false`, the connection is closed automatically.
6565

6666
On errors, the [`error`](./socket-object-reference.md#socketerror) property of the Socket object contains a short message describing the type of the error.
6767

‎docs/file-system-access/using-file-and-folder-objects.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,7 @@ To access a remote volume, use a uniform naming convention (UNC) path name of th
123123

124124
### Aliases
125125

126-
When you access an alias, the operation is transparently forwarded to the real file. The only operations that affect the alias are calls to `rename` and `remove`, and setting properties `readonly` and `hidden`. When a File object represents an alias, the `alias` property of the object returns true, and the `resolve` method returns the File or Folder object for the target of the alias.
126+
When you access an alias, the operation is transparently forwarded to the real file. The only operations that affect the alias are calls to `rename` and `remove`, and setting properties `readonly` and `hidden`. When a File object represents an alias, the `alias` property of the object returns `true`, and the `resolve` method returns the File or Folder object for the target of the alias.
127127

128128
On Windows, all file system aliases (called shortcuts) are actual files whose names end with the extension `.lnk`. Never use this extension directly; the File and Folder objects work without it.
129129

‎docs/integrating-external-libraries/defining-entry-points-for-indirect-access.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -692,7 +692,7 @@ typedef struct {
692692
| `type` | The data type tag. One of: |
693693
| | |
694694
| | - `kTypeUndefined`: a null value, equivalent of JavaScript `undefined`. The return value for a function is always set to this by default. |
695-
| | - `kTypeBool`: a boolean value, 0 for false, 1 for true. |
695+
| | - `kTypeBool`: a boolean value, 0 for `false`, 1 for `true`. |
696696
| | - `kTypeDouble`: a 64-bit floating-point number. |
697697
| | - `kTypeString`: a character string. |
698698
| | - `kTypeLiveObject`: a pointer to an internal representation of an object (SoHObject). |

‎docs/integrating-external-libraries/externalobject-object.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ The ExternalObject class provides these static properties:
4949

5050
#### Description
5151

52-
Set to true to write status information to standard output (the JavaScript Console in the ExtendScript Toolkit).
52+
Set to `true` to write status information to standard output (the JavaScript Console in the ExtendScript Toolkit).
5353

5454
Set to `false` to turn logging off. Default is `false`.
5555

‎docs/interapplication-communication/communicating-through-messages.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -197,7 +197,7 @@ A response message can be:
197197
- The result of an error in processing the message. This is handled by the [onError()](bridgetalk-message-object.md#bridgetalk-message-object-onerror) callback.
198198
- If an error occurs in processing the message body (as the result of a JavaScript syntax error, for instance), the target application invokes the [onError()](bridgetalk-message-object.md#bridgetalk-message-object-onerror) callback, passing a response message that contains the error code and error message. If you do not have an [onError()](bridgetalk-message-object.md#bridgetalk-message-object-onerror) callback defined, the error is completely transparent. It can appear that the message has not been processed, since no result is ever returned to the [onResult()](bridgetalk-message-object.md#bridgetalk-message-object-onresult) callback.
199199
- A notification of receipt of the message. This is handled by the [onReceived()](bridgetalk-message-object.md#bridgetalk-message-object-onreceived) callback.
200-
- Message sending is asynchronous. Getting a true result from the send method does not guarantee that your message was actually received by the target application. If you want to be notified of the receipt of your message, define the [onReceived()](bridgetalk-message-object.md#bridgetalk-message-object-onreceived) callback in the message object. The target sends back the original message object to this callback, first replacing the body value with an empty string.
200+
- Message sending is asynchronous. Getting a `true` result from the send method does not guarantee that your message was actually received by the target application. If you want to be notified of the receipt of your message, define the [onReceived()](bridgetalk-message-object.md#bridgetalk-message-object-onreceived) callback in the message object. The target sends back the original message object to this callback, first replacing the body value with an empty string.
201201
- The result of a time-out. This is handled by the [onTimeout()](bridgetalk-message-object.md#bridgetalk-message-object-ontimeout) callback.
202202
- You can specify a number of seconds in a message object's [timeout](bridgetalk-message-object.md#bridgetalk-message-object-timeout) property. If the message is not removed from the input queue for processing before the time elapses, it is discarded. If the sender has defined an [onTimeout()](bridgetalk-message-object.md#bridgetalk-message-object-ontimeout) callback for the message, the target application sends a time-out message back to the sender.
203203
- Intermediate responses. These are handled by the [onResult()](bridgetalk-message-object.md#bridgetalk-message-object-onresult) callback.
@@ -275,7 +275,7 @@ BridgeTalk.onReceive = function (message){
275275
while (!done) {
276276
// the message.body uses "i" to produce different results
277277
// for each execution of the message.
278-
// when done, the message.body sets "done" to true
278+
// when done, the message.body sets "done" to `true`
279279
// so this onReceive method breaks out of the loop.
280280
message.sendResult(eval(message.body));
281281
i++;

‎docs/scripting-xmp/xmpscript-object-reference.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1586,7 +1586,7 @@ This object is returned by [XMPFile.getPacketInfo()](#getpacketinfo). The read-o
15861586
+-------------+---------+---------------------------------------------------------------------+
15871587
| `padSize` | Number | The packet's padding size in bytes, 0 if unknown. |
15881588
+-------------+---------+---------------------------------------------------------------------+
1589-
| `writeable` | Boolean | If true, the packet is writeable. |
1589+
| `writeable` | Boolean | If `true`, the packet is writeable. |
15901590
+-------------+---------+---------------------------------------------------------------------+
15911591

15921592
---

0 commit comments

Comments
 (0)