Internet access to Comfort

[juwi_uk]

Sorry all,

I have to confess to 1.0.12.0 being quite a ropey old build.  :? I\'m a bit under the weather this week with the bug that\'s going around the UK at the moment (sorry if I gave to anyone at the Heathrow Training session yesterday!!) and let this build slip through my usually rigorous QA  as there was something i wanted in there in time for the training session.

Please consign that version to the recycle bin and download 1.0.13.0 from:

<link removed by JUWI_UK>

Regards

Julian

Bug Fixes

• Improved stability/consistency (debug) Floorplan Editor NEW, OPEN, SAVE. SAVEAS menu actions.
  
• Floorplan XML file load would fail if image referenced in the XML file was missing from the Images folder (either via corruption or manual/explicit delete outside of the application).
  
• Further cleanup of design objects when exiting the Floorplan editor.
  
• Sending a logon request with blank password incorrectly enabled the mode (alarm button) icons on the keypad.  Still secure as without logon they wouldn’t have sent commands to Comfort, but wrong functionality nonetheless.

New Features

• User Settings are now preserved between versions (much needed!).
  
• Prompt user on whether to make edited Floorplan the ACTIVE Floorplan on Exit from Editor.
  
• Once logged on the previous user code value is cleared.  Security enhancement so that users cannot leave their workstation logged out of the UCM but with the ability for someone to use the log on button again with the existing password.

Known Errors

• Exception when reading Event Log (at the end of the fetch).  You can opt to continue and the application will be OK.  Occurs if the UCM is slow to send back event log items and the application starts to process what it thinks to be the fully received log.  The background process sends out all of the outbound requests and expects timely responses.  Most of the time this is OK but not always!   I’ve added a short wait at the end of the fetch to help this as a workaround but I’ll probably need to improve this if it’s a recurring issue for some.

An additional note on using the keypad to log on/off etc:
[font=\"Times New Roman\"]

[size=2]Assuming you are already connected but not logged in (this should be the default state at application start up):

a.     Type your user 4 digit code on the keypad
b.     Press “ENT” on the keypad to log on
c.     If you make a mistake in entering your 4 digit code before completing (b) then    pressing  “END” will clear the user code field (so you can start again).
d.     Once logged in, pressing “END” will log you out.
e.     Pressing “END” again when logged out will disconnect the TCP session
f.      Pressing “ENT” again will reconnect the session
g.     Repeating steps (a) to (b) will log you in again.

Hopefully you will see that most connect/log on/log off/disconnect actions can be done purely via the keypad and you do not need to have the Connection Tab in focus for this to work.  I’m looking at this as the precursor to removing this tab and putting the IP addressing info on a form on the Configuration menu as you shouldn’t need to access that often once set up.[/size][/font]