Re: Logging to the history window from a custom renderer

2012-07-06 Thread Kamen Lilov
Hello Nicolas -- There is no built-in way to pass a request (let alone execute a script command) to the UI thread of SI. The workaround is to design a custom message passing system and use a timed event on the main thread. Yes, it is extremely nasty -- I would go so far as to call it a

Re: Logging to the history window from a custom renderer

2012-07-06 Thread Ben Houston
I am pretty sure we are writing to LogMessage from background threads. We have a logging system that routes all messages through a lock though so two messages, even if they are on different threads, are not being written at the same time. That may be addressing the issue you are running into.

Re: Logging to the history window from a custom renderer

2012-07-06 Thread Nicolas Burtnyk
Thanks Kamen for the suggestion of using the timer callback. Re: you guys not experiencing issues with LogMessage... It's quite rare, but we do get the crash sometimes in regular use and I was able to whip together a simple example that causes the crash pretty regularly by calling LogMessage

Re: Logging to the history window from a custom renderer

2012-07-06 Thread Nicolas Burtnyk
Thanks for the tip of using the hidden window. The strings are well formed and don't have strange characters. I can get it to crash by calling LogMessage(crash) many times. The printf trick sounds like a viable alternative as well. I'll try that out. -Nicolas On Fri, Jul 6, 2012 at 11:58 AM,

Re: Logging to the history window from a custom renderer

2012-07-06 Thread Nicolas Burtnyk
Is the VC++ version associated with each version of Softimage documented somewhere? E.g. what VC++ version should be used for Softimage 2012? On Fri, Jul 6, 2012 at 12:07 PM, Nicolas Burtnyk nico...@redshift3d.comwrote: Thanks for the tip of using the hidden window. The strings are well

Re: Logging to the history window from a custom renderer

2012-07-06 Thread Steven Caron
i believe that is vs 2008. i also think softimage 2013 switched to using vs 2010. s On Fri, Jul 6, 2012 at 12:16 PM, Nicolas Burtnyk nico...@redshift3d.comwrote: Is the VC++ version associated with each version of Softimage documented somewhere? E.g. what VC++ version should be used for

RE: Logging to the history window from a custom renderer

2012-07-06 Thread Stephen Blair
Subject: Re: Logging to the history window from a custom renderer i believe that is vs 2008. i also think softimage 2013 switched to using vs 2010. s On Fri, Jul 6, 2012 at 12:16 PM, Nicolas Burtnyk nico...@redshift3d.commailto:nico...@redshift3d.com wrote: Is the VC++ version associated with each

Re: Logging to the history window from a custom renderer

2012-07-06 Thread Nicolas Burtnyk
: softimage-boun...@listproc.autodesk.com [mailto: softimage-boun...@listproc.autodesk.com] On Behalf Of Steven Caron Sent: July-06-12 3:19 PM To: softimage@listproc.autodesk.com Subject: Re: Logging to the history window from a custom renderer i believe that is vs 2008. i also think softimage

RE: Logging to the history window from a custom renderer

2012-07-06 Thread Stephen Blair
-12 3:25 PM To: softimage@listproc.autodesk.com Subject: Re: Logging to the history window from a custom renderer Thanks! Although I'm not particularly thrilled that 2005 is the version to use with XSI 2012... On Fri, Jul 6, 2012 at 12:20 PM, Stephen Blair stephen.bl

Re: Logging to the history window from a custom renderer

2012-07-06 Thread Luc-Eric Rousseau
On Fri, Jul 6, 2012 at 3:16 PM, Nicolas Burtnyk nico...@redshift3d.com wrote: Is the VC++ version associated with each version of Softimage documented somewhere? E.g. what VC++ version should be used for Softimage 2012? It's not documented, apparently. That link that Stephen sent doesn't

Re: Logging to the history window from a custom renderer

2012-07-06 Thread Luc-Eric Rousseau
I've never run into that myself (Softimage runs tons of stuff on PostMessages and timers, including things like property page script logic, the implementation of the printf rerouting to logmessage and the history log itself). if your plug-in must work on linux, I guess you'd look at pushing your