![]() |
|
ComfortClient - Printable Version +- Comfort Automation/ Security System Forums (https://www.comfortforums.com) +-- Forum: Software Applications (https://www.comfortforums.com/forum-4.html) +--- Forum: ComfortClient (https://www.comfortforums.com/forum-65.html) +--- Thread: ComfortClient (/thread-1434.html) Pages:
1
2
|
- juwi_uk - 04-25-2009 Hi all, I\'ve posted 1.0.17.2. Solves a couple of Ingos problems:
<link removed by JUWI_UK> Regards Julian - juwi_uk - 04-25-2009 Hi Ingo, Quote:Cbus Tab: Can I get a screenshot of these \"empty responses listed\". Should be easy to fix but I\'m intrigued why they are happening in the first place. The wraparound happens automatically depending on the length of the text on the tab. Not much i can do about that except astyou say make the default tab text shorter. I\'ve corrected for you in 1.0.17.2 (posted). - Ingo - 04-26-2009 Thanks for the updates, below are the screenshots as requested. - juwi_uk - 04-26-2009 Hi Ingo I cant exactly see from your screenshots but is for example \"Response194\" in both lists or just the one? Two possibilities i see: (1) I am listing blank values as you say (2) They aren\'t blank in as much as they might have definitions behind them which are matching the filter but they are \"blank\" from your perspective in that you aren\'t using them and hence they have default names You could open the cclx file in an editor and find the section with say \"Response194\" and see if it has \"X10\" anywhere in the action strings. If (1) an easy one to fix. Let me know. Julian - Ingo - 04-26-2009 Julian, I see the problem. Response number 194 on the X10 side is actually the name of Response name X10A14OFF (if that makes sense). Inside that response is a default X10 command hence your filter works fine. It is confusing but it works... <Response Fixed=\"false\" Number=\"194\" Description=\"X10 A14 OFF\" Name=\"X10A14OFF\" ActionCodeString=\"195,65,14,7, 255\"> <ActionSource> <string>X10 A14 Off</string> </ActionSource> <Errors /> </Response> Response name \'Response194\' is referring to Response number 227 which is blank and not listed under X10. <Response Fixed=\"false\" Number=\"227\" Description=\"\" Name=\"Response194\" ActionCodeString=\"255\"> <ActionSource /> <Errors /> </Response> On the CBus side Response name 243 is actually Response number 277 but this time it is blank and shoiuldn\'t be listed under the CBus tab. <Response Fixed=\"false\" Number=\"277\" Description=\"\" Name=\"Response243\" ActionCodeString=\"255\"> <ActionSource /> <Errors /> </Response> Ingo - juwi_uk - 04-26-2009 Hi Ingo Quote:Response name \'Response194\' is referring to Response number 227 which is blank and not listed under X10.As you say, these are blank so nothing that should make it appear in the filter lists other that there is a code issue somewhere. Let me look now and I\'ll do a 1.0.17.3 version to fix. Regards Julian - juwi_uk - 04-26-2009 Hi I\'ve posted 1.0.17.3 in response to Ingo\'s feedback. Quote:Bug FixesDownload from link below: <link removed by JUWI_UK> Regards Julian - juwi_uk - 04-26-2009 Hi All, I\'ve posted 1.0.17.4. The fix with ClickResponses is important as when greater than 255 it called the wrong Response and so I thought it was important to post the fix. Bug Fixes
<link removed by JUWI_UK> Apologies for the \"build-fest\" this weekend but with Ingo testing I wanted to implement any issues as we found them especially as he\'s testing kit I don\'t use. Regards Julian - juwi_uk - 04-28-2009 Hi All, I\'ve noticed a problem with 1.0.17.4 and specifically the Floorplan Editor. If you edit a larger Floorplan than your screensize, scrollbars will appear automatically (by design). If however you save the Floorplan when you have scrolled the window then the saved Floorplan will be clipped. Whilst I fix this, if you find yourself in this scenario then make sure you scroll back to the Top (vertical) and Left (horizontal) BEFORE you save. I suggest you also save a copy of your floorplan XML somewhere safe as a backup as best practice and at regular intervals. This issue might have always been there in versions earlier than 1.0.17.4 but I\'ve just noticed it. Apologies. I\'ll make it my priority to fix. Regards Julian |