Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Good Practices Question (for driver's development)
#1
If the goal is to add a feature to an existing/released CML driver and create a development version. could somebody list the order of opeation using the DriverTestHarnes, Manifest files, modifying from System to User, coping the code from the Macro window, saving.....

I have done it before in various ways and I always find I don't perform the right steps in the correct order and it's a source for confusion.

I couldn't find this "good practices" order in any of the driver development docs.
Reply
#2
I second that. I've done it before but couldn't tell you how I did it and what is copied and placed where.
Reply
#3
I think the general steps would be...

1.) Copy the macro file and manifest file to User
2.) Edit the manifest to:
...a.) reference the new macro path under user
...b.) append -DEV to the driver name and model
3.) Open the file in the test harness and change the macro's path reference to the new one.
4.) Save it and verify it compiles ok
5.) Develop away...
Wuench
My Home Theater/Automation Website

[THREAD=5957]BlueGlass CQC Config[/THREAD]
[THREAD=10624]Wuench's CQC Drivers[/THREAD]
Reply
#4
You shouldn't actually copy the macro file. Just change the manifest, open the manifest, let it create the new file, then copy the original driver into the new one. It's best never to try and play any tricks behind CQC's back. Let it create files and such. You never know how a file might be tied to its location.
Dean Roddey
Explorans limites defectum
Reply
#5
I followed Wuench steps with Dean's improvement and expected to see both two driver when trying to Add a drivers with the Admin but don't see the -Dev driver. Just the original

The steps I took were:

1.) Copy the manifest file to the User directory
2.) Edit the manifest to:
...a.) reference the new macro path under user
...b.) append -DEV to the driver name and model
3.) Open the original file in the harness and save the in the test in the macro window
4). Open the modify file from the User directory, let the harness create a new template
5.) Copy and saved old code and change the macro's path reference to the new one.
6.) Save it and verify it compiles ok
7.) Develop away...

Tried to load the -Dev driver but didn' see it in the list.

Any ideas? I must doing something wrong
Reply
#6
It's not going to show up until you either:

1. Put the manifest in the [cqc]\CQCData\DataServer\Manifests\User\ directory on the master server, and cyle the machine

or

2. Create a driver pack and import it, which will do the above for you. It'll also overwrite the macro, but that's OK since the contents will be the same.


For a developer working on the driver, #1 is usually easier. Also be sure to change the short description in the manfiest to include something that indicates it's the development version, since that's what shows up in the list.
Dean Roddey
Explorans limites defectum
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Driver for Amazon 4k Stick Darrie 3 514 01-15-2022, 02:21 PM
Last Post: znelbok
  CQSL Interface Driver connects but no control NightLight 3 571 10-26-2021, 01:12 PM
Last Post: NightLight
  SSL Certificate Question gReatAutomation 1 950 10-26-2020, 07:48 AM
Last Post: gReatAutomation
  ClickPLC driver now failing after upgrade znelbok 2 997 09-21-2020, 10:48 PM
Last Post: znelbok
  Pentair driver tom 5 1,990 08-02-2020, 11:29 PM
Last Post: kblagron
  Marantz receiver driver (IP) dlmorgan999 6 2,086 05-15-2020, 03:32 PM
Last Post: dlmorgan999
  V2 Question - OpenWeatherMap Using their New JSON Data Feed kblagron 7 2,136 05-07-2020, 01:40 PM
Last Post: Dean Roddey
  Variables Driver Client gReatAutomation 4 1,679 04-25-2020, 12:46 PM
Last Post: gReatAutomation
  Dynamic Overlay Question bryanb 4 1,372 04-17-2020, 03:48 AM
Last Post: bryanb
  Reconfig of Driver Causes Built In Triggers to Fire gReatAutomation 2 1,242 03-25-2020, 04:09 PM
Last Post: gReatAutomation

Forum Jump:


Users browsing this thread: 1 Guest(s)