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 been missing the corresponding integer values, it should be something like this: *itemsComboArray = ["ItemA", 0, "ItemB", 1, "ItemC", 2]* Here's a pastebin link to a version that's working on my side: http://pastebin.com/CvT5VmE6 Cheers, Martin -- Martin Chatterjee [ Freelance Technical Director ] [ http://www.chatterjee.de ] [ https://vimeo.com/chatterjee ] On Fri, Dec 11, 2015 at 11:08 AM, Dan Yargici <danyarg...@gmail.com> wrote: > 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 <stephenrbl...@gmail.com> > wrote: > >> Plugins are cached (right click one in the Plugin Manager). >> >> And there's a cache of PPG layouts. >> >> Never had the global PPG not defined problem. >> >> On Thu, Dec 10, 2015 at 4:54 PM, Dan Yargici <danyarg...@gmail.com> >> wrote: >> >>> I have been tearing my hear out for hours now while working with a >>> plugin not knowing if I'm seeing the updates I've been making. >>> >>> It's total voodoo. Sometimes when I reload, all is well, sometimes I'll >>> break something on purpose to be certain that it's reloading/updating >>> correctly only to find that it actually isn't and it still works despite >>> the fact that I broke *hard coded paths*! >>> >>> I just thought I'd finally got this thing nailed and then restarted Soft >>> only to find it was broken again! >>> >>> What's puzzling me is that accessing PPG from the plugin seems to be >>> intermittent (it complains that no global 'PPG' has been defined) and also >>> sometimes it won't fire the callbacks like OnChanged. >>> >>> Anyone else experienced this behaviour? >>> >>> Tried on 2013_SP2 and the trial for 2015_SP2, both the same. >>> >>> Cheers, >>> >>> DAN >>> >> >> >
