Adobe 27510753 Scripting Guide - Page 53

Selecting a debugging target, that is not running, the Toolkit prompts for permission to run it.

Get Adobe 27510753 - InDesign CS2 - PC PDF manuals and user guides
UPC - 718659445294
View all Adobe 27510753 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 53 highlights

Adobe InDesign CS2 Scripting Guide Select target application Using ExtendScript Tools and Features 45 Invoke tab context menus Split pane shows Browser and Editor tabs Each tab has a flyout menu, accessed through the arrow icon in the upper right corner. The same menu is available as a context menu, which you invoke with a right click in the tab. This menu always includes a Hide Pane command to hide that pane. Use the Window menu to show a hidden pane, or to bring it to the front. The Editor, which has a tab for each script, has an additional context menu for debugging, which appears when you right-click in the line numbers area. The Toolkit saves the current layout when you exit, and restores it at the next startup. It also saves and restores the open documents , the current positions within the documents, and any breakpoints that have been set. l If you do not want to restore all settings on startup, hold shift while the Toolkit loads to restore default set- tings. This reconnects to the last application and engine that was selected. l If you want to restore the layout settings on startup, but not load the previously open documents, choose Start with a clean workspace in the Preferences dialog. Selecting a debugging target The Toolkit can debug multiple applications at one time. If you have more than one Adobe Creative Suite 2 application installed, use the drop-down list at the upper left under the menu bar to select the target application. All installed applications that use ExtendScript are shown in this list. If you select an application that is not running, the Toolkit prompts for permission to run it. All available engines in the selected target application are shown in a drop-down list to the right of the application list, with an icon that shows the current debugging status of that engine. A target application can have more than one ExtendScript engine, and more than one engine can be active, although only one is current. An active engine is one that is currently executing code, is halted at a breakpoint, or, having executed all scripts, is waiting to receive events. An icon by each engine name indicates whether it is running, halted, or waiting for input

  • 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
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
Adobe InDesign CS2 Scripting Guide
Using ExtendScript Tools and Features
45
Select target application
Invoke tab context menus
Split pane shows Browser and Editor tabs
Each tab has a flyout menu, accessed through the arrow icon in the upper right corner. The same menu is
available as a context menu, which you invoke with a right click in the tab. This menu always includes a Hide
Pane
command to hide that pane. Use the Window menu to show a hidden pane, or to bring it to the front.
The Editor, which has a tab for each script, has an additional context menu for debugging, which appears
when you right-click in the line numbers area.
The Toolkit saves the current layout when you exit, and restores it at the next startup. It also saves and restores
the open documents , the current positions within the documents, and any breakpoints that have been set.
If you do not want to restore all settings on startup, hold shift while the Toolkit loads to restore default set-
tings. This reconnects to the last application and engine that was selected.
If you want to restore the layout settings on startup, but not load the previously open documents, choose
Start with a clean workspace in the Preferences dialog.
Selecting a debugging target
The Toolkit can debug multiple applications at one time. If you have more than one Adobe Creative Suite 2
application installed, use the drop-down list at the upper left under the menu bar to select the target
application. All installed applications that use ExtendScript are shown in this list. If you select an application
that is not running, the Toolkit prompts for permission to run it.
All available engines in the selected target application are shown in a drop-down list to the right of the
application list, with an icon that shows the current debugging status of that engine. A target application
can have more than one ExtendScript engine, and more than one engine can be
active
, although only one is
current
. An active engine is one that is currently executing code, is halted at a breakpoint, or, having executed
all scripts, is waiting to receive events. An icon by each engine name indicates whether it is
running
,
halted
, or
waiting
for input
l
l