Smart Macro Install

Started by steven r, November 16, 2004, 03:37:04 AM

Previous topic - Next topic

steven r

My Smart Macro install went well.

While the chained macros approach was not
what I expected, I think I figured out how
to use them. I had hoped to be able to just
add a condition to my existing shutdown
macro to turn the front light back on at
night. It looks like I have to copy the
steps to my "chained else" macro.

How about an update to the help file with
examples?

The programing option of using the wizard
or not is a nice touch.

I have yet to test what happens when the
conditions for the "else macro" overlap
with the main marco. Will we have a case of
dueling macros?
BVC let's me tell my camera where to go!
:) Murphy is my beta testing pal. He helps me find problems whether I like it or not. :)

X10 Pro

No dueling macros -- the first condition
that's true will be the one that runs. We'll
be updating the help and providing more
examples. That's definitely needed.

steven r

"...the first condition that's true will be
the one that runs."

Let's see if I understand it correctly.

e.g.
A Primary Macro conditionally executes
between 1:00 pm and 7:00 pm.

The ELSE conditionally executes between
Dusk and 12:00 am.

If it's 6:59 pm the Primary Macro is going
to execute regardless of weather the sun
has set. If it's 7:01, however, the else
comes into play and would only run if the
sun had set.

Between midnight and 1:00 pm nothing
happens.

Have I got the idea correct?
BVC let's me tell my camera where to go!
:) Murphy is my beta testing pal. He helps me find problems whether I like it or not. :)

X10 Pro


steven r

"Exactly right."

I guess that means my conditionals aren't
working, then. :(

I made one this morning the triggered the
else during the time of the primary macro.

BTW.. AHP displaying the time between
midnight and 1:00am as "00:mm am" is a bit
confusing. It would be more correct to use
24 hr time as "00:mm" or 12 hr time
as "12:mm am". Combining the 2 is confusing.
BVC let's me tell my camera where to go!
:) Murphy is my beta testing pal. He helps me find problems whether I like it or not. :)

steven r

Correction: I forgot to include seconds in
my example.

AHP displaying the time between midnight
and 1:00am as "00:mm:ss am" is a bit
confusing. It would be more correct to use
24 hr time as "00:mm:ss" or 12 hr time
as "12:mm:ss am". Using "00" as an hour for
12 hr time could be confusing.
BVC let's me tell my camera where to go!
:) Murphy is my beta testing pal. He helps me find problems whether I like it or not. :)

steven r

This "0:mm:ss am" format exists in both the
clock at the bottom right of the page as
well as in the activity monitored times.
Maybe I'm just picky but I'd rather have it
in 12hr or 24hr time not the "zero hundred
hours am" it is now.
BVC let's me tell my camera where to go!
:) Murphy is my beta testing pal. He helps me find problems whether I like it or not. :)

X10 Pro

Steven R: The extra leading zero during the
AM while using 12-hour time should be gone as
of 3.169. When I look here that's the case,
but if it's not for you let me know.

steven r

"The extra leading zero during the AM while
using 12-hour time should be gone as of
3.169."

I wasn't referring to the leading "0" which
is indeed gone. I was referring to the fact
that the correct way to represent 12 hr
times between midnight and 1:00 am is in
the format "12:mm am" not "0:mm am"
BVC let's me tell my camera where to go!
:) Murphy is my beta testing pal. He helps me find problems whether I like it or not. :)

X10 Pro

Oh, OK. We'll fix this in the next update.