Quote:
Originally Posted by sorrow
Find py2exeWalkthroughPython27.txt in the packaging directory. Thats the best one for getting a machine setup for deployment.
Sorrow
This will be of interest to developers only, or someone with Windows, 2 monitors and the left hand one mapped as not the main display.
Thanks, found it yesterday. The link on the web page in my earlier post is dead.
After some debugging, I'm pretty much convinced my multi-monitor problem is due to a gtk bug (if you know where to report those, let me know).
As stated earlier, my left hand monitor has negative x-coordinates (0,0 is the top left of my right hand monitor). If I use gtk's get_position() on a window that's on my left hand monitor, it reports the same as the the window api call, or ahk spy, i.e. a correct negative x-coordinate. However, if I use gtk move() (as used in fpdb) to move(0,0), the window moves to the top left of my left hand monitor, not right hand monitor as it should be.
Once I figured this out I spent a while searching for a generic solution... but it seems I'm stuck. I (think I) know how to hack the source code to make the fix for my own specific situation, so I'll probably just go that route.
The -32000 thing I reported earlier is still a bug and should be fixed; once I changed that, saving doesn't totally mess up the coordinates any more, there's only the constant offset.