Re: Plugin cached?

Hey Dan, hope you're well! Well, I usually get the handle on both the Property itself and the Layout and then pass those to my method: *oProp = PPG.Inspected[0]* *oLayout = PPG.PPGLayout* *buildPPGLayout(oProp, oLayout)* The other thing I noticed is that your itemsComboArray initialisation has

Re: Plugin cached?

Thank you Stephen. Martin had helped me resolve this off-list and I was about to post the solution. That was indeed the issue. Ended up like this: def DY_propTest_DefineLayout( in_ctxt ): return True def DY_propTest_ComboMode_OnChanged(): oProp = PPG.Inspected[0]

Re: Plugin cached?

The PPG object is available in callbacks like OnClicked. Like the doc says: This object can be manipulated within the event handling script code associated with a PPGLayout. So, not in DefineLayout. In DefineLayout, you should get the PPGLayout object and pass that to your rebuild function.

Re: Plugin cached?

OK, I'll admit I'm little wet behind the ears when it comes to this sort of thing. Could someone explain why I get a "# NameError: global name 'PPG' is not defined" error with this test property. http://pastebin.com/Z0YYSVbs Many thanks, DAN On Fri, Dec 11, 2015 at 12:14 AM, Stephen Blair

Re: Color shift w/ QuickTime

Time for H.265 ! On 11 December 2015 at 09:29, christian wrote: > what codec are you using though ? the quicktime h.264 i assume which is > horrible with gamma and colors. > > we usually use not the quicktime > h.264 one but the one just labeled > h.264. file ending should

Friday Flashback #253

>From the pile of old graphic elements: a Sumatra banner (circa 07 April 1999) http://wp.me/powV4-3fL

Re: Color shift w/ QuickTime

Hello, here we usually don't conform media with an adobe product, the quality is horrible. The keep the gamma right from top to bottom first, use a proper codec, the "x264" encoder. This codec is 100% compatible and used by every "Linux" server, YouTube / Vimeo / also The codec behind nuke h264