You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by ge...@apache.org on 2019/05/04 14:11:00 UTC

[netbeans-website] 01/01: Cleaning up 'Using the Visual Debugger in NetBeans IDE'

This is an automated email from the ASF dual-hosted git repository.

geertjan pushed a commit to branch geertjanw-patch-3
in repository https://gitbox.apache.org/repos/asf/netbeans-website.git

commit 33af6817108a17f827d4232b304dfa46ca1c833d
Author: Geertjan Wielenga <ge...@oracle.com>
AuthorDate: Sat May 4 16:10:55 2019 +0200

    Cleaning up 'Using the Visual Debugger in NetBeans IDE'
---
 .../src/content/kb/docs/java/debug-visual.asciidoc         | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/netbeans.apache.org/src/content/kb/docs/java/debug-visual.asciidoc b/netbeans.apache.org/src/content/kb/docs/java/debug-visual.asciidoc
index e7ddae3..46353f1 100644
--- a/netbeans.apache.org/src/content/kb/docs/java/debug-visual.asciidoc
+++ b/netbeans.apache.org/src/content/kb/docs/java/debug-visual.asciidoc
@@ -78,11 +78,11 @@ The commands can also be invoked from the Navigator window by right-clicking the
 
 When you select a component in the snapshot, the IDE displays details about the selected component in the Properties window. If the Properties window is not visible you can choose Window > Properties from the main menu to open the window.
 
-image::images/debug-snapshot.png[title="GUI Snapshot"]
+image::images/debug-snapshot.png[]
 
 The IDE also displays the location of the component in the form hierarchy in the Navigator window.
 
-image::images/debug-navigator.png[title="GUI Snapshot"]
+image::images/debug-navigator.png[]
 [start=2]
 2. Right-click the Guess button in the snapshot and choose Go to Component Declaration from the popup menu.
 
@@ -94,7 +94,7 @@ image::images/debug-gotodeclaration.png[title="Line of code where component is d
 
 When you choose Go to Component Source the IDE opens the source file in the editor and moves the cursor to the line in the source code for the JButton component.
 
-image::images/debug-gotosource.png[title="Line of source code for component"]
+image::images/debug-gotosource.png[]
 
 You can use the Go to Hierarchy Addition command in the GUI snapshot to locate the line in the source code where a component is added to its container. The Go to Hierarchy Addition command is disabled by default. You can enable the command in the Options window.
 
@@ -113,7 +113,7 @@ You can use the Go to Hierarchy Addition command in the GUI snapshot to locate t
 
 The IDE will open the source code in the editor at the line where the component is added.
 
-image::images/debug-hierarchy.png[title="Line of source code where component is added to container"]
+image::images/debug-hierarchy.png[]
 
 === Exploring Component Events
 
@@ -123,7 +123,7 @@ This exercise will demonstrate how you can use the GUI snapshot and the Events w
 
 When you choose Show Listeners, the IDE opens the Events window. You can see that the Custom Listeners node is expanded.
 
-image::images/debug-customlisteners.png[title="Line of source code where component is added to container"]
+image::images/debug-customlisteners.png[]
 [start=2]
 2. Right-click *com.toy.anagrams.ui.Anagrams$3* below the Custom Listeners node and choose Go to Component Source in the popup menu.
 
@@ -140,7 +140,7 @@ When you select the text field, the items in the Events window will change autom
 Alternatively, you can right-click the Event Log node and choose Set Logging Events from the popup menu.
 [start=5]
 5. Select the  ``java.awt.event.KeyListener``  listener from the dialog. Click OK.
-image::images/debug-select-listener.png[title="Line of source code where component is added to container"]
+image::images/debug-select-listener.png[]
 
 This listener is now listening for keyboard events in the text field.
 [start=6]
@@ -148,7 +148,7 @@ This listener is now listening for keyboard events in the text field.
 
 When you type a character in the text field, the event is recorded in the events log. If you expand the Event Log node you can see that each keystroke is now logged. New events appear each time that you type in the Anagram Game application text field. If you expand an individual event, for example  ``keyPressed`` , you can see the properties of that event in the log.
 
-image::images/debug-eventlog.png[title="Line of source code where component is added to container"]
+image::images/debug-eventlog.png[]
 
 If you expand the "Called From..." node for an event you can see the stack trace for the event.
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists