hasemrep.blogg.se

Sublime text editor step
Sublime text editor step









  1. #SUBLIME TEXT EDITOR STEP INSTALL#
  2. #SUBLIME TEXT EDITOR STEP MANUAL#
  3. #SUBLIME TEXT EDITOR STEP CODE#
  4. #SUBLIME TEXT EDITOR STEP SIMULATOR#

There's an implicit breakpoint set on the first line of a so to hit your own first breakpoint you need to run once to start the debugger and stop on the first line then run again to continue until you hit your own breakpoint.Single stepping through “internal locations” is tedious.

#SUBLIME TEXT EDITOR STEP CODE#

  • If you Run the project and it doesn't hit a breakpoint, you'll have to stop and restart to regain control (in particular, setting a breakpoint on a line of code you know is being executed wont stop the program).
  • #SUBLIME TEXT EDITOR STEP SIMULATOR#

    Set this to true to have the Solar2D Simulator Console be shown when running a project with Super+F10 (or Super+B). The name of the preference is not quoted in Lua).Ĭorona_sdk_simulator_show_console (default: false) Is different to the JSON syntax of the Sublime Text preference files in that Is used for each project (note that the Lua syntax for the ttings file You can also set this in the ttingsįile of individual projects to customize the version of the Solar2D Simulator that In the default location for your operating system (remember to double Set this to the path of your Solar2D Simulator if it's not installed PreferencesĬorona_sdk_simulator_path (default: system dependent)

    #SUBLIME TEXT EDITOR STEP INSTALL#

    On macOS, if you install Solar2D in /Applications without changing the default name, it will use the highest numbered (most recent) build to run the project (to change this behavior, see corona_sdk_simulator_path below). Super+B (usually bound to the Build command) is now bound to the Run Project command for Solar2D Lua files. It is also better at finding your project's a if you aren't using Sublime Text's projects. It doesn't have all the bells and whistles of the build system but it is quick and easy. Run Project in the Debugger or continue project executionĪ simpler alternative to the Build command in Sublime Text is the Run Project command in the Solar2D Editor menu (or Super+F10). The following keys also control the Debugger: Key Select the name of a variable and choose Inspect Variable from the context menu to see its value. Right click on a code line in the editor and choose Toggle Breakpoint to turn a breakpoint on or off. You can run the debugger using the Solar2D Editor menu from any file in the project and it will automatically find a. Debuggerĭebugger allows code to be single stepped, variables to be examined and breakpoints to be set. You can find information on setting User Preferences here. There are several Sublime Text User Preferences that can be set to fine tune the behavior of the plugin. If the syntax option is set correctly you'll see it displayed in the bottom righthand corner of the Sublime Text window. lua files by choosing View > Syntax > Open all with current extension as… > Lua (Solar2D) when you have a. You will probably also want to change Sublime Text's default for. Most of the features of the plugin rely on the current Syntax setting so when editing files you should use View > Syntax > Lua (Solar2D) command to set the correct syntax for the file. If you install the tip from Github please report any issues using the Issues page on Github: Using the PluginĪfter restarting Sublime Text you'll have several new features available in the Solar2D Editor menu and in the context menu when editing Solar2D.

    #SUBLIME TEXT EDITOR STEP MANUAL#

    lua files to see the new featuresĪlternatively, if you are comfortable doing manual installs of Sublime Text plugins and want to run the latest development version, you can download the plugin from Find CoronaSDK-SublimeText (or, on some machines, Corona Editor - Daily Build) by typing in the search field, click on it to install it.Choose: Tools > Command Palette… > Package Control: Install Package.Choose: Tools > Command Palette… > Package Control: Add Repository.In Sublime Text choose: Tools > Command Palette… > Package Control: Remove Package and uninstall any installed version of Corona Editor.If you want to help test the latest development version of Solar2D Editor you can configure Package Control to grab it instead of the official release version by following these steps: Restart Sublime Text to see the new features.Find Corona Editor by typing in the search field, click on it to install it.When that's installed, in Sublime Text choose: Tools > Command Palette… > Package Control: Install Package.Install the Sublime Text Package Control plugin if you don't already have it using Tools > Command Palette… > Install Package Control.Sublime Text 3 is required to use Solar2D Editor. Designed to make building apps even easier by adding functionality to Sublime Text to improve developer productivity. Solar2D Editor (rebranded Corona Editor) is the official Solar2D plugin for Sublime Text.











    Sublime text editor step