format of the BlidePI files is:
Line1:BlidePI file version (it has to be 1.0)
Line2:Plug-in Version (it deppends of each plug-in)
Line3:Author name
Line4:Executable name of the Plug-In
Line5:Name of the Plug-In in the BLIde menu
Line6:Description of what the Plug-In does
Line7:Any additional info
When a Plug-in is started, BLIde starts a communication protocol to interact with the Plug-in, so it's not a good idea to put stand-alone EXEs linked to BLIde via BlidePI files. IT can cause several run-time errors. I'll make a add-on manager, to integrate any other EXEs with BLIde, but I suggest not to use the Plug-in engine for this. Anyway, if the EXEs are not using standard output orinput to manage data, the linking could work...
:)
Thanks a lot klepto2 for reporting. As always, your help and suggestions are welcome.
Has anybody else tried the test Plug-in?
Line1:BlidePI file version (it has to be 1.0)
Line2:Plug-in Version (it deppends of each plug-in)
Line3:Author name
Line4:Executable name of the Plug-In
Line5:Name of the Plug-In in the BLIde menu
Line6:Description of what the Plug-In does
Line7:Any additional info
When a Plug-in is started, BLIde starts a communication protocol to interact with the Plug-in, so it's not a good idea to put stand-alone EXEs linked to BLIde via BlidePI files. IT can cause several run-time errors. I'll make a add-on manager, to integrate any other EXEs with BLIde, but I suggest not to use the Plug-in engine for this. Anyway, if the EXEs are not using standard output orinput to manage data, the linking could work...
:)
Thanks a lot klepto2 for reporting. As always, your help and suggestions are welcome.
Has anybody else tried the test Plug-in?