Keller-1, a project

EDITS: I would like the app to also pause and await input from user when one string is a substring of the other, not just when they are exactly equal. I would like the 'pause' to be measured in microseconds if possible rather than millseconds -- and I would like this pause to occur after every randomly generated character! This app starts with a main window (the control window) which accepts a single parameter which is the time (in milliseconds) that the thread waits for before performing a computation -- this is to prevent the process hogging the cpu. The control window also contains the following data: received: (number) dispatched: (number) match count: (number) match-count/received-dispatched-pairs*100: (number)% The control window also contains a 'start' button, which changes to a 'pause' button when clicked on, and an 'pause-and-input' button should also spawn after the start button has been clicked on. After start is clicked on: two windows are spawned two threads are attached to/associated with each of these windows Each of these windows contains two subwindows: on the left is entitled 'received' and on the right is 'dispatched'. The second-window-process waits for a response/input from the first-window-process. The first-window-process then does the following: Populates 'received' subwindow with just a newline (empty string) (for first iteration only). Generates a string of random characters. These characters can be lower case a to upper case Z and 0-9, with equal chance of each, OR a newline character (\n). Once a newline is encountered, the process populates the 'dispatched' subwindow with the string, and then sends the waiting second-window-process the string. The first-window-process then starts waiting itself for a response/input from the second-window-process. Second-window-process then ceases to wait, having received input from first-window-process. It populates its first subwindow (received) with the received string. It then compares its previous 'dispatched' string to the current 'received' string. If the strings are equal, the second-window-process starts waiting for the control-window to respond with a returned string. The control window opens a dialog that receives a string input from the user. This string is then passed back to second-window-process and is used in place of its own randomly generated string. It then is _its_ turn to generate its own random string, OR use the user-inputted string. It then populates its 'dispatched' subwindow with its own generated string OR user-inputted string. It then dispatches the string to the first-window-process, releasing it once again. The first-window-process populates its 'received' subwindow with the received string. It compares the received string to its previous 'dispatched' string. If there is a match, it waits for a string from the control-window-process, dialog box opens, user input, etc. etc. From here it should be easy to figure out the programs' pattern of behaviour! Please let me know if it needs further elaboration. It should also be self-evident what values go into the control window, but again, let me know if further elaboration is required! I would like the values to use big-number computation so as to achieve precise values and to allow the process to run indefinitely. Thank you.