diff options
| author | Mattes D <github@xoft.cz> | 2015-08-12 08:25:29 +0200 |
|---|---|---|
| committer | Mattes D <github@xoft.cz> | 2015-08-12 08:25:29 +0200 |
| commit | d118550a5bdf761cc90ff722ff8dd7391df7285f (patch) | |
| tree | 482062f5cdc11520ff0d0496e419524be01f1299 /MCServer/Plugins/APIDump/SettingUpDecoda.html | |
| parent | Merge pull request #2423 from cuberite/JsonCppCheck (diff) | |
| parent | Updated APIDump to follow the namechange (diff) | |
| download | cuberite-d118550a5bdf761cc90ff722ff8dd7391df7285f.tar cuberite-d118550a5bdf761cc90ff722ff8dd7391df7285f.tar.gz cuberite-d118550a5bdf761cc90ff722ff8dd7391df7285f.tar.bz2 cuberite-d118550a5bdf761cc90ff722ff8dd7391df7285f.tar.lz cuberite-d118550a5bdf761cc90ff722ff8dd7391df7285f.tar.xz cuberite-d118550a5bdf761cc90ff722ff8dd7391df7285f.tar.zst cuberite-d118550a5bdf761cc90ff722ff8dd7391df7285f.zip | |
Diffstat (limited to '')
| -rw-r--r-- | MCServer/Plugins/APIDump/SettingUpDecoda.html | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/MCServer/Plugins/APIDump/SettingUpDecoda.html b/MCServer/Plugins/APIDump/SettingUpDecoda.html index 4ad827efe..7f51ad19d 100644 --- a/MCServer/Plugins/APIDump/SettingUpDecoda.html +++ b/MCServer/Plugins/APIDump/SettingUpDecoda.html @@ -2,7 +2,7 @@ <html> <head> - <title>MCServer - Setting up Decoda</title> + <title>Cuberite - Setting up Decoda</title> <link rel="stylesheet" type="text/css" href="main.css" /> <link rel="stylesheet" type="text/css" href="prettify.css" /> <script src="prettify.js"></script> @@ -13,7 +13,7 @@ <div id="content"> <h1>Setting up the Decoda IDE</h1> <p> - This article will explain how to set up Decoda, an IDE for writing Lua code, so that you can develop MCServer plugins with the comfort of an IDE.</p> + This article will explain how to set up Decoda, an IDE for writing Lua code, so that you can develop Cuberite plugins with the comfort of an IDE.</p> <h2><img src="Static/decoda_logo.png" /> About Decoda</h2> @@ -30,9 +30,9 @@ <p>In the debugging section, fill in the full path to MCServer.exe, or click the triple-dot button to browse for the file. Note that the Working directory will be automatically filled in for you with the folder where the executable is (until the last backslash). This is how it's supposed to work, don't change it; if it for some reason doesn't update, copy and paste the folder name from the Command edit box. All done, you can close this dialog now.</p> <h2><img src="Static/decoda_logo.png" /> Debugging</h2> - <p>You are now ready to debug your code. Before doing that, though, don't forget to save your project file. If you haven't done so already, enable your plugin in the settings.ini file. If you want the program to break at a certain line, it is best to set the breakpoint before starting the program. Set the cursor on the line and hit F9 (or use menu Debug -> Toggle Breakpoint) to toggle a breakpoint on that line. Finally, hit F5, or select menu Debug -> Start to launch MCServer under the debugger. The MCServer window comes up and loads your plugin. If Decoda displays the Project Settings dialog instead, you haven't set up the executable to run, see the Project management section for instructions.</p> - <p>At this point you will see that Decoda starts adding new items to your project. All the files for all plugins are added temporarily. Don't worry, they are only temporary, they will be removed again once the debugging session finishes. You can tell the temporary files from the regular files by their icon, it's faded out. Decoda handles all the files that MCServer loads, so you can actually debug any of those faded files, too.</p> - <p>If there's an error in the code, the Decoda window will flash and a dialog box will come up, describing the error and taking you to the line where it occured. Note that the execution is paused in the thread executing the plugin, so until you select Debug -> Continue from the menu (F5), MCServer won't be fully running. You can fix the error and issue a "reload" command in MCServer console to reload the plugin code anew (MCServer doesn't detect changes in plugin code automatically).</p> + <p>You are now ready to debug your code. Before doing that, though, don't forget to save your project file. If you haven't done so already, enable your plugin in the settings.ini file. If you want the program to break at a certain line, it is best to set the breakpoint before starting the program. Set the cursor on the line and hit F9 (or use menu Debug -> Toggle Breakpoint) to toggle a breakpoint on that line. Finally, hit F5, or select menu Debug -> Start to launch Cuberite under the debugger. The Cuberite window comes up and loads your plugin. If Decoda displays the Project Settings dialog instead, you haven't set up the executable to run, see the Project management section for instructions.</p> + <p>At this point you will see that Decoda starts adding new items to your project. All the files for all plugins are added temporarily. Don't worry, they are only temporary, they will be removed again once the debugging session finishes. You can tell the temporary files from the regular files by their icon, it's faded out. Decoda handles all the files that Cuberite loads, so you can actually debug any of those faded files, too.</p> + <p>If there's an error in the code, the Decoda window will flash and a dialog box will come up, describing the error and taking you to the line where it occured. Note that the execution is paused in the thread executing the plugin, so until you select Debug -> Continue from the menu (F5), Cuberite won't be fully running. You can fix the error and issue a "reload" command in Cuberite console to reload the plugin code anew (Cuberite doesn't detect changes in plugin code automatically).</p> <p>If the execution hits a breakpoint, the Decoda window will flash and a yellow arrow is displayed next to the line. You can step through the code using F10 and F11, just like in MSVS. You can also use the Watch window to inspect variable values, or simply hover your mouse over a variable to display its value in the tooltip.</p> <h2><img src="Static/decoda_logo.png" /> Limitations</h2> |