Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
DELETE UNREFERENCED RESPONSES -
#1
The delete unreferenced responses i thought was a good idea and have used this on several occasions..........

However

What i had NOT considered was that responses used by third party devices (old Prontos) such as bespoke iphone apps (not the Comfort app) are not recognised as being \'used\' by comfigurator. I\'ve just had an instance where i deleted quite a number of responses that were in fact \'used\' by third party devices.......

Not sure how to overcome this one.... perhaps put a warning into the delete tab !

I can provide the .cclx file of the customer in question if needed.

 
Reply
#2
How are these responses \"used\" by the third party devices?
If they are actually used they should not be deleted. If they are then it is a bug and should be fixed, so send the cclx files

However if they are there as standby and not used then they are \"Unreferenced\" and will be deleted by the \"Delete Unreferenced Responses\" function. It is not possible for Comfigurator to know which responses you may want to use  in future

\"Delete Unreferenced Responses\" is meant to delete the responses that are not used[color=\"#ff0000\"] now[/color]

I suggest that \"standby\" responses not be kept in the file but saved as Scenarios which can be imported when you really want to
Reply
#3
We are not talking about \'standby\' responses here.

We have an iPhone which is triggering various responses for controlling a number of devices around a disabled persons home (curtains, blinds, lights, gates, irrigation, automatic doors, etc.). I must stress that this is NOT the Cytech iPhone App, it is a bespoke App which is more appropriate to the user\'s needs and pre-dates the current Cytech App.
The responses that are triggered by this App are not referenced within Comfort, they are triggered only by the iPhone (i.e. a 3rd party device.)Thus, when deleting all unreferenced responses we find that our carefully crafted installation stops working. (I just think an extra confirmation (like the \'unsaved changes\' warning box) would be a good addition to Comfigurator.

Yes, I suppose that in hindsight, it\'s obvious that these responses will be deleted in this instance, but so is the \'unsaved changes, do you want to save.....\'
Reply
#4
We may change the funcction to delete Unreferenced and Unfixed Response
If you are activating responses from a thrid party system OR CWM, you need to FIX the responses, which then appear in BOLD

Reply
#5
Comfigurator 3.33 now Has Delete Unreferenced and Unfixed Responses
Fixed Responses have their response numbers in Bold while Unfixed Responses are not bold.
Fixed Responses numbering are not changed when adding and deleting responses
Responses can be fixed and unfixed using the right click  key

Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)