so good
i like it [import]uid: 134538 topic_id: 23072 reply_id: 101741[/import]
@All,
Please note the new update is primarily bug fixes:
v1.5.1 (these will also show up in the update screen)
-Fixed Navigator not displaying bug
-Fixed performance bugs
-Fixed callstack bug
-Fixed read only table bug
Hopefully we will be getting our own third party forum soon! Please bear with us for a few more days.
@gtellgtell,
Thanks for your interest! we hope you like it.
@srdjan.markovic,
Maybe it’s not bad idea to have list of Cider safe Netbeans plugins under “available plugins” tab
pretty much any plugin from netbeans should work with Cider, provided it isnt java specific. This includes the awesome substance look and feel library: Just go to plugins->settings->add
http://kenai.com/projects/nbsubstance/downloads/download/updates/updates.xml
Is the Macro feature turned off?
No it is not disabled. Does nothing show up when you click stop macro?
@liuhm,
Glad you like it!
@schizoid2k,
Variables tab should be fixed in this update. Please check.
@aisaksen,
Call stack should stop graying out. Also, the location (file and line) is displayed in its own column. You may have to right click and enable the column to view it.
@doubleslashdesign,
Read only issue and variables tab should be fixed.
@corona706,
Please try again with Lime. The issue may be resolved.
Regards,
M.Y. Developers [import]uid: 55057 topic_id: 23072 reply_id: 101789[/import]
How do I upgrade to 1.5.1? I’m still running 1.0. The “Check for Updates” menu appears to only be for plug-ins. All I can find on your website are the links for the trial versions.
Thanks much!
Jim Barber
[import]uid: 5540 topic_id: 23072 reply_id: 101796[/import]
Thanks for great update M.Y.! Works great.
I wanted to add mentioned nsubstance and then I noticed you added new plugin: memory timeline. Is this first step to integrating with the profiler?
I also did notice two more things:
-
accelerometer controls work only if there’s “enterFrame” listener registered (even empty) - I didn’t investigate, it might be Corona’s emulator quirk
-
if you register for accelerometer events - you can’t debug handler function… Is that intended?
Regards,
Krystian
[import]uid: 42082 topic_id: 23072 reply_id: 101800[/import]
Single step problem with print
Hi M.Y.,
Enjoying Cider but I think have discovered a bug.
I’ve created a simple main.lua which demonstrates it:
CiderRunMode = {};CiderRunMode.assertImage = true;require “CiderDebugger”;
a = 1 --Line 2
a=a+1 --Line 3
a=a+1 --Line 4
print( “Test A” ) --Line 5
a=a+1 --Line 6
a=a+1 --Line 7
a=a+1 --Line 8
print( “Test B” ) --Line 9
a=a+1 --Line 10
a=a+1 --Line 11
Set breakpoints at lines 3, 7, 11
Click Debug Main Project: Stops at line 3 as expected
Click Stepover: Stops at line 4 as expected
Click Stepover: Stops at line 5 as expected
Click Stepover: Stops at line 7 but I would expect it to stop at line 6
Click Stepover: Stops at line 8 as expected
Click Stepover: Stops at line 9 as expected
Click Stepover: Stops at line 11 but I would expect it to stop at line 10
My impression is that somehow “print” is turning off single step and it then needs another breakpoint to force another break.
I’m using Version 1.5.1
[import]uid: 67842 topic_id: 23072 reply_id: 101835[/import]
@M.Y…
Yes, the varible tab is now fixed.
Thanks for the quick fix! [import]uid: 114363 topic_id: 23072 reply_id: 101839[/import]
While I have not installed 1.5.1 yet, I have been having considerable performance problems with 1.5.0 and 1.4.9 (and possibly earlier).
It will stop responding to keystrokes. I’ll have to press a key several times which is really annoying. The auto-fill box is really sluggish and it gets to a point where it becomes unusable. Usually a quit and restart helps things.
There seems to be some tie-in with me photoshopping large images, so perhaps there is a big memory leak. [import]uid: 19626 topic_id: 23072 reply_id: 101850[/import]
No still happens when I start debug:
…mples/ParallaxAndPlayer/lime-external-deflatelua.lua:108: attempt to perform arithmetic on local ‘n’ (a string value) [import]uid: 111413 topic_id: 23072 reply_id: 101868[/import]
The plugins are the core components of Cider. Please update those and the version number change will be reflected. It should say 1.5.1 in the title bar (the about page will still say v1.0 however)
@krystian9,
I noticed you added new plugin: memory timeline
Yes. a memory and cpu timeline is soon to come.
1. accelerometer controls work only if there’s “enterFrame” listener registered (even empty) - I didn’t investigate, it might be Corona’s emulator quirk
Strange, should not be related, we will investigate.
2. if you register for accelerometer events - you can’t debug handler function… Is that intended?
No this is not intended. You should be able to place a breakpoint in there and it will stop.
@SUHADA,
Thanks for the test case! Makes our life much easier. Unfortunately we were not able to replicate the problem. Are you running the most up to date version?
@schizoid2k,
Sounds great! Let us know if you find anything else.
@robmiracle,
Please get the update. We addressed performance issues related to the responsiveness of the IDE. Also, when was the last time you reinstalled Cider. We added some JVM switches that will increase the amount of memory to prevent swapping and GC thrashing.
@corona706,
Lets try this: please go to options(or prefs)->Corona options->debugger-> Under startup options change to “Do not debug main chunk”
This will bypass the loading code which you are probably not debugging anyway. Hopefully this will fix the problem until we can find a better solution.
Regards,
M.Y. Developers
[import]uid: 55057 topic_id: 23072 reply_id: 101872[/import]
I set to debug main with delay and that worked too. Thank you! [import]uid: 111413 topic_id: 23072 reply_id: 101877[/import]
It looks like I last downloaded 1.4.7 back around 3/29. I’ve redownloaded and applied the latest updates. I’ll report back when I know more. [import]uid: 19626 topic_id: 23072 reply_id: 101897[/import]
Right you are! Top left corner says 1.5.1… I was going by the About box! Sorry about that! [import]uid: 5540 topic_id: 23072 reply_id: 101908[/import]
I thought I had the most up to date version because in the title bar it says Cider v1.5.1
But I did Help->About and I get: Product Version: Cider 1.3
Is that correct?
If not how do I get the later base version?
[import]uid: 67842 topic_id: 23072 reply_id: 101921[/import]
And I’m using Corona Version 2.0.0 Build 2011.704
Maybe that would have an effect?
[import]uid: 67842 topic_id: 23072 reply_id: 101929[/import]
@M.Y. call stack doesn’t display the line that you are working on, just the line number for the start of the function. I need to know where in the calling function we are calling from. this is how call stacks always work for IDEs.
Thanks! Super useful product (and just bought the profiler today) [import]uid: 122310 topic_id: 23072 reply_id: 101951[/import]
@M.Y. Any chance we could hover our mouse cursor over a variable during debug to see its value? Thats always a very easy way to check the values of things on the current line. [import]uid: 122310 topic_id: 23072 reply_id: 101952[/import]
call stack doesn’t display the line that you are working on
The call stack is in reference to the current program counter (the green arrow/line) The call stack only gets updated when you pause or hit a breakpoint.
Any chance we could hover our mouse cursor over a variable during debug to see its value
Yes this is planned. Thanks for the tip.
@SUHADA,
Yes that should be the most up to date version. Is this on mac or pc?
Regards,
M.Y. Developers [import]uid: 55057 topic_id: 23072 reply_id: 101972[/import]
@MY
On a PC.
[import]uid: 67842 topic_id: 23072 reply_id: 101985[/import]
– [import]uid: 55057 topic_id: 23072 reply_id: 101971[/import]
@MY Thanks again for all the hard work!
Some thoughts:
-
I understand how the call stack works now, but is there any chance it could (optionally?) work like other typical debuggers where you can see variables and locations at any place in the stack? This lets you move up the stack and look at variables in other scopes. Its very useful for tricky bugs! Maybe this would slow things down so should only be an option?
-
the debugger doesn’t work in coroutines. If you put a breakpoint in a co-routine it won’t stop, so i’m forced to use print debugging for coroutines. Any chance that could work in the future?
-
Sometimes I get warnings from Corona that i’m using the api wrong, or setting a variable as nil incorrectly, but i can’t find where that is. Any possibility there could be an option that cider would break at warnings just like it does for errors when debugging?
Thanks again! [import]uid: 122310 topic_id: 23072 reply_id: 102098[/import]