From: Bill D. <dr...@dm...> - 2013-11-19 01:54:51
|
On Fri, Nov 15, 2013 at 10:13 PM, Steve Switzer <st...@sw...> wrote: > Yeah, I was thinking about this a little and thought there could be an > 'a' option for both, meaning auto. This could be the default. > Excellent. > However, at the point when this code is running, does the object actually > exist for us to test and see what type it is? > >From looking at the .mht file and the .mhp file, the object is created before it is added to the scene. If this was not the case, then wouldn't adding it to the scene would fail? What I do not know is if creating the object is enough so that it's characteristics could be determined. If it is enough then perl code could use that to determine whether to sent up a responder or a controller link or both. Could you then modify read_table_A.pl to generate the necessary code? Might that be possible? It would be another big step in the right direction. Thanks, Bill Best regards, > > Steve Switzer > > --- > Get world-class business I.T. services and a phone system with awesome features that won't challenge your budget!http://www.SwitzerBusinessSolutions.com > > On 11/15/2013 06:32 PM, Kevin Robert Keegan wrote: > > On Fri, Nov 15, 2013 at 8:52 AM, Bill Dripps <dr...@dm...> wrote: > >> Could SCENE_BUILD automatically get the C and R flags from the device >> type rather than requiring the user to set them? >> > > That might could work. > > Perhaps if neither the C or R flag is specified, then it defaults to > what the device is capable of. The only hiccup would be the on_level and > ramp_rate options. Since those two items are last, if you wanted to > specify them, you would need to use ',,'. Of course, if you don't even > want to specify that information, then the SCENE_BUILD line gets very > short. > > > |
From: Stephen S. <st...@sw...> - 2013-11-21 02:22:39
|
I think you're right. Probably the way to do this is to have each object default to controller, responder, or both. It could be changed at the object level (in main mh code), device level or scene level. Seems reasonable. I'll branch and try it out. Steve On Nov 18, 2013 8:54 PM, "Bill Dripps" <dr...@dm...> wrote: > On Fri, Nov 15, 2013 at 10:13 PM, Steve Switzer <st...@sw...>wrote: > >> Yeah, I was thinking about this a little and thought there could be an >> 'a' option for both, meaning auto. This could be the default. >> > > Excellent. > > >> However, at the point when this code is running, does the object actually >> exist for us to test and see what type it is? >> > > From looking at the .mht file and the .mhp file, the object is created > before it is added to the scene. If this was not the case, then wouldn't > adding it to the scene would fail? What I do not know is if creating the > object is enough so that it's characteristics could be determined. If it is > enough then perl code could use that to determine whether to sent up a > responder or a controller link or both. Could you then modify > read_table_A.pl to generate the necessary code? > > Might that be possible? It would be another big step in the right > direction. > > Thanks, > Bill > > Best regards, >> >> Steve Switzer >> >> --- >> Get world-class business I.T. services and a phone system with awesome features that won't challenge your budget!http://www.SwitzerBusinessSolutions.com >> >> On 11/15/2013 06:32 PM, Kevin Robert Keegan wrote: >> >> On Fri, Nov 15, 2013 at 8:52 AM, Bill Dripps <dr...@dm...> wrote: >> >>> Could SCENE_BUILD automatically get the C and R flags from the device >>> type rather than requiring the user to set them? >>> >> >> That might could work. >> >> Perhaps if neither the C or R flag is specified, then it defaults to >> what the device is capable of. The only hiccup would be the on_level and >> ramp_rate options. Since those two items are last, if you wanted to >> specify them, you would need to use ',,'. Of course, if you don't even >> want to specify that information, then the SCENE_BUILD line gets very >> short. >> >> >> > |