Debugging with a plugins.dialogs call

Classic Servoy
1

When stepping through code that has a dialog plugins call, when the dialog pops up it pops up blank and can’t be dismissed. Which means force-quitting Servoy developer. Could just be a mac thing, not sure.

I’m fairly certain this has been brought up before. Any update on this one?

Servoy 5.01 on a Mac here.

2

To add why this is important: force-quitting in this situation very often hoses the workspace. Getting developer up and running again after this occurs is one of those fairly annoying things. Troy and I have hosed our workspaces 3 times today between us for various reasons and I’d like to get the land mines we have to look out for reduced a bit.

3

HI David,

that’s exactly why we have switched from subversive to subclipse!!
we have showed Johan, several times our stacktraces & workspaces, and always subversives was the blaim.
after swithing over to subclipse, we have never seen such thing again.

4

Yep, I have ‘lost’ many workspaces due to Subversive as well. Always hanging Servoy when launching.

You can get it back by renaming your old workspace directory and create a new directory with the original name. Then launch Servoy.
After this import the solutions into the new workspace from the old one using the import “Existing projects into workspace” function (make sure you check the “Copy Projects into workspace” checkbox)

I highly recommend using Subclipse instead.

5

david:
When stepping through code that has a dialog plugins call, when the dialog pops up it pops up blank and can’t be dismissed. Which means force-quitting Servoy developer. Could just be a mac thing, not sure.

I’m fairly certain this has been brought up before. Any update on this one?

Servoy 5.01 on a Mac here.

yes this is a mac problem, with form in dialogs we work around it by not letting macs be able to debug method when a form in dialog shows up.

What i do find weird is that you should be able to go to the dialog and dismiss it (but you shouldn’t be able to go to the developer/debugger at that time, you first have to dismiss it)
Weird that you cant even access the dialog close button…