unload - release usr-dlls

[23fx23]

When working on user modules with sdk, man have to make a lot of back and forth usine<->compiler.
Actually, unless missed someting, the only way to update code is to recompile the module, open usine, load the module, then if want to twak again the code, close usine, recompile, reopen ect..
wich end up being very long for loads but minor tweaks, debug ect..

I thought this could be speeded up a bit by keeping usine open, clearing the workspace, then reload workspace.

but then here the compiler prevents me to overite the module, as it was still 'open'/locked' by usine.exe , even if the workspace is now empty.

Could there be a way to relase/close the dll/usr module so it can be overwritten maybe?, that would be already great speed up time.

[senso]

ok,
I'll add an 'UnloadLibrary' after the module is deleted.
I hope it does the trick, without guaranty.

[sephult]

+1

I just started to use the SDK (warning...lol)

23fx23 is correct....wow very difficult for me...I am lost with certain things to begin with and constantly having to open/close because I am still in that trial and error phase.

Definitely think this is good thing to do.
Which release should we look for?

-s

[sm_jamieson]

ok,
I'll add an 'UnloadLibrary' after the module is deleted.
I hope it does the trick, without guaranty.

Of course there can be more than one module in the workspace using the same DLL, so you have to keep a count and only unload
the DLL when there are no more modules using it. Else as soon as one module is deleted the other ones will crash.

[senso]

Of course there can be more than one module in the workspace using the same DLL, so you have to keep a count and only unload
the DLL when there are no more modules using it. Else as soon as one module is deleted the other ones will crash.

the counter is managed by the system (OSX, WIN) it self. So no risk!
That's why I said "without guaranty"...

[23fx23]

Personally if simpler i would already enjoy with just closing reopening the wksp wich would mean all modules are gone anyway. Unless gigantuc wksp wich is not the case when im debugging its even faster than delete, recreate and rewire the module