SendMessage mHwndTextboxMaster, WM_SETTEXT, 0&, StrPtr(s) SendMessage mHwndTextboxMaster, WM_SETTEXT, 0&, StrPtr(vbNullString) SendMessage mHwndTextboxSlave, WM_SETTEXT, 0&, StrPtr(s) SendMessage mHwndTextboxSlave, WM_SETTEXT, 0&, StrPtr(vbNullString) Private Declare Function SendMessage Lib "user32" Alias "SendMessageA" (ByVal hWnd As Long, ByVal wMsg As Long, ByVal wParam As Long, ByVal lParam As Long) As Long
Im looking at the Trick example now and see if I can understand it! no need to send it if the words are also shared the same way. Sharedmemory maybe I could put that "array" into it where I only need to tell the "worker" to check that index. If I get a return, that "position" will get flagged and show a "red wave-line" under the word. The return is an integer of the "position" of the word. that is why I can use it otherwise a range of integer would get unusableĪlso I have hidden textbox that triggers when "change", that way I can send strings as well. If u create a new project, the key works when I typeīut if u add another component (picturebox) on the form, the keyup/down will not work anymore. One very strange behavior of "form_keyup/down" is that I like this method as its create a "raiseevent" kind of solution. Private Sub Form_KeyUp(Ke圜ode As Integer, Shift As Integer) ' secondexeĪnd here is the 2nd exe that receive commands. Keycode is an integer that I can tell the main-exe something. Private Sub Form_KeyDown(Ke圜ode As Integer, Shift As Integer) ' mainexe but maybe someone have something interesting to share?Īnd the difference is that he uses another method to communicate (sharedmemory) its of course better but my solution works well because of: Some people suggest activex-exe but those need to be registered.
Open arena multithreading how to#
Is there a way to do that or another suggestion how to make it better? create 3 FORM and each one is its own thread. to have everything in 1 EXE will make the project large. exe, if u have 1 it will just react for 1 and not 3. exe.- why? because AV don't like to have multiple. Its kind of client/server, as they communicate using sendmessage, much like winsock. each exe is its own instance and u can notice it that is faster. Now, this is not really multi-threading, but close to it. they are also checking each other and quit together. The 3rd main.exe checks the command-line and "makes" it into a "sound"-module The 2nd main.exe checks the command-line and "makes" it into a "music"-module main.exe shell main.exe with command-line parameters
0 kommentar(er)
