Oleg Kobchenko wrote: > Hmm, from what I can see, this is a clever way > to do a callback synced on a message loop, like > a COM call crossing appartment boundaries. > > Suppose such callback will cause automatic glsel > of the dummy isigraph. But will it disrupt other > true isigraphs used for painting? See, by the time > they get their turn, it will happen already on > their own event, mouse or paint, so they will also > receive their glsel at that time. > > Even if you want to paint the other visible isigraph > from the dummy isigraph event, then you can use > explicit glsel. But it is more proper instead to > invalidate the visible isigraph, wd 'setvalid', > (which is marked win32, but it's Java equivalent > is "Component.repaint()"). So by the time it > receives its own dedicated paint, it will be > properly selected. > > Does this make sense? > Or there are any other reasons, why it will break > existing code.
Thank you, I agree with your auto glsel will have little chance to break my code. As a friendly warning, be careful when using winsock sdasync in J without sdselect, my code was presented as an example only. sdasync itself is as reliable as the tcp layer, but J interpreter can choose to ignore events when J is busy, That's why you hear beep sound. Missing a timer or user mouse click events is not important but not so for winsock event. -- regards, bill ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
