To clarify: Particles 2 can use "sprites" (alpha-ed planes that always face towards the camera, no matter which way you move it) or any fully-3D object you want. Sprites are a great way to get fantastical effects (like the fire on the splash page), or you might care to use 3D objects (like the feathery stars in one of the sample images). Most game engines use sprites to generate their special effects, to give you some idea of how these new shapes could be applied.

There's no native PoserPy method to open compressed files; you'll have to un-gzip the file before you open it.

Actor.OnOff() refers to whether or not the actor representing the light is displayed in the scene, not whether or not the light is turned on. Since Poser's global lights don't display by default, you're getting zero for all of them. As far as I know, there's no way to directly query whether a light is turned on or off. (Unfortunately, you can't access it as a Parameter either.) You would have to use Scene.SaveLibraryLight() and then collect the information from the LT2 file.

Face_off--be sure to use a "caller" script like the one described in the WooYah thread to kill the PyTrojan figure and then process its deletion. Ockham--I've noticed that the interface will cling to remnants of PyTrojanFig, but as long as you have the script process a Poser event after deletion, there should be no trace of the PyTrojanFig after your script is done running. What artifacts/messiness have you encountered? LtD--Could you describe this technique some more? It sounds promising.

Attached Link: http://wooyah.com/ubbt/prod/showflat.php?Cat=&Number=7028&page=0&view=collapsed&sb=5&o=&fpart=1

You could try setting a callback with after_idle([,args]) that would set WM_DELETE_WINDOW to a function of your choosing (one that didn't delete windows at all) after the alien script had gone to the mainloop. An example would be: ------------------- > def nullify(): > -----pass > def reset_x(master): #may need an event arg too, not sure > -----master.protocol('WM_DELETE_WINDOW',nullify) > master.after_idle(reset_x, master) > exec("script.py") ------------------- This has the unhappy side-effect of making the user unable to destroy windows through the system's close button though. If you know that the script that you want to execute is safe, you could do something like this: ------------------- file = open("script.py",'r') file_data = file.read() file.close() import re new_data = re.compile("""Tk()""").sub("Toplevel()",file_data) file = open("temp_script.py",'w') file.write(new_data) file.close() exec("temp_script.py") ------------------- But it's somewhat dangerous to monkey with someone else's code. What's the reason for trying to execute someone else's script, and would be consistently be the same script?

When you have two Tk apps, you should use Toplevel for the newest window.

I like to build my window classes with an argument to take a root window. That way I can feed them an appropriate root window:

from Tkinter import *

class NewWin:
-----def init(self, root_win=None):
----------if root_win:
---------------self.root = root_win
----------else:
---------------self.root = Tk()
---------------self.root.protocol('WM_DELETE_WINDOW',self.destroy)
-----def mainloop(self):
----------self.root.mainloop()
-----def destroy(self):
----------self.root.destroy()

if name == 'main':
-----test_win = NewWin()

-----test_win.top = Toplevel()
-----test_win.son_of_test_win = NewWin(test_win.top)

-----test_win.mainloop()

#PoserPython hates it when you end on a tabbed line

You end up with a few more lines of code, but it may be worth it in a multi-window environment. (Remember, any extra windows should ultimately be slaved under the master window [master.slave], that way you can be absolutely sure that everything gets destroyed once the master window is destroyed.)

Message edited on: 12/06/2004 18:34

1. There are a few modules and options that aren't shared between Mac and PC Python, but, by and large, anything non-Tkinter script will work as well on either platform or on Unix as well. 2) Tkinter (Python's GUI [Graphical User Interface] module) does not function very well on Macs, and, by default, does not work at all for Mac PoserPython. PC PoserPython users can expect a little bit of funny behavior from Tkinter, but it largely works as expected. Another thing that might not work in exchange between the two programs are file paths. Windows uses / or to separate folders, but Macs use :. To remedy this situation, Python includes the os.path module which will format paths in your script according to the operating system it's being run on.

It's main use is definitely to simulate JCM. It can go beyond the traditional JCM set ups as well because it can use multiple dials and more robust math than addition and subtraction in figuring a parameter's value. Additionally, it's the only way to date to do this from inside of Poser, which lets you get real time feed back and make your changes a lot faster than text editting the cr2. Aside from linking dials together, it can simplify a few tasks in setting up a still scene (getting things to move relative to one another while you're tweaking your composition), but the main applications are for animation or building specialized figures (like a robot who would have moving gears). I hope this helps, if you'd like to see a bit more about how the product works, you can visit http://poseworks.8m.com/support.html and view the help files for PowerDials and Manager online.

PowerDials comes with a bonus utillity--Manager--that provides a much faster way to find, add and categorize your Python scripts. Manager is of most use to people who have a larger number of Python scripts, people who use the scripts regularly, or for people who don't know how to script and want to add buttons onto the Python window.

The trouble isn't actually manipulating the Poser figure's parameters: it's creating software sophisticated enough to not only recognize a part of a photograph as a human face, but then to recognize and read in three dimensions each feature of that face. There is software for facial recognition, but it's very complex and imperfect at best. What you're asking is unfortunately out of range for Poser for quite some time.

I am still alive (been busy with school), thank you for the purchase and good words :-) I don't have plans to adapt MKParticles to Poser 5 at the moment, but I might have time to do some updates for it this summer. I'm releasing a new Python script bundle for P4Pro and P5 in mid-April--PoseWorks PowerDials and Python Manager. PowerDials allows you to do some advanced work with parameter dials within Poser, letting you use mathematical functions (like trigonometry, logarithms, addition/subtraction, multiplication/division, and exponents) as well as variables and other parameter dials in the scene all instead of plain numbers. Python Manager is a new interface for loading and managing your Python scripts that should be quite a bit faster and more intuitive than the traditional Python Scripts Window. (If I do end up updating Particles this summer, I promise I'll throw in some extra goodies :-)