Messages

1

Feature Requests / Re: Group exclusive action

« on: August 20, 2014, 02:17:16 PM »

cool, waiting for next release
thanks

2

Feature Requests / Re: Group exclusive action

« on: June 15, 2014, 08:05:56 AM »

yes it's possible but i've not only 4 groups it's only for example.
in my idea, if keyboard group is activated, you can always use group.enable or disable on other group if you wan't, but vc do not execute command on this group while keyboard group is active.

deactivated group is always off because, it was off before activate keyboard group.

it's more simple to have exclusive group than manually enable/disable all group and testing with logic for all program who active group if process running.

3

Feature Requests / Group exclusive action

« on: June 15, 2014, 03:56:23 AM »

would it be possible to have an activating group action disabling all the others but keeping in memory status groups.

for example if I have these groups:

default (on)
XBMC (active only for process: XBMC, XBMC not started at this time)
deactivated group (off)
Keyboard (off)

if i exclusive activate Keyboard group, vc respond only command in keyboard group
but if i run xbmc and deactivate Keyboard group i wan't :

default (on)
XBMC (on, xbmc is started)
deactivated group (always off)
keyboard (off)


is it possible to adding this feature ?

4

Bug Reports / Re: Command starting with payloadxml not recognized

« on: June 15, 2014, 03:22:19 AM »

effectivement, je n'arrive plus non plus à faire marcher cette commande sur la v1, je suis pourtant sur d'avoir utiliser souvent cette commande avec succès auparavant.
c'est pas trop grave, je vais remplacer le payload par 4 commandes.
désole pour le dérangement

indeed,I can not seem to run this command on the v1, I have yet to use this command often successfully before.
it is not too bad, I'll replace the payload by 4 orders.
sorry for the inconvenience;)

5

Bug Reports / Command starting with payloadxml not recognized

« on: June 14, 2014, 06:00:24 PM »

a command that worked on the v1 no longer works on v2, command start with payload xml.
if i add a phrase at begining, its work.

Code: [Select]

<?xml version="1.0" encoding="utf-16"?>
<!--VoxCommando 1.9.5.6-->
<command id="397" name="Direction {1}" enabled="true" alwaysOn="False" confirm="False" requiredConfidence="0" loop="False" loopDelay="0" loopMax="0" description="">
  <action>
    <cmdType>InputKeys.Send</cmdType>
    <params>
      <param>{{1}}</param>
    </params>
    <cmdRepeat>{2}</cmdRepeat>
  </action>
  <payloadFromXML phraseOnly="False" use2partPhrase="False" phraseConnector="by" Phrase2wildcard="anyone" optional="False">payloads\4directions-frmonter.xml</payloadFromXML>
  <payloadRange>1,10</payloadRange>
</command>

6

Feature Requests / Re: Not display the OSD in standby mode

« on: June 13, 2014, 03:56:56 PM »

great, I expect the new version with impatience;) thank you

7

Feature Requests / Re: Not display the OSD in standby mode

« on: June 01, 2014, 07:29:35 AM »

Up, it is you planned to add this feature?
or adding "Show OSD on command" and "Show OSD alternate" param in VC.SetOption

8

Feature Requests / Re: Not display the OSD in standby mode

« on: October 06, 2013, 03:23:44 PM »

If you prefer, add an event VC.recognised, i can display OSD myself with custom variable for set state of VC (with VC.On and VC.standby event) and {LastSpoken}.
And add {confidence} for display confidence pourcent.

9

Feature Requests / Not display the OSD in standby mode

« on: October 05, 2013, 01:36:56 PM »

When VC is in standby all command trigger OSD, only "always on" command should display OSD.
OSD frequently popup in noisy environment.

10

Python Scripting / Re: Enable/Disable WSR example

« on: September 28, 2013, 01:02:51 AM »

thank you, I did not think to put the result in the ExecString

i've edited first post.

11

Python Scripting / Re: Enable/Disable WSR example

« on: September 27, 2013, 05:19:18 PM »

I do not succeed to get "result" in function with ExecString. ( i put result in wsron and off command but i think it's work same)

Window.SendMessage action would be better

12

Python Scripting / Enable/Disable WSR example

« on: September 27, 2013, 01:09:01 PM »

How to enable or disable Windows Speech Recognition using SendMessage, I used to activate Dictation mode.

WSRcontrol.py

Code: [Select]

import ctypes

def sendWsrMessage(iMsg):
   SendMessage = ctypes.windll.user32.SendMessageW
   FindWindow = ctypes.windll.user32.FindWindowA
   handle = FindWindow(b"MS:SpeechTopLevel",None)
   if handle:
      SendMessage(handle, 273, iMsg, 0)
      return 1
   else:
      return 0

def wsrOn():
   return sendWsrMessage(101)
def wsrOff():
   return sendWsrMessage(102)
Example of use in xml

VC must be run as administrator

13

Bug Reports / Re: OSD prevents windows to shutdown.

« on: September 27, 2013, 12:41:10 PM »

j'ai redémarrer une vingtaine de fois, je n'est plus eu de bugs, avec ou sans logiciels lancé ;(
I restart a about twenty times, I no longer had any bugs, with or without software launched.

j'essaierai de bien regarder quels sont les programmes lancé la prochaine fois que je rencontrerai ce bug.
I try to look closely at what programs are launched next time I meet this bug.

14

Bug Reports / Re: OSD prevents windows to shutdown.

« on: September 27, 2013, 11:25:16 AM »

i'm on W7 64b, vox 1.1.5.8

i haven't other VC window openned.
this is not always VoxOSD blocking, it changes (VoxRecognisedOSD or something like that)

I have a lot of program running, I do not close any when I shutdown the computer.
(firefox,thunderbird, utorrent, skype, notepadd++ for the most common)

sometimes the computer turns off directly, but most of the time it crashes.

15

Bug Reports / OSD prevents windows to shutdown.

« on: September 27, 2013, 08:11:31 AM »

i've a vox command for shutdown computer with confirm, when i use it, OSD prevents windows to shutdown.
i must cancel shutdown and close vox manualy.
can you close OSD when command is confirmed ?