Servoy Forum

Never seen this on 3.5.12 please open your java console, and see what errors you get...
this must be an other problem.

No errors.

As the client crashes, I can't cut and paste the text.
But it just says
date "com.servoy.j2db.util.Debug log"
then the
Servoy ver and Java ver numbers

so no help

- - -

What does fix it is this
On the client.
Go to Java Preferences
and in Advanced
turn off
Verify Mixed security code (sandbox vs. trusted)

- - - -

Like I said
Javaaarrgghhh!

I have also experienced this frustrating behavior in both Servoy 4 and 5 since I've started using Servoy (Over 1 year now).
It seems like it just happens randomly.
I just keep restarting Servoy Developer, and it usually works after a few restarts.
Sometimes it seems restarting the Mac OS Helps also.
I hope someone would fix all these quirks...
thanks

The blank screens are caused by a nasty race condition on the mac between awt/swing and swt at startup of developer.
Next 5.2 build contains a fix that hopefully reduces the blank screens.

Rob

Ah, the Mac races too fast for Servoy .-)

Robert

rgansevles wrote:The blank screens are caused by a nasty race condition on the mac between awt/swing and swt at startup of developer.
Next 5.2 build contains a fix that hopefully reduces the blank screens.

Rob

Rob, any idea when the release of 5.2 that fixes this problem will be ready? I'm really stuck. I've tried all the suggested in previous posts and still can't run Smart Client so can't see what's broken after the upgrade.

Kurt,

This change is included in 5.2 rc1 which is released last week.
Servoy 5.2 final is expected to be released this month.

Rob

I have been using 5.2rc1 and rc2 for a while now, but the blank client issue is still there, and nastier than ever I would say. In my case (Mac OS 10.6.4 with latest Java update) I get it every time I start the debug client, and it seems to me that it is occurring more frequently than in 5.1. However, deleting the globals.js.launch file in the workspace/.metadata/.plugins/org.eclipse.debug.core/.launches seems to work most of the times (but not always). So to avoid using the Terminal and typing everything each time, I have made an Automator action. When double-clicked it first deletes the globals.js.launch file and then starts Servoy

This grey screens issue is giving me similar hair.

We have could not reproduce this on our macs, but we have tried another fix in next build.

Rob

Still a real problem. Just shut down Servoy developer 5.2, shut down dbsrv11 and restarted, so far 10 times. Still get the blank screen. The only time Smart Client will work is when the Community splash screen appears. Then, consistently, the launch is successful.

Thanks for your help. K

and if you keep sybase?
works it better then?
we are testing with postgresql which by default works like you describe (start everytime and shutdowned everytime)

this is just a very hard issue to fix (if that is even possible, dont think so) because it is mainly a threading issue. If for example it helps to delete the global.js.lauch files then this only helps because the launching of a client will take a little bit more time!
but there are many places in the start up that it can go wrong, and the speed of your mac is also very important because the timings you get are different that when i take our test mac..

Happened to me yesterday on my mac with 5.2 rc4 and Microsoft SQL server 2005 (always running). Had to quit servoy developer and reopen three times. Almost always happens if I try to quit developer without manually closing client first (quit of developer on mac will not exit client launched from developer, ever) and closing all methods, ESP globals. Eventually the community edition splash shows up and I know it is going to work again. Just more info for your testing. I am on a 2.4ghz MacBook pro.

for me if i let the client stay open, yes the closing of the developer takes way way more time then when you close the client first
But it will close it for me

I am afraid that we cant do much more at this point it is working for us on our test systems
What you can try to do is play a bit with this property:

servoy.developer.startsc.delay

You can add that one to the servoy.properties file
By default the value is set to 1000 (1 second) on the mac. (windows it is just 0)
You can increase that value and see if that does anything for you do 3000 or something
This is purely when launching the debug client. So for the onces that say deleting globals.js.launch files before you start that property should help.

Also when you press the button of launch smart client.. Dont move anything in the developer ui anymore. Try not to do anything with the mouse or keyboard until the client is there
Any extra event there could trigger a blank screen in the smart client...

You really can't reproduce this just by leaving globals.js open when you quit developer, reopen developer, try launching client. That's always a blank screen for me. Just wondering...

no i cant but that can greatly depend on what you do in your globals.js file
For example do you also have it with an empty global.js file open?