Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#213 Keep session non-idle

open
nobody
None
5
2014-07-03
2012-01-31
Callum Gibson
No

This patch allows a configurable idle-timeout to be specified (via a new command line option) after which the mouse pointer will be virtually wiggled by a pixel. This avoids the windows screensaver activating on servers where you can't disable it which can be annoying.

This initial patch applies against 1.7.0

Discussion

  • Callum Gibson
    Callum Gibson
    2012-01-31

    Confirmed that the patch applies against 1.7.1 also.

     
  • Mike Coleman
    Mike Coleman
    2012-12-08

    I would really like this patch in, if it works as described. I'm in need of it right now.

    (I feel stupid, but I cannot see any way to get this patch. No link or anything. Can someone tell me how to do this?)

     
  • Callum Gibson
    Callum Gibson
    2012-12-10

    On 08Dec12 16:29, Mike Coleman wrote:
    }I would really like this patch in, if it works as described. I'm in need of
    }it right now.
    }
    }(I feel stupid, but I cannot see any way to get this patch. No link or
    }(anything. Can someone tell me how to do this?)

    I've just checked and the attachment is gone. In addition, I don't seem to
    be able to reply to the ticket from the web page and I can't add the
    attachment. I'm attempting to reply via email and see if this works.

    The patch appears to have something wrong with it as I get the occasional
    crash with bad protocol errors. YMMV so see how you go.

    --

    Callum Gibson @ home
    http://members.optusnet.com.au/callumgibson/

     
    Last edit: Callum Gibson 2012-12-10
    Attachments
  • Richard Smits
    Richard Smits
    2014-07-03

    Patch seems to work, but after the idle time has passed I also get a : disconnect: Internal protocol error.
    To bad. This is an old thread, but this feature has potential. Is there a way to solve this error ? Tried against 1.7.0 and 1.7.1.