Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ComfortClient
#11
I couldn\'t simulate either of the two exceptions mentioned. We\'ll have to wait for Julian to have a look tomorrow, he is enjoying a well deserved \'Father\'s Day\'

In the meantime, let us know what OS you are running and also append the external log file entries on any defect, it will greatly help to debug issues. The exact steps to simulate will also help.

Ingo.
Reply
#12
Hi Everyone,

I\'ve been looking at all of your problems.

I\'ve now posted build 65.
Quote:[size=2]Version 1.21.1.65 – (20 June 2010)

Bug Fixes/Changes

·         Fixed bug in FastStart mode where it would try to refresh all objects even though the user wasn’t logged in yet.  Also refactored the code to improve stability and user experience.

·         The Blank.xml file was set to read-only in the distribute zip which caused write errors on save.

·         Save to GaugePack would fail if the FONTS directory was empty.

·         Some Gauge attributes had an entry range of 0 – 500 which could limit the building of certain Gauge designs.

·         The “Max Drift” default for date/time synchronisation on newly created Configurations (i.e. via FastStart) should be 5 (minutes).

·         Connection AutoStart is now defaulted to Disabled for FastStart created configurations.

·         Keypad digits 0 – 9 are now greyed out before a connection is established.  This prevents users from thinking they can sign on before connected.

·         In Floorplan Editor, newly added Pictureboxes, Labels and Gauges were not added to Floorplan on OK if no other of the object’s properties were changed.

·         Fixed issue in building fonts when the Private Font collection was empty.
[/size]


The Build can be downloaded from:

*** Link Removed,  see download link at http://www.comfortforums.com/forum65/1948.html instead***

For those who have already downloaded Build 64 you can just download a replacement ComfortClient.exe to get you to build 65:

*** Link Removed,  see download link at http://www.comfortforums.com/forum65/1948.html instead***

Thanks for bearing with me.

Julian

 


 


Reply
#13
Ingo,

Thanks for you advice.

Hi Julian,

Thank you for your super fast respond & release on new exe.

FYI, i am using Win7 Ultimate, Comfort V5.164 & UCM05 V5.202 (Update to latest firmware soon)

After i send you the feedback on the error. i did tried again a few time to load on the JPG file. It seem to be work with no more unhandled exception. i mean on the Version 1.21.1.64, but after can load just problem on unable to save on the Blank.xml.FPE. i think that already resolve on your new release V1.21.1.65. i will tried out tonight.

A question to you, is that a way for me to offline (without sign on & connect to UCM) so that on the Configuration/Floorplan & etc tool still can be access? becos sometime perhap i am not at home or unable to remote access my system. But i still want to offline doing edit floorplan so on & so for. So I am not sure this is the right thing to have.

Tae

 
Reply
#14
Tae,

See the \'Persist Configuration Menus\' option under Configuration->Settings->Options, set that to enabled and the menu will be available offline.

Regards,
Ingo
Reply
#15
Tae,

As Ingo says go to Configuration MenuSettingsOptions and set the \"Persist Configuration Menu\" option to TRUE.   Note you\'ll need to be logged on to be able to configure this the first time,  after that you wont need to be logged in as the Configuration Menu will then be available (persisted)!.

Also if you dont want it to try to connect to the UCM on startup then set the \"AutoConnect\" setting in the Options menu to disable that too.  It\'ll mean startup will a be a few seconds quicker, which is good when you are configuring floorplans etc and dont actually need to be connected to Comfort. You can still press the \"Connect\" button anyway to connect once you are in the UI.

Regarding the Blank.fpe issue you reported that is true, in the files I zipped up in the initial Build 64 release I included a \"blank.xml\" file who\'s windows file permission was incorrectly set to read-only. If you make this file writable then all will work OK (even in Build 64 of the EXE).    The way a \"save\" works in the editor is that it firstly takes a copy of the original floorplan (blank.xml in this case) and creates a FPE version.  It then tries to write the new configuration to the Blank.xml file.  If that works then fine (and it deletes the FPE copy).  If it doesnt work though (ie in this case the file is read only) then it tries to copy the FPE (saved version) back so that effectively the changes are rolled back.   I did this to protect against failures during writes/saves.  In this case though it cant copy back the file because the old one can\'t be deleted (as it\'s read-only).  So a \"Catch-22\" situation I hadn\'t considered to now as floorplans shouldnt be read-only annyway.  I\'ll see how I can make this a bit better over the next releases to cope with this scenario; it should capture this and prompt you to save to another filename instead.  Of course you could have done a \"Save-As\" in the editor as well to get around this.

