It's an install file used by Windows installer.Originally Posted by Bugbyte
YGPMOriginally Posted by 0l33l
Downloaded your app and started using it today. It works well and the best part was that I was able to easily configure it in about 10 minutes! I figured out the "parent-child" pretty quickly.
I let it running when I shut the car off so we'll see if it survives hibernation. That's been the biggest problem I've had with apps like Centrafuse.
Stupid, but exciting - I was able to use voice to automatically open and close my screen while driving! I bet the folks in rush hour were wondering what the hell was going on. Unfold. Fold. Unfold. Fold.
One suggestion is to code in an overarching "keyword" for the app to use so it ignores you unless you use that word "Computer, open screen". I coded it in as a parent line but that means for each grammar file I have to put it in.
An additional suggestion is to give it a user selectable option to respond to you "Computer open screen" "Executing command". Also, some feedback at the bottom of the window to let you know that it heard you even if it didn't understand you. It does tell you when it understands you but otherwise you can't tell if the app is working or not. Something like: "Unable to decode" or maybe even let the user put the text in. This should also be able to be spoken.
Also, I know it can send key strokes but is there a way to sendkeys to an application? I use FrodoSatX and it doesn't have hotkeys but you can use sendkeys. This might be useful for other apps.
Thanks for the beta. I've found it easy to use and so far no bugs, but we'll see today when I start the car and say "iBug, open screen"
Originally Posted by Bugbyte
I can easily impliment talkback. Also, I will put in a "hypothesis" bar that will display what it thinks you are saying, even if it doesn't confirm it.
I am almost finished with a spelling feature, that will let you type hands free.
This will all be on the next release.
btw, do you think that the response should be "Command recognized" or.. just simply say what the command is. "Open screen"
also.. i'm not sure if i documented this, but if you make the master command "independent", then you don't have to say the master command, just the child command.
How about the default is "Command recognized" and the user can make it say whatever he/she wants?
Sorry to report that the app didn't survive hibernation today! It's a little murky for me because the screen is folded close when I start the car. If it doesn't open, that may be because the computer hasn't resumed from hibernate yet or it could be because it hasn't survived hibernation.
I mucked with it a bit when I got home and it wasn't recognizing anything. Then, after I hit the edit settings and then save defaults it was working perfectly. I tried it a couple of times and then put it back to hibernate. I'll check again tomorrow morning to see if it survives sleep.
The spelling feature will be very cool. My kids often ask me to pull up specific songs while driving but I tell them I can't operate the software for searching while we're moving. Test it out in either Centrafuse or Frodoplayer to see if you can perform a search in those apps.
It would be super cool to be able to run a sequence like "Close FrodoSatX", "launch Frodoplayer", "Search", "G-R-E-E-N-D-A-Y", "Down", "Down", "Play", "Minimize", "Launch GPS".
the idea is.. you make an ini file like:
you would say, "search, E A G L E S" then it would type Alt(s), EAGLES, down, down, enter, then open gps.
the way i have it coded now.. it will process all the command before [spell].. then wait for you to say "E A G L E S FINISHED", then it will process the commands after the [spell] tag.
As far as the response, I will have two options. One will be to respond with a phrase that is typed in by the user, and the other will be the command that was recognized. (or both at the same time)
It will work with frodo as long as frodo has hotkeys of some sort.
Great! v1.3 will survive hibernation as well.