Good! Thanks for the tip…
In ZeroBrane IDE is possible to show syntax errors directly on the corresponding line of source code?
Thanks in advance.
-j
> In ZeroBrane IDE is possible to show syntax errors directly on the corresponding line of source code?
@jospic, there is a plugin that shows syntax errors (in the status line) as you type (after Enter) and marks those lines that have errors: https://github.com/pkulchenko/ZeroBraneStudio/issues/215#issuecomment-26230496. You’ll need to get the latest code from github as it depends on some features that have been added after v0.39 (and will be included in 0.40).
Well, thank you! When will it be released next version 0.40?
Regards.
-j
> Well, thank you! When will it be released next version 0.40?
@jospic, it’s likely that 0.40 will be released before the end of this month, but I won’t make any promises.
After upgrade to Mavericks 10.9.2 (yesterday) when I launch my app from ZeroBrane I’ve received this issue in console view:
dyld: Symbol not found: \_gliCreateContextWithShared Referenced from: /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine Expected in: flat namespace
If I launch app directly from Corona there is not problem…
Any suggestions?
@jospic, thank you for the report. Unfortunately Apple has changed something in their handling of flat namespaces, which led to this issue with ZBS. It has already been fixed, but you need to use the current version from github (unzip the archive to any folder and launch ./zbstudio.sh) or wait for v0.41, which should be released in a week or so. My apologies for the inconvenience.
After upgrade to Mavericks 10.9.2 (yesterday) when I launch my app from ZeroBrane I’ve received this issue in console view:
dyld: Symbol not found: \_gliCreateContextWithShared Referenced from: /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine Expected in: flat namespace
If I launch app directly from Corona there is not problem…
Any suggestions?
@jospic, thank you for the report. Unfortunately Apple has changed something in their handling of flat namespaces, which led to this issue with ZBS. It has already been fixed, but you need to use the current version from github (unzip the archive to any folder and launch ./zbstudio.sh) or wait for v0.41, which should be released in a week or so. My apologies for the inconvenience.
Corona SDK 2014.2189 crash in ZeroBrane (debug enabled)
Corona under ZeroBrane with debug feature enabled (require(“mobdebug”).start()), go to crash if encounters a coding error (syntax, etc.).
Maybe you need to update your including file “mobdebug.lua” with this Corona version?
Thanks in advance.
-jospic
@jospic, what operating system? I just downloaded Corona SDK 2013.2189 for Windows and it displays the same popup message for run-time errors as the previous (2013.2100) version I had. Also, what version of ZBS are you running?
The debugger is copied to the Corona installation from ZBS folders, so it should always match the debugger that ZBS ships with and there is no need to update it manually (you only need to do this if you do on-device debugging).
Can you try running the same command that crashes outside of ZBS? You should see “Program starting as ‘…’.” message in the Output window of ZBS; you can take that command as is and run it from the command line.
Paul.
thanks for reply.
Operative system is a Mac OSX Mavericks
ZBS is the latest version 0.50 (10 Mar 2014)
I will do other tests…
Regards
-jospic
Corona SDK 2014.2189 crash in ZeroBrane (debug enabled)
Corona under ZeroBrane with debug feature enabled (require(“mobdebug”).start()), go to crash if encounters a coding error (syntax, etc.).
Maybe you need to update your including file “mobdebug.lua” with this Corona version?
Thanks in advance.
-jospic
@jospic, what operating system? I just downloaded Corona SDK 2013.2189 for Windows and it displays the same popup message for run-time errors as the previous (2013.2100) version I had. Also, what version of ZBS are you running?
The debugger is copied to the Corona installation from ZBS folders, so it should always match the debugger that ZBS ships with and there is no need to update it manually (you only need to do this if you do on-device debugging).
Can you try running the same command that crashes outside of ZBS? You should see “Program starting as ‘…’.” message in the Output window of ZBS; you can take that command as is and run it from the command line.
Paul.
thanks for reply.
Operative system is a Mac OSX Mavericks
ZBS is the latest version 0.50 (10 Mar 2014)
I will do other tests…
Regards
-jospic