Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=733539

Has anyone on a Mac tried the Python TK fix that is discussed in a message thread here on Renderosity (see attached link)? Is this supposed to only work with the author's Environment Creators script or is it supposed to be a overall fix for Python in Poser? I'm also having a very difficult time figuring out the installation procedure. The download has two folders with "placeholder" documents in them. Are these supposed to replace the folders with the same names in Runtime/Python/Lib? Can't be right. That would destroy everything that's currently in those folders with two basically empty folders. But that's how the Readme reads ... "Copy them from there, exactly as is show here." And what is meant by the folder heirarchy that is suggested ... Systeemmap/Extensies/Tool Command Language/tcl8.3 SystEEmmap? Extensies? What's that all about??? Hope someone can shed some light on this "fix." It sounds like it could be wonderful if it's true but it's impossible for me to figure out the install procedure! Extremely confusing! TIA for any help with this. :-)

It works and it is straightforward but for ---Macs only---. When you install TK from scratch on a Mac it will place a folder named "Tool Command Language" in the System extensions folder of your Mac. The TK stuff will simply reside there, and TK is searching for this folder. What the fix suggests is that you replace the placeholders with copies from your original Poser Python libraries folder. Quite simple - I used to have aliases in the Tool command Language folder, this also worked. By the way the author is Dutch and so is the language of his System. By the way I had emailed CL twice on the binding problem with no answer until I found a hint in a Python news group. CL should decouple Python from Poser and rely on a normal Python installation, that would make things much easier and would also allow to switch to newer Python and TK versions more easily. Karl

Attached Link: http://www.pcbos.nl

Oddly enough, after a couple of hours of playing around with it I'm able to answer my own question about this Python fix. I'll post the results here in hopes of helping other Mac users.

First of all, IT REALLY WORKS!!! And it's an overall fix for Python in Poser not just for the author's Environment Creator script.

I'm not a Python expert by any means so forgive me if what I'm about to say could be said better by those who know much more than me ...

The apparent problem with Python on the Mac is that the second time you try to run a script you most likely will get a "TCL Missing" error and the script won't run. If you've created a button for the script in the Python button window then the only solution is to again create a button before running the script successfully. Very buggy and anti-productive.

After trying different ways of installing the fix, some of which gave me some exasperating errors, I believe I finally figured out how this is supposed to be installed. The first problem I had is that the author is apparently using a Mac set up for the Netherlands. "Systeemmap" apparently means "System Folder" and "Extensis" apparently means "Extensions."

Here's how I successfully installed the fix ...

1. Drag the folder called "Tool Command Language" directly into your OS 9 Extensions folder (inside your Mac OS 9.x System Folder).

2. In the folder where Poser is installed, navigate down to your Runtime/Python/Lib folder.

3. Inside the Lib folder are two folders called "tcl8.3" and "tk8.3." Copy (don't just move them) both folders into your "Tool Command Language" folder inside your Extensions folder (in your Mac OS 9.x System Folder).

4. Navigate to your Runtime/Python folder. Drag the folder named "Lights" directly into your Python folder.

5. Reboot (I don't know if it's necessary but one usually reboots after adding things to the Extensions folder.

6. Restart Poser.

7. Either from your Python button window or from the "Run Python Script..." menu item, run the author's script called "InstallCreatorsDeLuxe.py" and test to see if those nasty "TCL Missing" errors have gone away. You might have to restart Poser before testing but I'm not sure about that.

THE DISCLAIMER
The procedure above, of course, should be done with some caution and I can't guarantee your success or anticipate any problems you might have. Please contact the author, pcbos (Paul Christiaan) if you have any questions. A link to his Web site is attached for your convenience. The Python fix is linked at the very bottom of his page on the right.

I was thoroughly confused about exactly what this fix was and how to install it. So far I'm delighted that Paul has figured out a fix that seems to work flawlessly thus far. Kudos!!!

There are probably others who are just as confused as I was. Hope this helps.

:-)

Thanks, Grammer. Guess we were writing our responses at the very same time. :-)

There is an easier way to apply that fix. Install the Shockwave 3D exporter, I made its installer do the fix for you.

Attached Link: http://www.pcbos.nl

Gentlemen! Dkal explained things great; I'm sorry I was'n't clearer myself. I'm working on implementing an even better fix straight into all the programs I'm writing for the Mac. Right now, I'm incredibly hard at work finishing the PCB ZOOM Tool for the Mac. To write good stuff for the Mac, you have to write most of the system routines yourself. The fix I supplied was meant for other's work: what I'm doing for the Mac will have no need of the fix- but it doesn't hurt either. You can savely apply the fix- things will just be better. P.S. I'm now testing my ZOOM Tool on a very bad, early IMac, the one with the massive problems- and it runs like fire, even though I have to make maasive use of virtual memory (testing 75 Mb pz3's on a 160 Mb Mac...). In other words: the fix helps, and is save. Shortly, I'll release a "Python fixer" via the Pro Pack freebies, here at Renderosity: a sort of medicine to quickly fix python problems that would otherwise hang your computer. This should really do away with any Pyhton problem out there, I should think. By the way: do you know that, as things now stand, Python works much more pleasantly on the Mac than on the PC? On the PC, I have to write whole novella's of code to keep things in order, while on the Mac I only have to write some Quickdraw routines... Great computer, the Mac. Cheers, Paul Christiaan. more info at my site, just follow the Poser link