6.x Beta Release Discussions Thread

[gReatAutomation]

The release URL provided is throwing an error.

Download Link: https://www.charmedquark.com/Web2/Downlo..._6_0_1.exe

[Dean Roddey]

Oy! It's not a Beta, it's a real release, so just remove the Beta bit. I'll update it.

[kblagron]

The 6.0.1 release brought my Logic variables over from .917. It also fixed the help system so that I can use the non-secure port. Thanks!

[kblagron]

Just a comment.  I am not sure why, but either my upgrade to 6.0.x  or the latest Windows Cumulative Update switched my Windows Voice from Zira to David, but I assume it was most likely Windows.  I guess it is possible that Zira changed her gender in todays times  .  Anyway, thought it was a bit odd.  Anyone else see this?

I was able to switch it back fairly easily in the Speech Recognition tab in Control Panel.

[Shaky]

I think we did a fairly similar upgrade path for CQC and had similar issues. My Windows voice didn't change from the CQC updates though. Maybe it was Windows... I have a few Windows updates I have to take here soon so will see if that triggers for me or not.

[LesAuber]

What happened to the Utils directory in System Macros?

[Dean Roddey]

Hmm... Yeh, it looks like it got deleted somehow. Were you using something in there?

[LesAuber]

Hmm... Yeh, it looks like it got deleted somehow. Were you using something in there?

Yes. I solved this temporarily by copying the Utils directory from 5.4.914 backup but didn't see that as a long term solution.

[kblagron]

What system macros are stored in there?

[gReatAutomation]

What system macros are stored in there?

The folder was located at C:\Program Files (x86)\CQC\CQCData\DataServer\Macros\System\CQC\Utils and contained:


CondPowerOn
//  This macro is used where you need to conditionally power up
//  a device (because it's one of those 'dead if on' type devices)
//  and perhaps need to do a small pause if you do power it up.

SpeakWeatherCh
//  This class is a convenient helper that will speak the current
//  weather conditions as reported by a Weather Channel driver. You
//  just provide the moniker of the driver, and it queries the values
//  it needs, formats them into a string, and then invokes them via
//  the Speech class, which will speak the values on the local system.

StatefulSet
//  This macro is used in those cases where you have a write-only
//  boolean entity (such as the power state in a write-only device)
//  and would like to at least try to keep up with its state so that
//  you can create nicer interfaces and whatnot.
//
//  What you should do is to create a boolean field in the CQC Variables
//  driver, which lets you define any fields you want. In our example of
//  the DVD player, you might call it HTDVDPowerState or some such thing.
//
//  This macro takes 3 parameters:
//
//      1.  The variables driver field to use as the faux value of the
//          entity, which must be boolean.
//      2.  The target field to write to, which must be a boolean field
//      3.  The new true/false state to set
//
//  This guy will look at the current value of the variables driver field,
//  and if it is different from the new state you sent, it will write the
//  new value to both the variables field and the target field.
//
//  This effectively allows you to treat that Power field like a field that
//  is readable, as long as you don't get it out of sync by changing it
//  without updating the variables field that is being used to hold the
//  last written value. Since the variables field will always hold the last
//  written value, you can read the variables field as though it were the
//  actual value of the device (which cannot be written.)

StatefulSetStr
//  This macro is used in those cases where you have a non-readable
//  boolean entity (such as the power state in an IR controlled device)
//  and would like to at least try to keep up with its state so that
//  you can create nicer interfaces and whatnot.
//
//  What you should do is to create a boolean field in the CQC Variables
//  driver, which lets you define any fields you want. In our example of
//  the DVD player, you might call it HTDVDPowerState or some such thing.
//
//  This macro takes 4 parameters:
//
//      1.  The variables driver field to use as the faux value of the
//          entity, which must be boolean.
//      2.  The target field to write to, which must be a string field
//      3.  The new true/false state to set
//      4.  The value to write to the target field if needed
//
//  This guy will look at the current value of the variables driver field,
//  and if it is different from the new state you sent, it will write the
//  value from #4 to the target field, and update the variables field with
//  the newly written value.
//
//  This effectively allows you to treat that Power field like a field that
//  is readable, as long as you don't get it out of sync by changing it
//  without updating the variables field that is being used to hold the
//  last written value.