We’re preparing to release version 1.5 of Corona Editor that fixes quite a few issues. You can find the README here and below is a summary of the changes. Many of these changes have been available in the “Daily Build” of Corona Editor that is available on Github.
If you want to help test this version of Corona Editor you can configure Package Control to grab it instead of the official release version by following the instructions in the README. Please let us know of any problems here or on Github.
Changes for Corona Editor 1.5.0:
- Various debugger improvements including:
- syntax coloring of debugger panes
- avoiding problematic debugger commands in certain versions of Corona Simulator
- better display of file paths
- table variable contents are shown correctly
- formatting of variable contents when inspecting
- Corona Editor is now less sensitive about the name it’s installed under
- Fix error in “class” snippet (fixes issue #17)
- Update snippets
- Add support for Simulator version detection
- Improved completion generation and latest completions (for build 2014.2511)
- Also look for settings in the main Sublime Text prefs. This means Corona Editor settings can be set in either the Corona Editor settings file ("~/Library/Application Support/Sublime Text 3/Packages/User/Corona Editor.sublime-settings") or the main Sublime Text settings file ("~/Library/Application Support/Sublime Text 3/Packages/User/Preferences.sublime-settings")
- Add “-no-console” option to Mac Simulator invocation
- Warn if completion inactive. A message is shown (briefly) on the status line if Corona SDK completion is not being done because a .lua file does not have “Corona SDK Lua” syntax set
- Fixed various Windows issues
- About box misbehavior
- Correct regex for finding errors
- Add regex for Windows
- Fix snippets path
- Fixes for Sublime Text 2 compatibility
- Tweaks to build subsystem
- Allow errors to be double-clicked in build panel when Run Project is used. Also, save all modified files before running project (but only if modified). Improved reliability of Run Project
- Improve Debugger behavior. You can now use “Debugger > Stop” to close the additional panes even if
- the editor doesn’t think the debugger is running
- Completion improvements
- Added capability to strip whitespace from completions (thx personalnadir); set “corona_sdk_completions_strip_white_space” to activate
- Fixed various issues with completion and periods
- Fix doubling of prefixes when doing completion under certain circumstances
- Files with “Corona SDK Lua” syntax type set are candidates for Corona Editor completion. New, unsaved files are assumed to be Corona Lua files unless “corona_sdk_default_new_file_to_corona_lua” is set to false
- Handle errors in completion data files more gracefully
- Changed the way periods are handled so that the Sublime Text “word_separators” preference is not changed (logic is now based on the more appropriate “auto_complete_triggers” preference). Changes are reverted when the buffer is closed
- Add appropriate symbols to the word terminators list
- Give Corona Lua its own scopeName so we can distinguish it from regular Lua when doing syntax based things
- Fix toggling of build pane. Toggling the build pane would clear its contents due to a Sublime Text weirdness which is now worked around. Fixes issue #10
- Fix autocomplete ignores text before period (fixes issue #6)
- Syntax highlighting fixes
- Show function arguments as regular variables as the code reads better
- Refactor Corona API keywords regex
- Add “composer” Corona API keyword
- Fix highlighting of function definitions (fixes issue #5)
- Escape pattern before compiling REGEX (fixes strange error messages in Sublime Text console)