AHP V3.200 Bug #5: Macro parser not executing as programmed

[Eric Edberg]

AHP V3.200 BUG #5
---------------------

When parsing a macro, AHP will parse all
house codes that are similar e.g.: all A's,
E's etc, and then send a unit attention for
each module (don't know the correct
technical term) and then a single on/off
command that controls all unit identified.
I verified that all lights on the same
house code in a macro all turn off
simultaneously.  This is a major problem.
I programmed the macro expecting a specific
sequence of events.  The AHP program parsed
the macro sequence and executed it in the
order the parser decided on.  How dare
you :-).   If I program a macro sequence I
expect it to operate in the order I program
it; not the way your program parses the
macro and executes it w/o exception.

How do I force ahp to execute a macro and
the step I include in it to execute exactly
as I program it in the order it's
programmed?


I assume that this will be a bug fix in
some future release.

I also theorize that a 0-second DELAY in
between each event might work-around this
bug.

Eric Edberg

[X10 Pro]

This is by design. Our macro compiler puts
groups of commands together if they're on the
same house code and execute at the same time.
This means events happen more quickly ("A1,
A2, A3, A On" takes quite a bit fewer
commands than "A1, A On, A2, A On, A3, A
On"), and that there is less traffic on the
powerline. You can force the behavior you
want by putting delays between the commands.
As I understand it, our current method is
desirable to most users, however we may be
able to put a preference option in for the
sequence that you describe.

[Eric Edberg]

I verified that a delay of zero seconds
will force the parser to in-line mode and
commands will execute as ordered in the
macro.

This does not change a users expectation
that macros operate in the order they are
specified in the macro file.

While you may not have had many users
complain (like me who is a software
developer & system tester by trade), this
does not make it a non-issue.

Clear documentation or an option in the
macro designer or global options to force
in-line parsing would be a cool addition.
Putting this in your FAQ would also be wise.

G'day for now...

Eric Edberg

[bronco]

For programmers, the method of gathering all
like housecodes is WRONG,WRONG!!!!
and not to tell us is a SIN!!!
I don't want a computer to decide what it is
that I want it to do.  Please fix it!!!!!