[Perseus Automatic Thread Follower 'Bot Post] Thread Following Rule #1: Follow the thread Thread Following Rule #2: Avoid the Minotaur Thread Following Rule #3: Keep following the thread Thread Following Rule #4: Avoid cutting the thread with sword Thread Following Rule #5: Adhere to Rules #1-#4 Ad Nauseam

Thanks stewer :-) A code sample is, as usual, the most concise way of illustrating the point I was trying to make: Check before assuming.

Any chance that CurrentActor() is returning None, as in nothing selected? You might need to debug it by assigning the function calls to intermediate variables and printing them out. Assuming, of course, that doing so doesn't make the problem vanish ;-) Also, if you're doing a print, it should be able to handle the form: print "ActorName = ", poser.Scene().CurrentActor().Name() without the str() evaluation and string catenation. print can print tuples and dictionaries as well as functions evaluating to None. The inherent assumption (regardless of whether it's a P6 bug or not) of the combined statement is that none of the Scene(), CurrentActor() or Name() evaluations is going to return something that can't be evaluated by the next bit to be parsed - i.e. can't evaluate Name() method if CurrentActor() instance returns None.

@ynsaen Utmost gratitude for this. Had remembered seeing this post ages ago and just purchased Kirwyn's Genesys 2 Hair (inspired by drooling over the P6 forums while I wait for my box). Being on a Mac, the hairCacheFile path was invalid, of course, but while the loading slowdown may have been negligible, it seems to have stuffed up the saving of the dynamics. I could certainly see the dynamics during calculation, but as soon as that finished, the hair seemed to spring back to its default state. All went back to normal expectations when I removed the offending hairCacheFile line and tried again, yay!

??? Is this an example of a problem between the keyboard and the chair??? (Sorry, couldn't resist ;-) [extract tongue from cheek])

Seems as though the foot has two parts, excluding the toes, possibly allowing for flexing of the arch? I also sincerely hope that extreme bending of the thighs will not deform the crotch area of the hip as happens on Millenium figures when the buttocks bend.

So, still no tkInter support on P6 Mac?

@PoseWorks, as stewer says, you need the dialog's Show() method called. Here's an example (hopefully not too OT) which works in P5 on Mac (expect to be waiting weeks to get my boxed P6 in OZ) and pops up an OS X styled file chooser dialog, rather than an XML styled one: initDir = poser.AppLocation() fileIndex = string.rfind(initDir, separator) initDir = initDir[:fileIndex] + ":Runtime:libraries:Pose" figure = scene.CurrentFigure() initFile = figure.Name() + "_FBM" + pz2ext getSaveFile = poser.DialogFileChooser(type=poser.kDialogFileChooserSave, message="Save Full Body Morph Pose File as:", fileName=initFile, startDir=initDir) if (getSaveFile.Show()): pz2File = getSaveFile.Path() pz2File = pz2File[:string.rfind(pz2File,pz2ext)] + pz2ext # Append extension if missing scene.SaveLibraryPose(pz2File) # Create Icon ... The code above doesn't involve any button callbacks as there is no XML parent dialog displayed prior to the File Save. I discovered the poser.DialogFileChooser (as opposed to DialogDirChooser) by searching the P5 binary for strings and looking at the XML files. Parameters were determined by guesswork and trial & error.

miked123, this brings to mind something I was playing with when looking at ockham's jiggles script. At one point, a body part morph value is modified by a little bit to determine the average direction the morph moves and then set back to its previous value. Unfortunately, what Poser Python (at least in P5) gives you for the morph.Value() is NOT that body part's morph dial setting, but the accumulated effect of PBM and JCM influences in addition to the local dial setting. If you have any active PBM or JCM effects, a loop getting and setting the morph value for the body part repeatedly will exponentially increase the effect. To try and counteract this, I developed a little function which takes a morph (actor.parameter), gets its current value and splits that into PBM/JCM (delta) and local dial parts and returns them, resetting the value without modification. def DialAndDelta(Morph): val1 = Morph.Value() # read value Morph.SetValue(val1) # set same value val2 = Morph.Value() # get new value delta = val2 - val1 # find FBM or JCM delta influence val0 = val1 - delta # find original parameter dial value for this actor Morph.SetValue(val0) # reset to original value return (val0, delta) example using DialAndDelta: for OneMorph in TheActor.Parameters(): if OneMorph.IsMorphTarget(): (dial, delta) = DialAndDelta(OneMorph) OneMorph.SetValue(-delta+0.001) # Set morph upward a bit without delta influence ... For a given body part, you could traverse back up the actor parent chain collecting all the PBM dial values for a given morph. Hope this is useful :-)

Found it. Fantasy3D.com. Just emailed Underdog to register.

Point me there and it's done.

Ditto tyd2. We're paying the shipping costs as appropropriate, but we're damned if we have to pay brokerage or currency exchange fees for a ridiculous intermediate currency. Digital River, hear our cries. In this era of electronic fund transfers and automatic currency conversions, don't punish your Southern Hemisphere clients unnecessarily. Let OUR credit providers do the currency exchange and bill us in $US.

@andygraph, sorry for the delay. Since you have that compressPoserFiles.py file, can you run it successfully? I don't mean to compress any files, just to see if it pops up a Mac OS style dialog, rather than one of the XML type dialogs.

andygraph, I've attached another version with a little bit of debugging. Just a couple of print statements. The thing I'm worried about is that you may not have a Pro Pack equivalent to the P5 poser.DialogFileChooser function. In the P5 directory ...:Poser 5:Runtime:Python:poserScripts:Utility:, there is a file called uncompressPoserFiles.py. this is one of the sample utility scripts supplied with P5. It has an equivalent poser.DialogDirChooser function call within it. It was this example which led me (as well as doing a binary string search in the Poser 5 executable) to the appropriate syntax for the DialogFileChooser function. If you can find this python script, or any equivalent (and working) example in your Pro Pack Python directories, there may be enough to give me a clue how to proceed. Otherwise, I think we'll be stumped.

Damn. I've just looked back at some of your earlier posts andygraph and it looks like your running P4 Pro Pack, if I'm reading the Runtime path correctly. I don't have Pro Pack, but IIRC there are substantial differences between it and P5 Python. I wouldn't be at all surprised if the SimpleDialogs in my script were only included with Poser 5 and therefore won't work at all for you, I'm afraid.