Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Off Topic (not related to VC) / Drone Life
« Last post by JonPeyton on October 11, 2023, 02:23:29 PM »
I've been working with my latest hobby drone a lot since retirement.They are very capable at performing autonomous feats that really are great.
  If anyone has ever thought they might enjoy this hobby but for some reason you didn't, I encourage you to rethink...
This is from the drone's "Master Shots" level of activities.Basically once I set it on its way Im done.Its flies the route, takes the videos and lands all without input.

https://youtu.be/A3qyiP2d3QQ

JP
22
VoxCommando Basics and Core Features / Re: Trouble viewing incoming TCP info in VC
« Last post by jitterjames on October 04, 2023, 10:39:47 AM »
I have no idea.
23
VoxCommando Basics and Core Features / Re: Trouble viewing incoming TCP info in VC
« Last post by monkee on October 02, 2023, 12:59:04 AM »
Hi, sorry, I was doing more experimentation and figured it out!  Thank you for the reply.

I am, indeed, using Client.Connect.  I needed to increase the delay when using Client.Write, maybe it was closing the connection before I got the response. 

However, my response is followed by \x00\x00\x00 about 20 times, which I do not get in a normal telnet response.  Is there a way to stop that from coming through or do I have to regex the result?  I have to anyway but hopefully there is a better way to get rid of the \x00\'s or not see them at all?
24
VoxCommando Basics and Core Features / Re: Trouble viewing incoming TCP info in VC
« Last post by jitterjames on October 01, 2023, 10:34:01 AM »
Are you using Client.Connect?  Have you read the action descriptions for the TCP plugin?

http://voxcommando.com/mediawiki/index.php?title=Plugin_TCP#Connect
25
VoxCommando Basics and Core Features / Re: Trouble viewing incoming TCP info in VC
« Last post by jitterjames on October 01, 2023, 10:31:23 AM »
It might also help to know what brand and model of receiver you are talking to.
26
VoxCommando Basics and Core Features / Re: Trouble viewing incoming TCP info in VC
« Last post by jitterjames on October 01, 2023, 10:30:11 AM »
Please post the xml for whatever command have tested.
27
VoxCommando Basics and Core Features / Trouble viewing incoming TCP info in VC
« Last post by monkee on September 29, 2023, 10:13:06 PM »
Hi, I'm having trouble getting VC to recognize the response from my receiver using the TCP plugin.  I can successfully send it "(VOL U)" command and the volume goes up.  Then my receiver spits out the current volume, I can see the info in Wireshark, but I cannot see it in VC and my lastresult stays empty.  What can I try?  I'd like to use any incoming volume changes to trigger events. 

Thanks so much!
28
It might be a bit clunky, but you could always make a backup of the clipboard contents first and then restore them after you paste.

It might turn into a mess, or you never know, it might just work perfectly.
29
Ok.

If I go via the clipboard I loose what's in the clipboard every time I dictate.

And I often use the clipboard and dictation at the same time like when editing/creating a document;

Dictating - cut or copy - dictating more - paste...


30
I don't know if it's possible to do this with the keyboard emulation I am using in VC.

Why don't you try to use SetClipboardText and paste using keyboard emulation of Ctrl-V
Pages: 1 2 [3] 4 5 ... 10