Stuck with Spinning Beach Ball at launch.

Glider (IDE)
#1

When launching Lua Glider v19, after the splash screen disappears I see the main window with the “Welcome / Basic Startup” explanation image, but the Spinning Beach Ball does not go away.

I get the “5 updates found” balloon in the lower right corner (but cannot click it).

I have installed the latest Java Verison 7u40, and can confirm this in the System Preferences -> Java.

I have tried reinstalling the application (and deleting ~/Library/Application Support/luagliderv19), but this does not change anything.

This is very frustrating, since I just bought the Glider license.

Please help,

Thomas

#2

Anybody from Support?

#3

Hello Thomers,

Sorry about the delay in getting to you. Please provide more information about the platform you are using (which Mac version?). Did the program ever start in the past properly and this problem just recently started? The Java version on your system is not the one used by Glider so Java issues should not be a problem. Generally clearing the user directory should reset the application to pristine state.

Regards,

M.Y. Developers

#4

Anybody from Support?

#5

Hello Thomers,

Sorry about the delay in getting to you. Please provide more information about the platform you are using (which Mac version?). Did the program ever start in the past properly and this problem just recently started? The Java version on your system is not the one used by Glider so Java issues should not be a problem. Generally clearing the user directory should reset the application to pristine state.

Regards,

M.Y. Developers

#6

This is exactly the problem I am having after just buying.   I created a couple of new Mac accounts, one admin and one user, copied the application across to each and it works perfectly on both other accounts.

I’ve followed the guidance to remove the directory files, I’ve removed everything and redownloaded, I’ve run fix disk permissions and disk.  I’ve tried running it from a different location, e.g. desktop and from within the dmg file.   Once in a while the program (maybe one in twenty times) will actually work properly.

I’m at a loss.

#7

Hello Coldwilson, 

We had a similar case we followed via email. The solution was resolved after installing Java 8. Does this sound familiar to you?

Regards,

M.Y. Developers

#8

Still having this problem, now with the latest 2.0 version.

As far as I know, Java 8 is still “early access”, which version do you mean exactly? And - in a previous reply you mentioned

 

The Java version on your system is not the one used by Glider so Java issues should not be a problem. 

So I’m surprised that the installed Java version should make a difference?

Best,

Thomas

#9

I got this working.

I looked at my system logs and could see it was always showing netbeans as the problem.  So I installed the latest Netbeans IDE on its own from their site.  This didn’t fix Glider but I did find that netbeans also froze the same way and therefore it was more about netbeans not working than Glider .  Netbeans had a lot of forum activity on that issue going back a year or more but was supposed to be fixed.  The route seemed to be upgrading java. I tried with the latest java (7.4) but netbeans still froze.  I then tried the early access java 8 and netbeans started working.   

However, much to my frustration, Glider still didn’t work.   I fed this back to the team and they sent the following below.   I commented out their link to java in the conf file as they said and it worked right away.  So it’s now using the system version of java rather than what they’ve included in the package.  So it looks like they ought to upgrade their package.

Hope that helps anyone with the same problem.

"Glider comes with a bundled java version so you do not have to mess with the java installations. However you think this is the source of the problem you can force it to use the one installed on the system. 

 

First open the app package by right clicking -> show package contents. Next edit the luaglider2.conf file"

 

They sent an image but I can’t copy it here for some reason so here’s the change.

 

open the package contents and go to  Contents/Resources/luaglider2/etc

 

There’s a file called luaglider2.conf.

 

Open that and you see this:

 

default location of JDK/JRE, can be overridden by using --jdkhome <dir> switch

jdkhome=“jre/Contents/Home/”

change it to this:

default location of JDK/JRE, can be overridden by using --jdkhome <dir> switch

# jdkhome=“jre/Contents/Home/”

Save and close - that’s it.

#10

Hello Coldwilson,

Thank you for taking the time to put up this solution for everyone to see. We really appreciate the time you put into this. Java support for Mac was much better when Apple used to maintain it themselves but since the control has gone over to Oracle they always seem to be one release behind of the latest and greatest OS X updates. 

Have you noticed any problems with the early access version?

Regards,

M.Y. Developers

#11

No problem, glad it worked, having tried almost every IDE and editor I can find and I love LuaGlider.  I do have some challenges with it (I can’t seem to resize the project pane narrower than about a third) but it covers all the areas you’d want in an IDE, most seem to be missing something.

