You mean like the .spdl and .preset formats?
nope at all, I mean like a specification file. plugins specifications are
usually little xml/json files where all informations relative to the plugin
are written (what you do with the PluginRegistrar::Put* calls). This has
mainly two big advantages wh
Yep cached. That explains it.
On Fri, Oct 26, 2012 at 4:37 PM, Kamen Lilov wrote:
> On 10/26/2012 7:52 PM, Nicolas Burtnyk wrote:
>>
>> I'm confused. I just tested this and global variable constructors
>> only get called once in my plugin (on 2012 SP1).
>>
> Nicolas, is your plugin DLL marked
On 10/26/2012 7:52 PM, Nicolas Burtnyk wrote:
I'm confused. I just tested this and global variable constructors
only get called once in my plugin (on 2012 SP1).
Nicolas, is your plugin DLL marked as 'cached'?
Because I double-checked the mechanism explained by Marc-Andre, turns
out he's righ
; glad the self installing stuff came online to replace it.
>
>
>
> Matt
>
>
>
>
>
>
>
> From: softimage-boun...@listproc.autodesk.com
> [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of jo benayoun
> Sent: Friday, October 26, 2012 9:28 AM
>
&g
softimage@listproc.autodesk.com
Subject: Re: SDK: When *exactly* does XSIUnloadPlugin get called
I guess the plugin is loaded once for discovering and registration (plugin
manager), and then reloaded for getting the actual features (actual extension
of features).
Usually, plugin systems use a specific
t; plugins in memory after registration like Maya does.
>
> -mab
>
>
> From: softimage-boun...@listproc.autodesk.com
> [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of jo benayoun
> Sent: Friday, October 26, 2012 12:28 PM
> To: softimage@listproc.autodesk.com
>
On Fri, Oct 26, 2012 at 12:52 PM, Nicolas Burtnyk
wrote:
> I'm confused. I just tested this and global variable constructors
> only get called once in my plugin (on 2012 SP1).
how did you test this.. if you're in the debugger the .dll probably
remains in memory due to the debugging process
...@listproc.autodesk.com] On Behalf Of jo benayoun
Sent: Friday, October 26, 2012 12:28 PM
To: softimage@listproc.autodesk.com
Subject: Re: SDK: When *exactly* does XSIUnloadPlugin get called
I guess the plugin is loaded once for discovering and registration (plugin
manager), and then reloaded for getting the
I'm confused. I just tested this and global variable constructors
only get called once in my plugin (on 2012 SP1).
On Fri, Oct 26, 2012 at 9:27 AM, jo benayoun wrote:
> I guess the plugin is loaded once for discovering and registration (plugin
> manager), and then reloaded for getting the actua
That's correct.
-Original Message-
From: softimage-boun...@listproc.autodesk.com
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Luc-Eric Rousseau
Sent: Friday, October 26, 2012 11:22 AM
To: softimage@listproc.autodesk.com
Subject: Re: SDK: When *exactly*
I guess the plugin is loaded once for discovering and registration (plugin
manager), and then reloaded for getting the actual features (actual
extension of features).
Usually, plugin systems use a specification file for each new plugin (xml
or other) that is in charge of describing (description, na
sounds like if you put some code in the constructor of a global
variable, then you'd be called twice per xsi session, since your dll
will be loaded and unloaded twice?
On Fri, Oct 26, 2012 at 9:34 AM, Marc-Andre Belzile
wrote:
> Sorry for not being clear enough. When a plugin is loaded at startup
ll is loaded back.
-mab
From: softimage-boun...@listproc.autodesk.com
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Kamen Lilov
Sent: Thursday, October 25, 2012 9:25 PM
To: softimage@listproc.autodesk.com
Subject: Re: SDK: When *exactly* does XSIUnloadPlugin get called
Marc-
custom commands or events. Ideally we should have
plugin entry-points for allocating and deallocating resources.
-mab
From: softimage-boun...@listproc.autodesk.com
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Kamen Lilov
Sent: Thursday, October 25, 2012 1:58 PM
To: softimage@lis
Of Kamen Lilov
Sent: Thursday, October 25, 2012 1:58 PM
To: softimage@listproc.autodesk.com
Subject: Re: SDK: When *exactly* does XSIUnloadPlugin get called
For example, if XSILoadPlugin() terminates prematurely by returning
XSI::CStatus::Fail, does XSIUnloadPlugin() get called? Or does
XSIUnl
For example, if XSILoadPlugin() terminates prematurely by returning
XSI::CStatus::Fail, does XSIUnloadPlugin() get called? Or does
XSIUnloadPlugin() only get called if XSILoadPlugin() returns
XSI::CStatus::OK indicating the plugin has successfully completed
loading? If XSIUnloadPlugin() gets
I have a developer question from a developer in our building. We've checked
the SDK manuals, but they were ambiguous on the subject.
Our developer is attempting to write a bridge between Softimage and our other
proprietary tools/systems for custom tool development and must allocate many
resour
17 matches
Mail list logo