File Open Project never works for me
Very sluggish app on my Mac Air
A lot of CPU overload.
Debug isn’t working well. The back button I see on the Advanced Debug video does not show even though I change the code sampling period to 3 seconds.
Variable watching is very inconsistent.
Perhaps its me but I think I’m just not getting along with this netbeans thingy.
Find in projects / replace in projects is helping me a lot but the rest is not helping my productivity.
Hello Ksan,
Sorry you are experiencing so many issues. Did all these problems happen today?
A lot of CPU overload. Find in projects / replace in projects is helping me a lot but the rest is not helping my productivity.
It seems you are not using the feature that is probably taking up all the CPU usage (auto-completion) so we are making a new option to disable scanning of everything except the Corona stubs. It is a bit extreme but if it is not used then there is no point in scanning anything.
Variable watching is very inconsistent.
In order for this to work properly we need to loadstring function to execute dynamic code. This is not available in the Corona simulator.
Debug isn’t working well. The back button I see on the Advanced Debug video does not show even though I change the code sampling period to 3 seconds.
Do at least breakpoints work?
Regards,
M.Y. Developers
Thanks for your prompt response. Being able to disable all scanning sounds like a good idea. These issues did not all surface today. I have been putting up with it so long for the advantages but today I just can’t do it anymore. Will be back once it gets better.
I don’t understand your comment about variable watching not available in simulator. So how can I watch the variables?
Yes the breakpoints work. I wish the back button worked as demonstrated on the video tutorial but debugging without proper variable watching is no use.
Hello Ksan,
Alright so we have now have an option to disable scanning except for Corona library functions. Of course this will improve performance and memory footprint significantly and we highly suggest enabling it if you do not use the following features:
Other than that other editor features like code folding, navigation, etc should still work. This will be available in the next update (v 1.9.15)
I don’t understand your comment about variable watching not available in simulator. So how can I watch the variables?
You can watch a variable one of 2 ways.
the “add watch” button is supposed to use loadstring to execute more complex watches but this is not available in Corona. We really only have 2 options here
Regards,
M.Y. developers
Ok. I’ll try again when the new version is out. When is that going to happen? Any ETA? How about not being able to open projects? I read about others having the same issue and deleting the user directory. That didn’t work for me. How about not being able to go between variable state snapshots? I don’t see that Back button even though I change the snapshot period to 3 seconds from the -1 which was the sys default.
Hello Ksan,
How about not being able to open projects?
How about not being able to go between variable state snapshots? I don’t see that Back button even though I change the snapshot period to 3 seconds from the -1 which was the sys default.
We will look into and fix the snapshot issue, currently there are just too many more really important issues in queue. Opening projects should always work, can you send a screenshot of what your open project dialog looks like?
When is that going to happen? Any ETA?
A fix for the sluggishness will be out shortly, I would estimate within a day or 2. A fix for the Java 7 bugs is out of our control. We are actually planning to just backport everything to Java 6 and wait for them to fix the bugs before upgrading to 7 again. The backport might take up to a week to implement and test.
Thanks for understanding,
M.Y. Developers
Open projects is working now somehow after user directory delete and a good night’s sleep.
Will wait for the next version to see how the performance issue turns out. I actually want to be able to see my globals and what not so turning the scanning down is not such a good idea but I’ll see.
Hello Ksan,
Have you tried this setup?
http://view.xscreenshot.com/a05603eb7d378f70f4aff5cfeeafee4a
Regards,
M.Y. Developers
Was using Ram but setting was at Main.lua + requires. Changed it to current file + requires. I will observe.
Alright. We will probably add another option in there (Only current file.) Just out of curiosity have you tried Glider on another computer? How about a windows machine?
Regards,
M.Y. Developers
No. Didn’t try it on another machine. Will try to try later on. 
Hello Ksan,
Please get the 1.9.15 update via help-> check for updates. By no means is this a permanent fix but it will make Glider usable until we can fix it for good. Please try this option:
http://view.xscreenshot.com/10a947a600f796601cf52664108dc6a0
And let us know how that works out for you.
Regards,
M.Y. Developers
Thanks. Got it and changed settings. I will use it today and report how it goes. Thanks for hearing us out and making continual improvements.
It is much better now. I use the “Scan only current file + requires” option as I like the ability to jump to functions and see globals etc from the Navigator. Seems more stable now. Look forward to having the debug snapshot function coming back. Thanks for your efforts.
Hello Ksan,
Thanks for your feedback. We just released a 1.9.2 that provides some further stability improvements. Please let us know of any more improvements, we will re-introduce the snapshot support once we figure out a good way to do it sustainably. The previous implementation was way too slow to be useful in large projects.
Regards,
M.Y. Developers
Sounds great! Got 1.9.2. Will let you know if things go south again. All the best
2 crashes (beach ball) since the most recent update (1.9.21 I think). Logs uploaded.
Hello Ksan,
Sorry you are experiencing so many issues. Did all these problems happen today?
A lot of CPU overload. Find in projects / replace in projects is helping me a lot but the rest is not helping my productivity.
It seems you are not using the feature that is probably taking up all the CPU usage (auto-completion) so we are making a new option to disable scanning of everything except the Corona stubs. It is a bit extreme but if it is not used then there is no point in scanning anything.
Variable watching is very inconsistent.
In order for this to work properly we need to loadstring function to execute dynamic code. This is not available in the Corona simulator.
Debug isn’t working well. The back button I see on the Advanced Debug video does not show even though I change the code sampling period to 3 seconds.
Do at least breakpoints work?
Regards,
M.Y. Developers
Thanks for your prompt response. Being able to disable all scanning sounds like a good idea. These issues did not all surface today. I have been putting up with it so long for the advantages but today I just can’t do it anymore. Will be back once it gets better.
I don’t understand your comment about variable watching not available in simulator. So how can I watch the variables?
Yes the breakpoints work. I wish the back button worked as demonstrated on the video tutorial but debugging without proper variable watching is no use.
Hello Ksan,
Alright so we have now have an option to disable scanning except for Corona library functions. Of course this will improve performance and memory footprint significantly and we highly suggest enabling it if you do not use the following features:
Other than that other editor features like code folding, navigation, etc should still work. This will be available in the next update (v 1.9.15)
I don’t understand your comment about variable watching not available in simulator. So how can I watch the variables?
You can watch a variable one of 2 ways.
the “add watch” button is supposed to use loadstring to execute more complex watches but this is not available in Corona. We really only have 2 options here
Regards,
M.Y. developers