search

sonzzdq / python-windows-tiler

Automatically exported from code.google.com/p/python-windows-tiler
GNU Lesser General Public License v3.0
0 stars 0 forks source link

cx_Freeze: Python error in main script #13

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Leave computer alone for some time, or
2. Computer has 'a lot to do' (CPU load, file system access)
3.

What is the expected output? What do you see instead?
The following error message box appears: 

---------------------------
cx_Freeze: Python error in main script
---------------------------
Traceback (most recent call last):
  File "c:\Python32_32\lib\site-packages\cx_Freeze\initscripts\Console3.py", line 27, in <module>
  File "pwt.py", line 27, in <module>
  File "E:\Python\PWT\src\pwt\controller.py", line 109, in start
  File "E:\Python\PWT\src\pwt\controller.py", line 291, in cmd_switch_to_group_5
  File "E:\Python\PWT\src\pwt\controller.py", line 188, in switch_group
  File "E:\Python\PWT\src\pwt\notifyicon.py", line 82, in draw_icon
pywintypes.error: (1460, 'Shell_NotifyIcon', 'This operation returned because 
the timeout period expired.')

---------------------------
OK   
---------------------------

After acknowledging the message box, the PWT process stops.

What version of the product are you using? On what operating system?
Latest version on Win XP.

Original issue reported on code.google.com by 7enderh...@gmail.com on 6 Nov 2012 at 7:51

GoogleCodeExporter commented 8 years ago 
Hey, sorry for the late response.

This is happening apparently because I did not catch the exceptions in 
draw_icon. 

It should easily be solved by catching it and simply ignoring it or retrying 
it. Apparently the win32 errors out when a call has to wait for a while due to 
high cpu-stress.

Sadly I am (definitely for now) discontinuing my work on this project. I am 
working on a successor project which will tile windows cross-platform 
(linux/windows). It is a rather large project so it is going to take a while, 
but when it is finished I will be able to easily provide longterm support as 
I'll be a frequent user of the program as well.

Original comment by tzb...@gmail.com on 13 Nov 2012 at 8:23

GoogleCodeExporter commented 8 years ago 
No problem. I have actually managed to set up a Python debugging environment 
and have fixed this by catching the exception. I will most probably send you a 
push request (or whatever it is called in Mercurial) for my changes in the near 
future.

Original comment by 7enderh...@gmail.com on 14 Nov 2012 at 8:23

GoogleCodeExporter commented 8 years ago 
Hey!

First off, thanks a lot for helping out. I started this project as a mere 
learning experiment which is why it's using mercurial as well.

I (and I'm sure a lot of other people) am more comfortable with git. If you 
don't mind could you send push requests to 
https://github.com/Tzbob/python-windows-tiler ?

I will post on the frontpage that github is now the main repo.

Original comment by tzb...@gmail.com on 14 Nov 2012 at 9:53

GoogleCodeExporter commented 8 years ago 
Ok, I'm now working based on the Git repository. You will get my first push 
request in a few days.

Original comment by 7enderh...@gmail.com on 15 Nov 2012 at 4:59