VC.TriggerEvent bypasses confirmation - NOT A BUG !

[pioneer]

Hi James and everyone. Happy holidays. 

I've been wanting to write about one problem since half a year ago. This applies to the version 2.2.0.7. If you call an event (by VC.triggerevent) which is located in a different command, which must be confirmed, the event bypasses this confirmation and gets called anyway. 

[jitterjames]

Yes this is how it is supposed to work and it has been mentioned more than once on the forum, and is mentioned in the wiki here: http://voxcommando.com/mediawiki/index.php?title=Logical_Command_Builder#Command_Settings along with a workaround. 

When a command is triggered by an event it is assumed that it is done on purpose so it does not matter if a command is marked as requiring confirmation.  The purpose of requiring confirmation for a command is to avoid the false positives that can occur when triggering a command by voice which could result in VC executing a command by accident.

The solution which we have proposed before and which works fine is to use VC.TellVox instead of an event.

[pioneer]

Okay, got it. And yea, I use TellVox instead. But according to the description it's better to use TriggerEvent. 

[nime5ter]

Ha. You are definitely in the top 5% of VC users if you take the time to read the action descriptions.

We have a very hard time convincing people to do that. ;-)

As you note, the action description for VC.TellVox does say "If possible use VC.TriggerEvent instead".  In this case, it's not possible, so VC.TellVox must be used.

It's really for all VC users that we are noting here with a bold!! subject that this is not a bug, because even though it is documented in the wiki and the forum, it is a question that comes up every few months.

It's not personal. We are simply trying to find new ways to let users know that this is not a bug.

A happy 2016 to you as well!

[pioneer]

Ok  

[nime5ter]

Hi pioneer,

You may like to know that, in version 2.2.1.6, James implemented the feature that you and other users have previously asked about.

Per the "Big Change!" notice in the Change Log, commands that require confirmation will now also require confirmation even if triggered by an event. Previously, as you know, such commands only required confirmation when triggered by voice. :-)

http://voxcommando.com/mediawiki/index.php?title=ChangeLog#Version_2.2.1.6

[pioneer]

Big thanks.