I’m not all that technical so just followed my nose really and got lucky, plus your help.  So in terms of Java early release I can’t say whether it’s causing any problems.  I went for it as a last resort as even the most up to date builds for 7.4 weren’t working.   I’ve not noticed any issues yet and I’ve been using LuaGlider for the past week or so without any major issues.  The occasional hang that’s all.

What I still can’t fathom out though is why (before I upgraded to java 8)  it worked perfectly with your package in a new user environment using the version of java you include.  There must be something on my main account that’s buggering up things.  I was half contemplating migrating all my stuff over to the new account to resolve the issue.

Cheers

#12

This is exactly the problem I am having after just buying.   I created a couple of new Mac accounts, one admin and one user, copied the application across to each and it works perfectly on both other accounts.

I’ve followed the guidance to remove the directory files, I’ve removed everything and redownloaded, I’ve run fix disk permissions and disk.  I’ve tried running it from a different location, e.g. desktop and from within the dmg file.   Once in a while the program (maybe one in twenty times) will actually work properly.

I’m at a loss.

#13

Hello Coldwilson, 

We had a similar case we followed via email. The solution was resolved after installing Java 8. Does this sound familiar to you?

Regards,

M.Y. Developers

#14

Still having this problem, now with the latest 2.0 version.

As far as I know, Java 8 is still “early access”, which version do you mean exactly? And - in a previous reply you mentioned

 

The Java version on your system is not the one used by Glider so Java issues should not be a problem. 

So I’m surprised that the installed Java version should make a difference?

Best,

Thomas

#15

I got this working.

I looked at my system logs and could see it was always showing netbeans as the problem.  So I installed the latest Netbeans IDE on its own from their site.  This didn’t fix Glider but I did find that netbeans also froze the same way and therefore it was more about netbeans not working than Glider .  Netbeans had a lot of forum activity on that issue going back a year or more but was supposed to be fixed.  The route seemed to be upgrading java. I tried with the latest java (7.4) but netbeans still froze.  I then tried the early access java 8 and netbeans started working.   

However, much to my frustration, Glider still didn’t work.   I fed this back to the team and they sent the following below.   I commented out their link to java in the conf file as they said and it worked right away.  So it’s now using the system version of java rather than what they’ve included in the package.  So it looks like they ought to upgrade their package.

Hope that helps anyone with the same problem.

"Glider comes with a bundled java version so you do not have to mess with the java installations. However you think this is the source of the problem you can force it to use the one installed on the system. 

 

First open the app package by right clicking -> show package contents. Next edit the luaglider2.conf file"

 

They sent an image but I can’t copy it here for some reason so here’s the change.

 

open the package contents and go to  Contents/Resources/luaglider2/etc

 

There’s a file called luaglider2.conf.

 

Open that and you see this:

 

default location of JDK/JRE, can be overridden by using --jdkhome <dir> switch

jdkhome=“jre/Contents/Home/”

change it to this:

default location of JDK/JRE, can be overridden by using --jdkhome <dir> switch

# jdkhome=“jre/Contents/Home/”

Save and close - that’s it.

#16

Hello Coldwilson,

Thank you for taking the time to put up this solution for everyone to see. We really appreciate the time you put into this. Java support for Mac was much better when Apple used to maintain it themselves but since the control has gone over to Oracle they always seem to be one release behind of the latest and greatest OS X updates. 

Have you noticed any problems with the early access version?

Regards,

M.Y. Developers

#17

No problem, glad it worked, having tried almost every IDE and editor I can find and I love LuaGlider.  I do have some challenges with it (I can’t seem to resize the project pane narrower than about a third) but it covers all the areas you’d want in an IDE, most seem to be missing something.

I’m not all that technical so just followed my nose really and got lucky, plus your help.  So in terms of Java early release I can’t say whether it’s causing any problems.  I went for it as a last resort as even the most up to date builds for 7.4 weren’t working.   I’ve not noticed any issues yet and I’ve been using LuaGlider for the past week or so without any major issues.  The occasional hang that’s all.

What I still can’t fathom out though is why (before I upgraded to java 8)  it worked perfectly with your package in a new user environment using the version of java you include.  There must be something on my main account that’s buggering up things.  I was half contemplating migrating all my stuff over to the new account to resolve the issue.

Cheers