When going forward, sequence by sequence (right blue arrow), it always selects the step #1 in the new displayed sequence.
But, when going backward, sequence by sequence (left blue arrow), there’s two possibilities,
if you are on the first step, it will select the previous sequence and its last step,
else if you are on any other step > 1, it will select the previous sequence and its first step.
Why ?
this way, when locking the “goto” button and browsing through steps backward, when you reach the step one of the sequence, you are able to use the left blue arrow to jump to previous sequence on its last step, which is a better choice than the first one as the “sequence -1” last step is the previous one of the “sequence” first step.
I’m looking if i can reproduce the second problem here…
Is there anything else you can think of I should look at for testing or have I caused you enough problems?
I’m fairly stumped on trying to get the bot on a Wifi link, I was hoping to use a serial to Lan virtual module so that the bot would physically be connected on RS232 but would appear to the P.C. as an I.P. port but the app I have doesnt want to play nicely.
There is one possibility that I’ve just thought of…
If I write a VB.NET app that has a Winsock for SEQ to connect to and a Comm port to connect to the bot, I wonder if I could just wrap the inputs and outputs…That way SEQ would think it was sending to a Socket…Is that right?
Wrote a dopey app in VB6 (dotnot examples are all console so got nowhere) and wrapped a socket to a commport…
Set commport as bot bluetooth virtual port (COM5). Opened SEQ and set the commport on there to something that wasnt going to work (Port 15 in this case) most buttons greyed out.
Set the Client settings to the App I had written and activated.
After a few moments the config dialog appeared and the Sequencer button became available.
Clicked Sequencer and the form loaded ( could see lots of QP going to bot) then got a “Cant show dialog error”.
Closed and reopened and this time got right in and all seemed to work fine.
Played a few sequences just to be sure…
Cant get the dialog error to come back so I cant give you the exact message. If it reappears I will get the message.
But at least it proved the core is working… That one I really am going to play with.
new socket server commands <buttonpress:pose 1> to <buttonpress:pose 16> in order to control the 16 new buttons
sockect server command returns “Ready” or “Busy” as before or now “Paused” if paused or “Error”
if Visual sequencer is not in the “Advanced Play” form.
socket server command ssc-32:ver returns the SSC-32 firmware version as before or now “Virtual” if
connected to the virtual robot.
bug corrected : when clicking on an assigned button (Advanced play form), it wasn’t loading the correct “end” step
sometimes.
Robot Dude, you are gonna ahve to share your secrets… If I was trying to get my missus to do something, the phrase “You know where the stuff is so do it yourself” would have been retort no 1
Wow, Laureatus, you are truely awesome at making SEQ and the other LM software better and better! I am really looking forward to being able to work with SEQ at some point, and am really good at beating bugs out of software. Several years ago, I did maintenance programming/feature updating for a regular job.
I’m on it.
Beth is my right hand man, except she sits on my left and is a girl. lol