[EMAIL PROTECTED] wrote:
> I saw your post on the net. We are having a similar problem. Did you
> ever find out how to detect system lock?
I can't seem to see the original post you're referring to
(reading this via the mailing list) but assuming that by
"locked" you mean: Ctrl-Alt-Del locked, th
Further to my last post, I will try some of the tips presented above.
Also the app writes to the screen display (or Active Desktop). As
someone suggested, that could be where the problem is.
Best.
rod
--
http://mail.python.org/mailman/listinfo/python-list
Yes, I mean just a good old fashioned screen lock (for security)
initiated by the user. 'Sadly' there has been nothing as exciting as a
blue-screen of death as yet, not even when the app swells to 400MB.
Best,
rod
--
http://mail.python.org/mailman/listinfo/python-list
[EMAIL PROTECTED] wrote:
>
> rod> I have written an application which works perfectly when the
> rod> machine is operating under normal conditions, however when the
> rod> screen becomes locked it imediately starts to fill up several
> rod> hundred MB's of memory.
>
> What do you
rod> I have written an application which works perfectly when the
rod> machine is operating under normal conditions, however when the
rod> screen becomes locked it imediately starts to fill up several
rod> hundred MB's of memory.
What do you mean by "locked"? Unresponsive to mous
[rodmc]
| I have written an application which works perfectly when the
| machine is
| operating under normal conditions, however when the screen becomes
| locked it imediately starts to fill up several hundred MB's of memory.
|
| Is there a way to detect when the system is locked?
This may not
