Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 04/12/2012 at 12:17, xxxxxxxx wrote:
User Information: Cinema 4D Version: 14 Platform: Windows ; Language(s) : C++ ;
--------- is it possible to run the plugin from different folder example: normal plugin is located at Maxon\cinema4d\plugins\myplugin
can i make it run from path (for example) "c:\myplugin"
On 04/12/2012 at 13:58, xxxxxxxx wrote:
No, it isn't, unless you don't load the plugin yourself from a plugin which again lies in Cinema 4D's plugin directory.
-Nik
On 04/12/2012 at 14:04, xxxxxxxx wrote:
well i want to do this ...but how (i know i need to load the plugin custom folder path from another plugin inside cinema4d plugins folder) i just need basic steps no need for actual code
On 04/12/2012 at 14:33, xxxxxxxx wrote:
You should be able to do this using an Environment Variable set up. Did this long ago for a while but its very "global" (All Cinema versions see this link)
Some efforts here: http://forums.cgsociety.org/showthread.php?f=47&t;=948633&highlight;=Environment
Cheers Lennart
On 04/12/2012 at 20:01, xxxxxxxx wrote:
well from what i've seen (what i understand) is that you have changed environment variables to force cinema4d to look at the folder u want ...but that's not exactly what i want (as i want my plugin to be shipped and don't know if it will be possible to change other ppl environment variables in windows)
what I (imagined) to be possible is to: 1-make the main plugin file .cdl/.cdl64 inside cinema4d plugins folder 2-make a part in that main plugin file to refer to a custom path of another precompiled plugin file (another .cdl/.cdl64) -_- like loading plugin from another plugin (if this is possible)
On 04/12/2012 at 23:28, xxxxxxxx wrote:
1. Load the library (using the OS API) 2. Redirect PluginStart(), PluginMessage() and PluginEnd() to it.
Best, Niklas
On 05/12/2012 at 06:31, xxxxxxxx wrote:
thanks alot niklas I think it should do the trick (though i didn't test it yet) but looking promising