Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Driver Configuration w/8 prompts
#1
I have a driver with 8 prompts.  This doesn't work well with the driver configuration window as the 7th option tab appears in the far left position.  The next button does not bring up the 8th option (it moves to Moniker).  Fortunately the upside down triangle in the upper right lets me set all my options and then get to the summary page.


.jpg   Options.jpg (Size: 22.69 KB / Downloads: 8)


--Bob
Reply
#2
There are new prompt types now that generally will allow you to avoid that sort of scheme. There are checkable lists or lists where the user can enter a value for each slot in a list and so forth. These are a lot more convenient for the user and avoids this problem. For what you are doing one of those would be appropriate.

You can check for the new prompt value if present and use that. Else look for the old ones just to support previously installed versions. One gotcha is that when they reconfigure, the old ones will get dropped and they'll have the new one, so they'll have to re-enter the values. But it would be worth it probably long term to switch over to the new prompt type.

The one you want is probably the CfgNMLPrompt. Any slots they don't want to use, leave empty. You get a comma separated list of the values entered, empty values for ones that they left empty. So if you have 8 slots, you'll get 8 values, some possibly empty. So just parse out the values and you have all of the prompts into one.

See the RCS 485 V2 thermostat driver for one example of it. It's used to name the thermostats. The Space value indicates whether the entered values can have spaces in them or not. And you indicate the count of slots you want to provide, 15 in this example.

Code:
<CQCCfg:CfgNMLPrompt CQCCfg:Title="Name Your Thermos"
                     CQCCfg:Count="15"
                     CQCCfg:Spaces="No"
                     CQCCfg:Name="ThermoNames">
    <CQCCfg:PromptText>
        Each entry here represents an RCS thermo address, 1 to 15. Double
        click one to give a name to that thermostat, using only numbers,
        digits, hyphens and underscores, no spaces or other punctuation.
        This will be used to create the fields for each thermo. Any found
        but not named here will have simple Tx type names, where x is
        the thermo address.
    </CQCCfg:PromptText>
</CQCCfg:CfgNMLPrompt>
Dean Roddey
Software Geek Extraordinaire
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  "Client Side Driver Directory Could Not be Cleaned Out" TurboSam 15 702 09-27-2018, 01:43 PM
Last Post: TurboSam
  CML Driver IDE docs - where? rbroders 1 209 09-18-2018, 05:41 PM
Last Post: Dean Roddey
  Timer Driver Question kblagron 5 314 09-14-2018, 02:43 AM
Last Post: znelbok
  reset driver statistics? rbroders 9 661 09-11-2018, 07:50 PM
Last Post: Dean Roddey
  Driver info/stats rbroders 6 595 09-02-2018, 08:34 PM
Last Post: Dean Roddey
  Sonos Driver zra 3 399 09-01-2018, 03:09 PM
Last Post: Dean Roddey
  HTTP Get driver not working znelbok 10 837 08-28-2018, 10:10 AM
Last Post: Dean Roddey
  Can't add fields to ElkDev driver rbroders 4 482 08-07-2018, 06:24 PM
Last Post: Dean Roddey
  Possible to copy all the name in a driver so can paste is elsewhere? ghurty 11 993 07-14-2018, 05:24 PM
Last Post: Dean Roddey
  What cool HA projects/configuration can I work on with my current configuration? ghurty 32 1,912 07-10-2018, 09:54 PM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)