Compare http://www.google.com/search?q=WM_LBUTTONDOWN+Notification and http://www.jsoftware.com/books/help/user/isigraph_events.htm
In latest j601 it reads For mouse events the wdhandler variable sysdata contains: x y width height leftbutton rightbutton ctrl shift middelbutton xbutton1 xbutton2 wheel So you need the handle of the other J's isigraph and SendMessage (or PostMessage) with the WPARAM and LPARAM encoding your custom values, which will make their way into the sysdata values. But I am not sure it's better than other ways IPC, like sockets. Although, listening J will have to be locked in a loop. Unless you want to use the socket select on a message loop, as Bill does. Also there is a section on win32 synchronization on MSDN of a related interest: http://www.google.com/search?q=Synchronization+Functions --- Henry Rich <[EMAIL PROTECTED]> wrote: > 2) what's this about using an isigraph to create an event > for a unique socket? Bill's script was interesting, but > why does a mbldown event result, and what is sysdata after > the mbldown? And is there any way to extend this to > provide event-signaling between J processes? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
