Zugg Software :: View topic

Wanderer Joined: 07 Oct 2001 Posts: 71

I noticed that none of the #ALARM triggers in my main .pkg file were firing. It was creating the alarms, with the correct time and trigger ID, but they were just sitting there.

As a test, I made an alias for the session window in the settings editor

Name: test2
Value: #ALARM testAlarm2 {+1} {#ECHO Test alarm 2 fired.}

and another basic alias in the seperate package that is enabled for the session window.

Name: test1
Value: #ALARM testAlarm1 {+1} {#ECHO Test alarm 1 fired}

From the command line, entering "test2" in one second I get the echoed msg on the screen. Entering "test1" yields nothing; however returning to the settings editor, in the seperate enabled package there is and Alarm created with the ID "testAlarm1" and the time pattern of +1, with the propper value.... but it just sits there in the package.

Posted: Thu Oct 12, 2006 12:08 am

Currently, executing/defining an alarm from within an alias doesn't seem to work. This is on the bug list for one of the next versions.

Wanderer Joined: 07 Oct 2001 Posts: 71

I did not have any problems with an alarm created from within an alias - the alias I used that was part of the session window settings functioned perfectly, as did the alarm that was created. The alias that was in the seperate package created the alarm perfectly to, however that alarm did not function.

I tested a bit more and:

- I don't have any trouble with alias created Alarms as long as the alias is in the session window settings; I used multiple aliases with differing alarms.
- Aliases in seperate packages create alarms every time, with the propper id, pattern, and value; however, these alarms are non functional.
- I created Alarm triggers manually in the settings editor, and again Alarms made in the session window settings function perfectly; alarms created in seperate packages are non functional.

From what I've experienced so far, the bug seems to lie in Alarm triggers contained in seperate packages - no matter how they are created. They're just not processing at all.

Posted: Thu Oct 12, 2006 4:02 am

OK, thanks for the additional information...that should be helpful in finding the problem.

Wanderer Joined: 07 Oct 2001 Posts: 71

Oh, one more thing I forgot to mention, that I tried:

If you create a new package, and put an alias in the seperate package that creates an alarm trigger - then drag the seperate package into the Session window settings, making it a child package - the alias and alarm will both function.

It's definitely just when I have the package seperate, published, and enabled as a package for the window.

Posted: Thu Oct 12, 2006 9:41 pm

Verified this problem and I have it fixed in 1.10.