Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us
topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • December 04, 2016, 10:26:07 AM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: IDEA: adaptation of tasklog to "pause" after certain amount of idle time  (Read 3434 times)

tasker

  • Participant
  • Joined in 2007
  • *
  • default avatar
  • Posts: 2
    • View Profile
    • Donate to Member
This one is for skrommel I guess..

Since 2 days I am using the (almost) perfect http://www.donationc.../TaskLog/TaskLog.ahk

But I have 2 little remarks/ideas:

- How can I add a "Pause"-option, where timers are stopped? For example, I am working on task XYZ, and leave for 30 minutes, how can I halt the timer without adding a "Pause"-task?
- It would be great if somewhere an idle time could be checked. If I am hibernating or just ran away, it should stop counting after xxxx minutes, or at least have the option.

Needless to say, I am not a programmer

I am very confident that master skrommel has some good thoughts about it :-)

Thanks for the good work!

tasker

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 36,406
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
very good ideas  :up:

tasker

  • Participant
  • Joined in 2007
  • *
  • default avatar
  • Posts: 2
    • View Profile
    • Donate to Member
Eh, I tried to fiddle with OnMessage(0x218, "WM_POWERBROADCAST") to see wether a system is idle due to hibernation or standby mode.

MSDN says: WM_POWERBROADCAST messages do not distinguish between sleeping states and hibernation. An application can determine only that the system has entered a sleeping state; it cannot determine the specific power state that the system entered when the transition occurred.

Its a pity that A_TimeIdlePhysical does not detect these modes: it keeps on counting even when standby or hibernated..

When using function WM_POWERBROADCAST(wparam,lparam) the wparam and lparam give the following values:

Suspend cycle :

Powerbroadcast 10 - 0
Powerbroadcast 10 - 0
Powerbroadcast 0 - 1
Powerbroadcast 0 - 1
Powerbroadcast 4 - 0
Powerbroadcast 4 - 0
Powerbroadcast 18 - 0
Powerbroadcast 18 - 0
Powerbroadcast 7 - 0
Powerbroadcast 7 - 0
Powerbroadcast 10 - 0
Powerbroadcast 10 - 0

Hibernation cycle:
Powerbroadcast 0 - 1
Powerbroadcast 0 - 1
Powerbroadcast 10 - 0
Powerbroadcast 10 - 0
Powerbroadcast 4 - 0
Powerbroadcast 4 - 0
Powerbroadcast 7 - 0
Powerbroadcast 7 - 0
Powerbroadcast 18 - 0
Powerbroadcast 18 - 0
Powerbroadcast 10 - 0
Powerbroadcast 10 - 0

So there is a difference to see..

« Last Edit: June 21, 2007, 08:25:02 AM by tasker »