Source language: Translate to:


Questions about using NeoBook's scripting language

Moderator: Neosoft Support

Postby Gaev » Fri May 11, 2012 7:51 pm


I was not saying that you were confusing the two ... my comment was directed at Alex ... who started out talking about "idle" but in followup posts changed to "pub being on top" ... which looks like he is looking at his pub losing/regaining focus.
User avatar
Posts: 3757
Joined: Fri Apr 01, 2005 7:48 am
Location: Toronto, Canada

Postby Alex » Sat May 12, 2012 1:26 am


Thank you for all your answer.

You are right Gaev, I was confusing Idle and Activate/Deactivate.

I put this:

setvar "[acti]" "1"

in the activate section and:

setvar "[acti]" "0"

in the desactivate section and all is working fine.


Posts: 745
Joined: Sat Mar 04, 2006 4:53 am

Postby Neosoft Support » Mon May 14, 2012 11:04 am

The concept of an app being "not idle" isn't really something that's used often. I think usually programmer's will just try to differentiate between being active or on-top as opposed to not active. An app is considered active when it has the input focus - meaning that any keyboard or mouse activity will be sent to the app and not somewhere else.

NeoBook's Idle action is intended to detect if the user has walked away from the computer, lost interest, etc. It's usually used to return to a specif page after a period of inactivity.

I think NeoBook's Activate/Deactivate actions are probably the best place to determine if a pub is "active" or has the input focus.
NeoSoft Support
Neosoft Support
NeoSoft Team
Posts: 5621
Joined: Thu Mar 31, 2005 10:48 pm
Location: Oregon, USA


Return to NeoBook Action Commands

Who is online

Users browsing this forum: No registered users and 2 guests