How to: Fixing Various Mac Developer Hangs

[mboegem]

many developer bugs/hangs that David numbered out in the top post are mac specific

1> blank screens: mac only

Johan, any news on this one?
Just spent (too) much time on helping a Mac colleague, ended up trying to find this post.
As for a solution: David's 'fix2' did it, so something must be wrong in the file(s) he mentioned.

[jcompagner]

and that is just some kind of threading issue,
if you delete that file then there is a little more time at some point creating that file again, and that seems to be the trigger some how.
Strange thing is if i fake this extra time, then it doesn't have that same effect...

[mboegem]

if you delete that file then there is a little more time at some point creating that file again, and that seems to be the trigger some how.
Strange thing is if i fake this extra time, then it doesn't have that same effect...

and there's no way to automate the delete action when executing the client?
or at least create some kind of cleanup button for our fellow Mac users?

[Harjo]

marc,

In my case, I had never to delete that file!

I only have to take care, that there are no, global.js tab (window) open in eclipse
if that's true, in my case, the debug client always opens!! if the first start was succesfull, than opening globals.js, has no issue, even when your restart a debug client.

So, to keep it short, when I close eclipse, I always, take care of that all tab's (window) are closed before.
than (again, in my case) the debug client always opens fine the first time!

[rafig]

I have noticed that what I need to do is as soon as Serclipse has launched and everything is built, launch Debug Client, then you can quit it, do stuff in Serclipse and from then on (in that session) Client will always open.
You also need to be careful to make sure Client is not running when you quit Serclipse.

Rafi

[mboegem]

guys, thnkx for the feedback.
I still hope there will be a fix for this issue at some point.

From what I understand my colleague will try to write a separate start-up file for his installation.
Hope that will keep him working!

[rioba]

and there's no way to automate the delete action when executing the client?
or at least create some kind of cleanup button for our fellow Mac users?

I have created an Automator action that deletes the file and then starts Servoy. I should say that now that blank screen doesn't appear any more, or maybe just once every hundred restarts. If you are interested in this Automator Action, please let me know.

[IT2Be]

Hi Rioba,

I would love to test your automator action. Can you maybe post it to the forum?

[rioba]

Hi Marcel,

I enclose the Automator Action (Servoy Automator) as a zip file. As you will see I have also made a custom icon combining the Servoy icon with the Automator one so it can be easily recognized on the dock or the desktop.

After unzipping you must change 2 lines in the file "document.wflow" inside the application package. These are the steps:
a) right click on the "Servoy Automator" application and select "Show Package Contents";
b) using a text editor (such as BBEdit, TextWrangler, Smultron, Editra, aso) search the following text (it starts at line 51)

Code: Select all

<array>
   <string>~/Servoy 5.2/servoy_workspace/.metadata/.plugins/org.eclipse.debug.core/.launches/globals.js.launch</string>
</array>

and modify the text between <string> and </string> for the path to the "globals.js.launch" file on your disk (you could just change the string "~/Servoy 5.2/servoy_workspace/" to path of your Eclipse workspace folder)
c) do the same for the string (at line 325)

Code: Select all

<dict>
   <key>appPath</key>
   <string>~/Servoy 5.2/developer/servoy.app</string>
</dict>

Change the text enclosed in <string></string> to the path of the Servoy application. Here too it would suffice to change the string "~/Servoy 5.2/" to the location of you Servoy developer folder.

I am not sure (I have used this application on my computer only), but it may be necessary to change the Servoy Automator privileges (cmd-i on the application icon and set the administrator name with read & write privileges)

[IT2Be]

Hi Rioba,

I will check this out one of these days. Looks good

Thank you for this!

[IT2Be]

Hmm, the rights are ok but the automator remains active after starting it and when closing Servoy the automator starts it up a second time with a dialog saying that the action 'Launch Application' encountered a problem.

I will investigate this later. I have done quite a few applescripts but never an automator so it could take some time...

[rioba]

I checked the script and I can't find any reason for this behavior. On my computer it works ok. I have tested it in Mac OS X 10.5 and 10.6.

[IT2Be]

Hi Rioba,

No problem, I will figure it out and let you know

I am already happy with the script so that I have a starting point...