Hi Sheri, ... That s why I removed the delay command (on the other clips list thread: timer and closing apps) And then I noticed no interference on status barMessage 1 of 5 , Dec 15 4:50 PMView SourceHi Sheri,
>The few times I tried them I gotThat's why I removed the delay command (on the other clips list thread: timer and closing apps)
>distracting interference on the program's status line.
And then I noticed no interference on status bar (except when shot up reminder prompt) but if I just have it play a sound file instead of shoot up a prompt then most likely there wouldn't ever be anything or any interruption on status bar. (or maybe there would ^!Shell d:\mysoundfile.wav) or the ^!sound command if I used that instead.
>The help file says though that a timer clip won't be executed ifI didn't understand that part of help. I thought it meant if another clip is currently in progress that, under such condition as that, I can not launch the TimerStart
>another clip is progress when the time comes.
Do you mean that if I've already launched the TimerStart that if whenever the reminder/event is supposed to pop up--if I have a different clip running at the moment when pop up is to happen that the pop up will not happen?
>And the clipbook has toYes. Can be hidden though.
>PowerPro has nice timers which I've used to run scripts. I have onThat's what I's try/attempt to find out via this thread if TimerStart uses a totally separate block/chunk of memory (like as if it was its own separate .exe program--or--if it kinda intermixes/intermingles with other activities that I'm simultaneously doing with NoteTab.
>occasion used Notetab clips to activate its timers and to send data
Hi Alan, I experimented a bit more with the timer and with a simple clip I don t have a problem on the status line. However, my mouse pointer disappears inMessage 1 of 5 , Dec 16 6:15 AMView SourceHi Alan,
I experimented a bit more with the timer and with a simple clip I
don't have a problem on the status line. However, my mouse pointer
disappears in Notetab context menus when the time resets. Eg if I
open a context menu with a 1 second timer going, the mouse pointer
disappears quicker than if if its a 5 second timer. So, there's
obviously some degree of impact on normal Notetab operations.
I guess you only get one timer, because ^!TimerStop stops it. There
also seems to be no warning if you execute a new ^!TimerPlay without
meaning to quit the old one. The old one just quits without warning.
BTW PowerPro has 26 independent timers. It can do a lot of things
without scripts, but there are some limitations related to use of
(2nd or alternate ini & 2nd instance of NoteTab Pro in conjunction with NoteTab Timer use & background task management is the topic that follows) It didn tMessage 1 of 5 , Dec 16 6:23 PMView Source(2nd or alternate ini & 2nd instance of NoteTab Pro in conjunction with NoteTab Timer use & background task management is the topic that follows)
It didn't occur to me until just now. Or I would have shared about this as a possibility sooner.
But (I just tried it) use of an alternate ini and launched a 2nd instance of NoteTab Pro
Minimized, in Win 2k, the 2nd NTB only uses near 400 something to 800K of my 'puters memory. That's minimal.
I had timer going in each instance of NoteTab, bells and whistles going off all over the place. Each timer only impacted its own NoteTab, had no detectable effect whatsoever on the other NoteTab instance.
I think each NoteTab instance runs in its own memory space just like the different .exe programs on your 'puter whereby you can have more than one up and running at the same time.
Commandline launch a minimized NoteTab with certain clip also executed for the purpose to manage background task(s) of which Timer might fit within that category. I may write a clip does such for timer, etc. Could even have it launch a Perl script and retrieve over the internet my favorite nntp news group articles at certain time of day via timer.
One thing about NoteTab: There are lots of possibilities.
if anyone want to experiment, follows is a 2nd ini file name that I used, then a clip to launch 2nd NTB via that 2nd or alternate ini
the ini filename:
the clip (2 be launched from the normal NTB instance):
H="Load ntptimer_ini NTB"
; --end clip--