Messages

1

VoxWav Free and VoxWav Pro / How to differentiate between VoxWav voice commands and those coming though mic

« on: December 19, 2014, 07:45:50 AM »

I see that the VoxWav thing can handle responses. That's great, but I want to be able to send responses to commands coming from the phone back to the phone, but speak responses coming through the PC Mic through the PC speakers. I know there's an event for when it processes the WAV, but setting a variable and then resetting on responding would be a clunky (and likely problematic) solution.

Any suggestions welcome. Am sending everything to EG to handle, which can then trigger an event in VC to respond back to the phone when appropriate (or perhaps just broadcast UDP straight back to the phone), just need something in the initial payload to signal when this should happen. Otherwise, EG speaks as normal through the PA system (connected through PC line out).

2

Bug Reports / Re: a non standard beahviour from VC rather than a bug

« on: December 18, 2014, 02:43:26 PM »

Yes, that's a fairly standard option in Windows apps. Usually termed "Start in Background" or similar.

3

Bug Reports / Re: CM19A RF vs. PLC

« on: December 18, 2014, 02:41:51 PM »

Been about a decade since I've dealt with the ActiveHome Pro SDK (CM19A/CM15A), but don't recall it having any ambiguity with RF vs. PLC. It's one of the most important distinctions for a usable, non-trivial HA setup.

What I see in the VC log with a CM19A indicates both RF and PLC, which is *impossible* with a CM19A. Also don't see commands from the large security remote (keyfob and camera remotes work fine). Don't remember having such an issue with the SDK, but I could be mistaken on that.

It's also strange that it only offers a PLC Send command (may be an SDK issue, but I don't think so). The send does work; but it obviously can't be sent through the PLC (CM19A is RF only).

Will have to hook up the CM15A to see if it works any differently. IIRC, I could send both RF and PLC command through that one (hopefully this thing will realize that). Could even send the RF-only commands (e.g. Ninja cameras) through the CM15A. It's all easily demonstrable from the command line. That's all this thing is doing as it is the only way to communicate with ActiveHome Pro.

Actually, after digging up an old VB application, it appears there is some rudimentary ActiveX interface for AHP, but it offers nothing more than can be done from the command line (at least for sending commands). Obviously, that's what VC is using, so not sure how this is getting screwed up. Maybe the CM19A has an issue with the SDK (seems highly unlikely) as I mostly used the CM15A with the application. Will see with CM15A...

4

Bug Reports / Re: a non standard beahviour from VC rather than a bug

« on: December 18, 2014, 01:09:07 PM »

Looking at the way other programs work they all seem to do it differently so I don't think we can claim that there are standards here.  For example, most programs in my notification area do not show and hide or minimize the main window at all when left clicking this icon.  MediaMonkey uses left click for play/pause, many others do nothing.  Most programs offer a context menu with a right-click, which VC does as well.

The standard is (and always has been):

1. Double click the tray icon to re-show/restore the app (default context menu command, should be in bold).
2. Or use the context menu, clicking the default command (e.g. "Show VoxCommando").

That's it.

As mentioned, lots of apps screw this up, so mimicking them won't help.

5

Bug Reports / Re: a non standard beahviour from VC rather than a bug

« on: December 18, 2014, 01:04:55 PM »

Clicking the notification icon will toggle the visibility of VC.  This is how I want it. I'm happy with the way that it works.  I hope it doesn't bother you too much because i don't intend to change it. 

That's definitely wrong and you should change things based on user demand, not your own personal view of how things should work. Looking at other programs won't help; have to read the MS interface standards (from '95). Might be able to get by observing MS applications as they seem to follow the standards in most cases.

When in doubt, make it configurable; but doubt anybody will want the tray icon to toggle the visibility of the window.

6

Bug Reports / Re: a non standard beahviour from VC rather than a bug

« on: December 18, 2014, 01:02:28 PM »

this do not qualify as a bug ... but more a strange behaviour from VC compared to other windows programs.

if one minimize VC from the top right of the window, it will go to be an icon in the task bar (standard for all windows programs) ...
now if the "minimize to tray" is enabled and I click on the tray icon, instead of restoring VC window the icon in task bar goes inactive... another click on the try icon will make the taskbar icon active ... clicking that will restore the window ... it is a bit confusing.

in most programs I dealt with that has a try icon ... it will restore the window weather it was minimised by the minimise button or by the tray icon ...

not a big deal but would be nice if fixed

VC version 2.0.0 (but I noticed the same in previous 1.9.x versions)

It is not standard to "minimize to tray", Windows developers have been screwing that up since '95 and it has become some sort of de facto standard. The tray icon indicates that the application is running in the background (even when its primary window is closed). Has nothing to do with minimizing the window (or shouldn't anyway). Always irritating to minimize a window and watch it suddenly vanish from the taskbar.

If the window was previously minimized, then it should be restored on re-showing via the tray icon. That's all. The rest of it is simply a failure to adhere to standards (though not the ones described).

7

Bug Reports / CM19A RF vs. PLC

« on: December 18, 2014, 10:46:39 AM »

Been about a decade since I've dealt with the ActiveHome Pro SDK (CM19A/CM15A), but don't recall it having any ambiguity with RF vs. PLC. It's one of the most important distinctions for a usable, non-trivial HA setup.

What I see in the VC log with a CM19A indicates both RF and PLC, which is *impossible* with a CM19A. Also don't see commands from the large security remote (keyfob and camera remotes work fine). Don't remember having such an issue with the SDK, but I could be mistaken on that.

It's also strange that it only offers a PLC Send command (may be an SDK issue, but I don't think so). The send does work; but it obviously can't be sent through the PLC (CM19A is RF only).

Will have to hook up the CM15A to see if it works any differently. IIRC, I could send both RF and PLC command through that one (hopefully this thing will realize that). Could even send the RF-only commands (e.g. Ninja cameras) through the CM15A. It's all easily demonstrable from the command line. That's all this thing is doing as it is the only way to communicate with ActiveHome Pro.