updated patch: simplified clone procedure, including clone instructions

Dan, note that I left the "cloning..." status message in, as I'm not yet using the common yaesu clone class for upload/download operations, and instead overriding _clone_{in,out} and _sync_{in,out}. If I remove it, status message defaults to an unsavory "Unknown" with inactive progress bar.

(I did try to remove the custom clone code, but it doesn't work for some reason. So I'll tackle that at a later date.)

-Jens

On Sunday, October 20, 2013 11:59 AM, Jens J. kd4tjx@yahoo.com wrote:

So the new get_prompts() elements for before the "ok" are pre_download and pre_upload. So if we have a second set of prompts elements for after hitting ok, during download, my vote would be for: during_download, during_upload  ;)

On Sunday, October 20, 2013 9:50 AM, Dan Smith dsmith@danplanet.com wrote:

-        status.msg = "Cloning from radio.\nPut radio into clone mode then\npress SET to send" +        status.msg = "Cloning from radio..."

So, my initial plan for this was to have a get_prompts() element for this extra bit as well, instead of overloading the clone status like this.

Would you be okay snipping this and the matching one below out of this patch for the time being until we extend get_prompts accordingly? I've been meaning to figure out where in the UI we should do that. I think for yaesus we need the pre-download instructions to tell you how to get it into clone mode, then start the clone thread, and then display another message that tells you what to push to start the transmission from the radio (like you did above), right?

Something like prompts.start_download maybe?

I think for the upload case, we can get them to put the radio into clone and RX mode before they continue and then jump right into sending the image.

Thoughts?