possible bug with xml payload

[Wanilton]

My http runing in OS win7 64bits, obrigado mesmo assim.

[jitterjames]

I've tried that and it is too buggy to be of any use.  It disabled ALL your bluetooth devices, and the idle timeout times out even if you are using the remote.  The developer seems to have given up on the project...  Do you actually use that Marcel?

BTW, it's also not ideal, but you can put the remote to sleep by holding down the button for 6 (I think?) full seconds.

[derelict]

yes i use it with the windows stack on windows 7 x86!

the only bluetooth device i'm using on my EG Host is the PS3 remote :-)... so i have no issues with disconnecting ALL bluetooth devices.

Yeah... sometimes the idle timeout fires while using the remote... but this is very very rare in my case... maybe 1-2 times a week.... then wait a few seconds... and i works again.

for me this was the cleanest solution without doing any nasty tricks/scripts in EG while still using the latest ps3 plugin.

Marcel

[jitterjames]

well for me it would always time out every (x) seconds no matter what.  It was really annoying.  I can't remember if I was on x86 or x64 when I tried it last.  Are you sure it doesn't work on x64?

Wanilton, do you know what bluetooth stack you are using?  The usual options are Microsoft builtin-in, Widcomm, and BlueSoleil, and maybe a toshiba stack...

We have hijacked this quite nicely.  I suppose I should move all this chatter to a special "not about VoxCommando" topic!

I'm uploading a whole bunch of new features in a minute with version 0.83 if you want to test.

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

http://voxcommando.com/forum/index.php?topic=101.0

[derelict]

cool.... will this new version also solve the problem of this, hijacked ;-) , thread ?

Marcel

BTW: BD Power Manager will DEFINITELY NOT work on x64.... tried it!

[jitterjames]

I guess, since we are now talking about VC again...

[derelict]

well... it sort of ;-)

remember the workaround to put those file into separate folders ?.... no i get an error:  "_1 rule reference not defined" just after my first folder with the xml payload file is processed !?

Marcel

[derelict]

moving the commands back into one folder doesn't work either :-(

[derelict]

i don't want to push anything.... just wondering if you've found the problem... or if i can assist you with something ?

marcel

[derelict]

just saw that there is a 831 version and gave it a try... it now loads without errors... but i still can't put all the commands into one folder :-)

[jitterjames]

I know what the problem is but there is no real solution.  I have found that if I load the payloads one way it can sometimes cause an error with certain complex* commands.  If I load the payloads another way (less efficient) it may work with those commands and not with others.

So VC will try the efficient way first, and if that fails, it will try the less efficient way, and if that fails, it should at least tell you which group is causing problems, and then load everything else.  I think it only double-fails if you put a bunch of complex* commands into a single group.

I am 99.9% sure that this is a glitch in the windows speech API.  They probably don't know about it, probably will never find out, and probably wouldn't care even if they did.

Anyway I feel the problem is basically solved.  VC does the most efficient thing that works, and if that fails you just need to break up your commands into groups.  Until we encounter a (real) command that won't work even when it is in its own group, I'm not going to spend waste any more time (or hair  ) on it. 

Note that you can break your group up into multiple groups of the same name.  That way you can still use the same enable and disable group commands and it should enable/disable them all.  If not there are new commands which enable and disable groups using substring matching.

(* by complex commands I mean commands that use multiple XML pair payloads where phrases are mapped to values.)

[derelict]

ok...i'm fine with that 

version 832 works for me now... with separate folders though... but that cool for me ;-)

actually i'm glad that i'm using "advanced" features :-)

marcel

[derelict]

do you have any news/progress about this "issue"... or still status quo ? .... just wondering! :-)

any idea why this:

Code: [Select]

       <command name="turnonoffdevice" enabled="true" confirm="False" loop="False" loopDelay="0" loopMax="0">
            <action>
                <cmdType>EventGhost</cmdType>
                <cmdString>statecontrol</cmdString>
                <cmdRepeat>1</cmdRepeat>
            </action>
            <payloadFromXML>C:\_Applications\VoxCommando\powerstates.xml</payloadFromXML>
            <payloadFromXML>C:\_Applications\VoxCommando\devices.xml</payloadFromXML>
        </command>
is causing vc to crash (windows error reporting)

powerstates.xml contains payloads with values like: "on,power on"
devices.xml contains payload with values like: "dvbviewer, satellite"

Marcel

[jitterjames]

does it crash when you load it or when yo try to execute the command?

you need to have a phrase somewhere in there, you can't just use payloads alone.  If it crashes when you issue the command it's because it can't figure out which actual command you mean, and so it doesn't know where to look for the actions to perform.

I should probably write some more robust error reporting for this (and other) situations.

[derelict]

Yes... It crashes as soon as i say one possible combination of the two payloads.

I can "solve" it with a phrase like "state" in the beginning... But it would be cooler to be able to say like:

"Power off" "television"

Instead of:

"state" "power off" "television"

Whereas "state" is the phrase.

Can this be fixed somehow?