Re: FS & Applications
Posted: Thu Mar 31, 2016 11:25 pm
My advice to create DLL for flowstone, it takes into account that it will share resources for each primitive module.
So pay attention to the use of global variables in DLLs.
If you want to create some runnable threads,
you must of course have the ability to keep track of which of the primitive module instance will create it,
with a thread list and some id, so you can finish the right one properly, and to recover the outgoing data,
you must constantly trigger its output, so you can take the data as soon as it is ready,
This way you can create your own detached main loop,
with which you can work in the same way you do with a main exe,
but to care for data exchange from the calling function and the executing thread, using mutex or other arquebuses.
I was working for a few examples, but given the complexity,
in the end, do first to directly use the C ++,
perhaps with the help of some libraries,
so as to have instant gratification,
If you like the program, instead of spaghetti, look here
https://github.com/bclucas/Alloy-Graphics-Library
So pay attention to the use of global variables in DLLs.
If you want to create some runnable threads,
you must of course have the ability to keep track of which of the primitive module instance will create it,
with a thread list and some id, so you can finish the right one properly, and to recover the outgoing data,
you must constantly trigger its output, so you can take the data as soon as it is ready,
This way you can create your own detached main loop,
with which you can work in the same way you do with a main exe,
but to care for data exchange from the calling function and the executing thread, using mutex or other arquebuses.
I was working for a few examples, but given the complexity,
in the end, do first to directly use the C ++,
perhaps with the help of some libraries,
so as to have instant gratification,
If you like the program, instead of spaghetti, look here
https://github.com/bclucas/Alloy-Graphics-Library