Re: Re: xPLExec

[Mal Lansell <mal@xxxxxxxxxxx>]

Inline...

Tom Van den Panhuyzen wrote:

> Mal,
> Some minor issues - I am writing them down because I noticed them, not
to
> be picky, ok ? ;-)
> - default name = "DEFAULT" (shouldn't that be
"instance1" ?)

I think "default" is correct.

> - no initial value for interval
> - I had to edit these values twice before xplExec would appear in the
> xplDevices list - it stayed in the Awaiting Config state (yes, I
> refreshed -
> maybe an xplHal issue ?)

Interval defaults to 5 - I don't know why it wouldn't show up.  I don't
have anything except the device name in the vendor xml file - I wonder
if that could have anything to do with it?

> - The configuration application allows a user to pick ".bat"
files, but
> these files do not appear in the filelist. I was able to enter the
name
> directly though and it accepted it.

OK - I'll look into that.

> - My original batch is a ".cmd" but your configuration
application only
> accepts ".bat". Maybe not an issue as I really do not know
the difference
> between a "bat" and a "cmd".

I've never heard of a .cmd as an executable file and I've been
programming PCs for 15 years - should I be embarrassed or is a .cmd a
bit obscure?  Either way, I can easily add it to the list.

> - An error in the path variable of the xpl msg results in an
"access
> denied"
> msg... it got me confused :-) took me some time to notice the error
was in
> the path and not in the configuration or somewhere else.
> In fact: why the path ? The configuration application already knows
the
> path to the executable.

True.  That would make things simpler.  The only issue would be that you
wouldn't be able to run anything with the same name but on a different
path, but that's probably a very minor thing compared to not having to
put the path in the message.

I should expand the documentation to list when these errors can occur.

> And now the good news: it works! :-)
> Cheers
> Tom
>
>
Hooray!! :-)

Regards

Mal