i had some success with this problem when i didn't DRAG the Gem-window to the second monitor but instead set the creation arguments of the Gem-window to the second monitor before creating it. the problem seems to occur when even a small part of the Gem-window is outside the second monitors coordinates.
on my laptop, the display is set to 1400x1050 and the second monitor to 800x600, so:
[offset 1401 1, dimen 798 598( | [gemwin 25]
did the trick (i did this 1-pixel offset for stability reasons and had a black desktop to avoid a "wallpaper-frame")
hope this helps
oliver
Gerardo Morel wrote:
hello everyone! I got a problem and would really apreciate any help to solve it... I´m running pd on winXP (sucks, I know) on a Toshiba Satellite a16-sp100 (celeron 2.4 Ghz-256 ram) with an Intel 82852/82855 gm/gme graphics controller that I use for an external monitor. The problem is that when I drag a gem window to the external monitor the CPU meter goes from, say, 7 to 70, when lucky... that doesn´t happen if i drag a Windows Media window for example, what makes me think that Gem makes the graph controller achieve some ram space to work somehow freely... and the fact that this only happens with pd and gem makes me wish there´s a solution from pd itself... so I ask for help to the community... thanks in advance cheers Gerardo Morel (aka Grod)
Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list