You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5c2fee8
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/extendscript-toolkit/debugging-in-the-toolkit.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,7 +112,7 @@ When debugging a script, it is often helpful to make it stop at certain lines so
112
112
113
113
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.
114
114
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.
116
116
117
117
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.
118
118
@@ -126,18 +126,18 @@ You can edit a breakpoint by double-clicking it, or by selecting it and choosing
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.
130
130
131
131
### Breakpoint icons
132
132
133
133
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.
||| Unconditional breakpoint, disabled. Execution does not stop. |
139
-
||| Conditional breakpoint. Execution stops if the attached JavaScript<br/>expression evaluates to true. |
140
-
||| Conditional breakpoint, disabled. Execution does not stop. |
||| Unconditional breakpoint, disabled. Execution does not stop. |
139
+
||| Conditional breakpoint. Execution stops if the attached JavaScript<br/>expression evaluates to `true`. |
140
+
||| Conditional breakpoint, disabled. Execution does not stop. |
Copy file name to clipboardExpand all lines: docs/extendscript-tools-features/localizing-extendscript-strings.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,7 +109,7 @@ All these identifiers are case sensitive; for example, `EN_US` is not valid.
109
109
110
110
ExtendScript stores the current locale in the variable `$.locale`. This variable is updated whenever the locale of the hosting application changes.
111
111
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:
Copy file name to clipboardExpand all lines: docs/external-communication/socket-object.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ if (conn.listen (80)) {
61
61
}
62
62
```
63
63
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.
65
65
66
66
On errors, the [`error`](./socket-object-reference.md#socketerror) property of the Socket object contains a short message describing the type of the error.
Copy file name to clipboardExpand all lines: docs/file-system-access/using-file-and-folder-objects.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,7 +123,7 @@ To access a remote volume, use a uniform naming convention (UNC) path name of th
123
123
124
124
### Aliases
125
125
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.
127
127
128
128
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.
Copy file name to clipboardExpand all lines: docs/interapplication-communication/communicating-through-messages.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -197,7 +197,7 @@ A response message can be:
197
197
- The result of an error in processing the message. This is handled by the [onError()](bridgetalk-message-object.md#bridgetalk-message-object-onerror) callback.
198
198
- 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.
199
199
- 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.
201
201
- The result of a time-out. This is handled by the [onTimeout()](bridgetalk-message-object.md#bridgetalk-message-object-ontimeout) callback.
202
202
- 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.
203
203
- 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){
275
275
while (!done) {
276
276
// the message.body uses "i" to produce different results
277
277
// 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`
279
279
// so this onReceive method breaks out of the loop.
0 commit comments