Re: X10

[Stuart Booth]

Edward, some incredibly minor change requests!

1. When it's attempting to connect to a CM1xU device, it sits for a
short while determining if it can or cannot ie is a CM1xU present on
the specified COM port. Would it be possible to bung up an hourglass
cursor whilst this operation is proceeding. I wasn't sure it was doing
anything when I first saw this.

2. What would you like to call it?

The DLL is named "X10-CM1xConnector.DLL" so I've named the
standalone
EXE package the same, ie "X10-CM1xConnector.EXE".

However, when it starts up the runtime shell takes its caption title
from the attributes on the plugin module and eventually names itself
"X10 Connector".

I quite like the idea of calling it "xAP X10 Connector" myself.
This
is the scheme with which I named the SlimServer Connector, which
displays "xAP SlimServer Connector" in its title bar.

I know that's incredibly minor but it's one of those detail things
that yells out at me, waving its arms in the air! :-))

--

Otherwise I've added a table entry into my packaging tool for this
now. It'll appear on the web site shortly.

S
--
Stuart Booth <<a
href="/group/xap_automation/post?postID=9Y5Pv20FyeBan6jNtdD1OjdiPoNg8Anqdve6DoX91l57OG6iD4NNhEUsaMC0HJl61yKF2Ci0BuvdATJDeEg">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net

<a href="http://www.xapautomation.org/";>http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>