Now that modules have us opening and closing solutions so often in developer, can we get rid of the dialog that tells us we have an open solution and to confirm that we wish to close it. If we need that, how about a check box to hide it in the future? This would save our wrists from unnecessary clicking… Thanks.
or maybe this: Modifying modules inside a solution - Classic Servoy - Servoy Community
I think this would be handy and nobody really told me why this shouldn’t be done. Right now I can debug a method in my solution, walk through methods of a module and find something. To fix it, I leave the solution, open the module, modify, go back to the solution and figure out I mistyped something and go the whole way again. I think it would be good enough to know I am inside a module (coloring or whatever)…
Bob Cusick’s suggestion to have the module open in another instance of developer and just reload the main solution works for me.
If a module is used only in one solution and there is only one person developing, I agree that what you suggest should be possible. However, with multiple developers and module being included within multiple solutions, there would need to be some type of module locking added to prevent collisions. Possible? I see no reason why it could not be added.Maybe a right click on the module node to unlock the solution which would cause it to lock in any other instance of developer?
bob cart:
Bob Cusick’s suggestion to have the module open in another instance of developer and just reload the main solution works for me.
I don’t think Mac OSX allows multiple instances of Servoy to run at the same time
raymanj:
bob cart:
Bob Cusick’s suggestion to have the module open in another instance of developer and just reload the main solution works for me.I don’t think Mac OSX allows multiple instances of Servoy to run at the same time :?:
Just copy the Servoy folder and launch the copy.
But make sure you alway launch the original version first to make your your original Servoy repository is open and running.