Regards

Julian

 

 
Reply
#16
Hi Julian & Ingo,

Thanks for the step & explaination.

At this moment it\'s working & further question will send you later on.

-----------------------------------------------------------------------------------------

Did anybody in the forum having a nice icon in gif file (in normal condition & trigger condition icon) for attached in the floor plan such as motion sensor, fan, cctv, corner cctv & etc?

Tae

 
Reply
#17
Good news is that a Maintenance release of ComfortClient will be released next week. It fixes some minor issues and adds a few small enhancements. One of those enhancements is the System Information screen. From the attached you can see that it displays all your system information in either Green or Red. Some information is displayed in both colours.

What the Green means is the module has been automatically detected and the information is then extracted from the module itself. If however you have a module that does not yet respond to the information query then the information is read from your cclx file and this time it populates the fields with a red colour.

Now you ask me, what about the Green and Red together... Well, this is when a module is new enough to respond to the query but it doesn\'t respond with the necessary information, again the information is then added from the cclx file and displayed.

In the attached you will see my KP04\'s have a 1.03 release version. This is something that I manually added to my cclx file. The current KP\'s don\'t respond to queries but I wanted to see the firmware anyway - nice but editing the cclx file is not recommended, you might end up destroying your file by doing this.

Until next week,
Ingo



Attached Files Thumbnail(s)
   
Reply
#18
Hi everyone,

I\'m pleased to post version 1.21.1.85 of the ComfortClient. 

This version is mainly a bug fix release but it also adds further support for the first release of the Modbus plugin that is also being released today on another thread.  If you are going to use this Plug then also use this ComfortClient build.

Changes in this release are:


Quote:Version 1.21.1.85 – (16 July 2010)

Architecture:

Microsoft .NET 3.5 console application developed under Visual Studio 2008

Tested against Comfort version:
  • Comfort II Ultra: Firmware – 5.199, File System – 34
  • UCM05: Firmware – 5.212
Bug Fixes/Changes
  • Negative values can now be selected for Gauge Range start and end values.
  • ComfortClient current window size was incorrectly saved to the configuration file at close when the closing from a minimised state.
  • Home Control menu would error at start-up if phrases were present at menu level 3 but not at higher levels.
  • Tooltips not showing on ComfortClient status bar items.
  • Monitor Log and Event Log panels are now rewritten. Full width highlighting is available. The Monitor Log size now defaults to 5000 rows before the panel switches to FIFO mode; this can be increased to 32000 max via direct edit of the ComfortClient configuration file.
  • System Information menu item now subject to the PersistConfigurationMenu option and only otherwise available when signed in. It can also now be closed with the Red \"X\".
  • Password length between 4 and 6 digits is now enforced.
  • Decode of minor version part of u? response; did not insert a leading zero when single digit.
  • The AutoSave option can now have an interval of between 10 and 3600 seconds (1 hour).
  • The Monitor Log panel did not show any entries during FastStart mode (ie the first time the Client was run) due to the log size incorrectly defaulting to zero. Did display OK for second run onwards.[suP]
New Features
  • ComfortClient can now be started with command line parameters. This is added mainly to improve the user experience when running over a WAN. Using these in conjunction with windows shortcuts enables the Client to be started differently. For example over Remote Desktop (RDP) connections the fade-in on the splash screen can slow down start-up significantly; the -F argument turns this off. Run \"ComfortClient.exe /?\" for a full list of the current arguments.
[/suP]
For this version I\'ve changed the way the files are posted.  The Help file is quite large now so I\'ve split off from some of the zips so you can download separately.

For downloads see:

*** Link Removed,  see download link at http://www.comfortforums.com/forum65/1948.html instead***



Reply
#19
Thanks Julian, thats great. You have brought it a long way
Do you plan to have installable versions of the Comfort Client? I think that would be easier to manage  as far as folders, versions, distribution etc
regards
Chiu
Reply
#20
Hi Chiu,

I dont have an installer tool and as a private deveoper cant justify the many hundreds of pounds to buy something like Installshield.

What do you use?

Regards

Julian
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)