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
I will look into your suggestions. My initial reaction is that you are
right and all isigraph events should select the same way as paint does
and that Jwdw and Jwdp should behave the same.
- Original Message -
From: Oleg Kobchenko [EMAIL PROTECTED]
To: Beta forum beta@jsoftware.com
The automatic selection is already done for paint. It probably should be
done for all isigraph events. Since a single isigraph is always the
selected one this is only of concern if you have multiple isigraphs on
the same form. This would be a slight change in behavior. My guess is
that most
glsel only affects the target of gl commands and doesn't affect anything
else. It would not affect the use of an hwnd of an isigraph for
wsaasync.
- Original Message -
From: bill lam [EMAIL PROTECTED]
To: Beta forum beta@jsoftware.com
Sent: Wednesday, August 16, 2006 10:28 PM
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
The t beta for Windows is available at:
http://www.jsoftware.com/download/j601tbeta_win.exe
This beta includes some updates to the scripts, but the main changes are
in Jwdw and Jwdp to respond to suggestions from Oleg and others on
isigraph behaviour, especially with multiple controls on a
As Oleg points out, now that setinvalid works properly on both Jwdw and
Jwdp, it is generally the preferred design model for painting. That is,
whenever possible, let the painting happen in the paint event handler.
If some event requires a change in the drawing do a setinvalid and do
the new
