+- Charmed Quark Systems, Ltd. - Support Forums and Community (https://www.charmedquark.com/vb_forums)
+-- Forum: General Discussion (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=3)
+--- Forum: CQC Support (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=9)
+--- Thread: my running post 5.0 wish list (/showthread.php?tid=9898)
Pages:
1
2
my running post 5.0 wish list - jkmonroe - 08-02-2016
Thought I would start this since 5.0 seems fairly solid. If you guys have any thoughts, please post them here and I will keep this top comment updated.
- Plex Clients/Repo - support clients other than PHT and add TV support to repo
- Fade Up/Down - for lighting, dim down/fade up over time
- Spotify - control Spotify App to select spotify connect devices and playlists
- Auto Login - provide a check box to set the environment variable for auto login (this one seems easy and would be really helpful)
- Button Time-Out - add ability for short time-out on successive button pushes on client (1-10 sec): See here for description
- CML - ability to read http body in CMLBinBase so I can finish my Automatic Car Adapter driver
- CML - TCP Listener
- CML - ability to create media repos
- CML - ability to create client interfaces
- CML - allow packaging outside of Macros dir, specifically allow CMLBin, Macrofileroot, and Web server files in CQC packages
- Nest - investigate why snapshot URL is missing even with subscription
- Yamaha Receiver - update/modify the Yamaha Generic YNCAV driver to accommodate new models
- Hue - expose groups/scenes, add support for tunable white bulb
- ISY - expose lock status messages to the driver
my running post 5.0 wish list - Dean Roddey - 08-02-2016
We should already support any Plex clients that have sufficient functionality exposed. I've tested it with the Roku3 Plex client.
my running post 5.0 wish list - jkmonroe - 08-02-2016
Dean Roddey Wrote:We should already support any Plex clients that have sufficient functionality exposed. I've tested it with the Roku3 Plex client.
hmmm. OK, I will give it another pass, but I don't think the XBox One client works with it.
my running post 5.0 wish list - Dean Roddey - 08-02-2016
It may not. They aren't required to implement any particular amount of functionality and some just won't have enough to work.
my running post 5.0 wish list - Deane Johnson - 08-02-2016
Wishes:
Ability to eliminate need for logging-in with a check box.
Ability to add short time-out on successive button pushes on client (1-10 sec).
my running post 5.0 wish list - jkmonroe - 08-02-2016
Deane Johnson Wrote:Wishes:
Ability to eliminate need for logging-in with a check box.
Ability to add short time-out on successive button pushes on client (1-10 sec).
i can add them, but can't we do both already? you can auto-login by setting an environment variable, and you can put in a short timewait in any command on your interface.
ill add them to the top post.
my running post 5.0 wish list - wuench - 08-02-2016
Piling on with CML stuff:
Immediate Need - Ability to read http body in CMLBinBase so I can finish my Automatic Car Adapter driver
Other stuff:
CML TCP Listener
Ability to create media repos in CML
Ability to create client interfaces in CML
Allow packaging outside of Macros dir, specifically allow CMLBin, Macrofileroot, and Web server files in CQC packages.
my running post 5.0 wish list - Deane Johnson - 08-02-2016
By "time wait" I would assume that might mean the button always has a time wait, even on the first push.
Back when I was using Elve, I got John to add it. It was great in stopping the problems associated with finger bounce and the like. Once the button gets a valid tap, it is dead for the length of time programmed in. That way, the button reacts normally the first time the activation is valid, but is locked out from a second activation for the set amount of time, usually 3 or 4 seconds.
An example is with toggle Action. The DVD Player tray is an example.
my running post 5.0 wish list - jkmonroe - 08-02-2016
Deane Johnson Wrote:By "time wait" I would assume that might mean the button always has a time wait, even on the first push.
Back when I was using Elve, I got John to add it. It was great in stopping the problems associated with finger bounce and the like. Once the button gets a valid tap, it is dead for the length of time programmed in. That way, the button reacts normally the first time the activation is valid, but is locked out from a second activation for the set amount of time, usually 3 or 4 seconds.
An example is with toggle Action. The DVD Player tray is an example.
ahh, ill add a quick link to this description in the top post. that makes sense.
my running post 5.0 wish list - batwater - 08-02-2016
My immediate wish/request: Update/modify the Yamaha Generic YNCAV driver to accommodate new models as they are released. Perhaps configuration driven. Yamaha does spell out command syntax for each model in a structured file format.