From ef95dc14df8046ec31d682034f4d34260e2d46ee Mon Sep 17 00:00:00 2001 From: jfiat Date: Thu, 19 Nov 2009 17:49:07 +0000 Subject: [PATCH] Author:jfiat Date:2009-11-19T17:49:07.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@360 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../eiffelstudio-guided-tour/recompiling-and-editing.wiki | 2 +- .../outputs-tool/external-compilation-pane.wiki | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/recompiling-and-editing.wiki b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/recompiling-and-editing.wiki index c02711f3..1d159146 100644 --- a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/recompiling-and-editing.wiki +++ b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/recompiling-and-editing.wiki @@ -21,7 +21,7 @@ The Editing Tool hosts a text editor which you can use to change the class text. io.new_line -They are very similar to the current first two lines of the routine, so you can just use copy-paste: select the first two lines with the mouse, copy them using CTRL-C (or Copy from the Edit menu), then paste them just after the do using CTRL-V (or Paste from the Edit menu). Add or remove tabs to align with the rest of the routine, and change the string to THIS IS SOME MORE ADDED TEXT so that the result will look like what's shown on the next figure. This is all there is to change; the second line remains untouched. Please check the result and be careful not to introduce any mistakes; in the next section we'll study how EiffelStudio will report syntax and other errors, but right now we want to see what happens when everything is right! +They are very similar to the current first two lines of the routine, so you can just use copy-paste: select the two lines with the mouse, copy them using CTRL-C (or Copy from the Edit menu), then paste them just after the do using CTRL-V (or Paste from the Edit menu). Add or remove tabs to align with the rest of the routine, so that the result will look like what's shown on the next figure. This is all there is to change; the second line remains untouched. Please check the result and be careful not to introduce any mistakes; in the next section we'll study how EiffelStudio will report syntax and other errors, but right now we want to see what happens when everything is right! [[Image:index-67]] diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/external-compilation-pane.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/external-compilation-pane.wiki index 9e4b19b3..5b6a7b95 100644 --- a/documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/external-compilation-pane.wiki +++ b/documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/external-compilation-pane.wiki @@ -35,6 +35,8 @@ You can open a file mentioned in the external compiler output in a specified ext [[Image:External compilation pane file selection|Selecting a file to open]] +If, as is often the case with C compilation errors, a line number is adjacent to the file name, you can select the line number and the file will be opened in the external editor and the cursor positioned at that line number. + ==View external code for a class/feature== You can view the external code for a particular Eiffel class or feature in an external editor. Pick the class or feature whose generated code you want to see, and drop it onto the [[Image:metrics-tool--command-send-to-external-editor-icon|send to external editor]] button. The external code for the class or feature will be shown in an external editor. @@ -43,6 +45,8 @@ The figure below shows an example of picking the feature make and d [[Image:External compilation pane edit feature]] +You can also drop a class or feature pebble on the '''open folder''' or '''terminal''' icon. This will get you to the folder in which the generated code for the class or feature resides. + ===View external code from the finalized folder=== By default the code that you see in an external editor is from the workbench (W_code) folder. You can see the corresponding external code from the finalized (F_code) folder by holding the CTRL key while you drop the class or feature pebble.