]]>
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! the DLL when there are no more modules using it. Else as soon as one module is deleted the other ones will crash.
That's why I said "without guaranty"...
Statistics: Posted by senso — 22 Sep 2017, 21:32
]]>
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 unloadI'll add an 'UnloadLibrary' after the module is deleted.
I hope it does the trick, without guaranty.
the DLL when there are no more modules using it. Else as soon as one module is deleted the other ones will crash.
Statistics: Posted by sm_jamieson — 22 Sep 2017, 21:17
]]>
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
Statistics: Posted by sephult — 21 Sep 2017, 12:44
]]>
I hope it does the trick, without guaranty.
Statistics: Posted by senso — 20 Sep 2017, 12:39
]]>
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.
Statistics: Posted by 23fx23 — 19 Jul 2017, 08:58
]]>