chadrik wrote: > we got eclipse/pydev remote debugging working with maya, but after > using it we end up with the partially dead maya window that always > seems to crop up when diverting the main thread in maya. here's a > description written by my co-worker: > > "When the process has terminated, the main window loses its > interactivity; you can create a sphere through the script editor, > select it with your mouse and manipulate it with editor commands, but > the main window is dead from the neck down - no hotkeys, > no spacebar-menu call, etc. We see this same behavior when we launch > PyQt4 or wx UIs. With pyQt we've loaded the pumpthread.py file, but > are still seeing the same behavior once the process has completed. > After the main qt UI has successfully completed, the qt ui closes and > Maya is in the same limbo as described in the above paragraph. We have > some secondary functionality, but the main window is unreachable by > the user." > > this same threading problem is killing many great possibilities. pyQt > windows, iPython console, and remote debugging, are all crippled by > it. it seems worse on osx than other platforms. does anyone have any > more insight into this? > > > on a different note, how is the svn integration in Wing? i'm growing > pretty frustrated with svn integration in eclipse, but i'm not sure if > the problems are due to svn itself or the subversive/subclipse plugins. > > > -chad > I second that, exact same problem, Maya also usually crashing at some point after the debugger server has been closed, after behaving strangely for the time it manages to remain up.
-- Olivier Renouard --~--~---------~--~----~------------~-------~--~----~ Yours, Maya-Python Club Team. -~----------~----~----~----~------~----~------~--~---
