Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 11 12:18 am)
Poser 7 and Poser Pro both use Python version 2.4. In previous versions the Python Tkinter keyword "col" was allowed as a short form of "column". In the new version only "column" is accepted.
Open your PY file in a text editor and serch for "col" replace with "column". Save and retry.
Python 2.4 was used by Poser 7 from the get-go, SR3 has not suddenly updated it.
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
I know that SR3 has been out for sometime, but I was reluctant to update due to the already myriad of previously reported problems.
That being said, after purchasing some pose sets, I was getting version warnings with those same pose sets. So, after speaking with one of the pose set vendors, I then went ahead and and got the SR3 update for Poser 7..
Everything was fine until it came to running a Python script. EVERY time I tried to use a script either by way of the python script window/list pane or running a script from the "File" menu, I get this error:
Traceback (most recent call last):
File "C:Program Filese frontierPoser 7RuntimePythonposerScriptsWacrosOcclusionMast er.py", line 338, in ?
MatDlg = MaterialsDlg(tk)
File "C:Program Filese frontierPoser 7RuntimePythonposerScriptsWacrosOcclusionMast er.py", line 70, in init
Label(self.HelpFrame, text='HELP', font=f).grid(row=0, col=0,sticky="w")
File "C:Program Filese frontierPoser 7RuntimePythonliblib-tkTkinter.py", line 1790, in grid_configure
self.tk.call(
_tkinter.TclError: ambiguous option "-col": must be -column, -columnspan, -in, -ipadx, -ipady, -padx, -pady, -row, -rowspan, or -sticky
This occurs regardless of the script location or the script being used. Anyone have a concrete solution to fixing this AND keeping the SR3 update?