The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

xPLHal Manager v1.5 released



Hi all,

We are pleased to announce the release of xPLHal Manager version 1.5.

This is now available for download from:
http://www.xpl.myby.co.uk/downloads/xplhalmgr/xplhalmgr.zip

If you already have xPLHal Manager installed, just copy the updated
xplhalmgr.exe out of the Manager folder inside the zip file and
overwrite your existing copy of xplhalmgr.exe.

Release notes are below.

We hope to release version 1.5 of the xPLHal server within the next
couple of days - this will be built against the latest xPL .NET library
so should avoid any of the hub issues that current xPLHal users have
discussed on here in recent weeks.

Regards,

John

xPLHal Manager
=============================

Version 1.5
Release Date: 01 October 2005

New Features:
- Right-click on xPL Devices node and you can select Poll for Devices.
This issues a hbeat.request so all devices can respond. The Manager will
wait for 5 seconds to allow all devices to reply,
then refresh the device list for you.

Fixes:
- Send xPL Message dialog no longer prepends a space to the source
address.
- When adding the action to "Execute another Determinator" to an
existing determinator,
the dropdown list of determinators is now populated.
- When editing an event, the combo box for selecting the sub routine or
determinator
has been increased in size.
- Better support for accessibility software such as screen readers.

Known Issues:
- The "Use internal hub" option on the Properties page needs to
be
removed, as the upcoming v1.5 of the xPLHal server no longer supports
acting as an xPL hub.



xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.