A cleanup that wasn't caused this bug. J is called with the event, but
instead of f_t_button it is calling f_t_ocx. Again, thanks for the very
clear report that made it so easy to track down. Fixed in the next beta.
- Original Message -
From: Oleg Kobchenko [EMAIL PROTECTED]
To:
Eric Iverson wrote:
A cleanup that wasn't caused this bug. J is called with the event, but
instead of f_t_button it is calling f_t_ocx. Again, thanks for the very
clear report that made it so easy to track down. Fixed in the next beta.
So it will be f_t_ocx in the future ?
--
regards,
bill
can scrollbar trigger an event while dragging the thumb? IMO hardware is much
faster than that of 10 years ago, more events can be handled when running J.
--
regards,
bill
--
For information about J forums see
I wish I understood the event system better. My primitive
view is that the OS sends J a bunch of events, and J decides
which ones it will handle and which it will pass to user code,
and discards the rest.
Like Bill says, nowadays J can handle a lot of events.
Why not have a foreign that lets the
On IE, it looks like there is no automatic refocus.
When I spin the wheel, nothing happens unless I click
in the child window I want to scroll.
My wheel-left is set to do the 'Back' function. That
function is executed on the most-recently-clicked
parent, regardless of where the cursor is.
On 8/19/06, Eric Iverson [EMAIL PROTECTED] wrote:
What do those apps do with keyboard input in the same case. That is, as the
focus for the wheel moves does the focus for up/down arrow also move. If so, I
think it simply means that mouse move events over the control do an automatic
setfocus.
As far as I can tell in both Windows and Java the mousewheel event is
always and only sent to the control with focus. However, within an app
anything can be done with that event. The app would keep track of
mousemove events to know which window the mouse was in and then the
mousewheel event
If I could learn where to read about the event system,
I'd go there, but till then I will have to rely on
the kindness of friends.
Take the event I called 'hover', which from the uniformity
of behavior of apps I guessed was an event that was
produced when the mouse lingers over a control for a
Henry;
Does the MSDN website cover this?
msdn.microsoft.com (?)
|\/| Randy A MacDonald | APL: If you can say it, it's done.. (ram)
|/\| [EMAIL PROTECTED] |
|\ | |If you cannot describe what you are
reading from this page
http://msdn.microsoft.com/library/en-us/winui/winui/windowsuserinterface/userinput/mouseinput/aboutmouseinput.asp?frame=true#_win32_The_Mouse_Wheel
It seems isigraph could support WM_MOUSEHOVER and WM_MOUSELEAVE message to easy
user's implementation of tooltip or no-focus
It turns out there is a mouse hover event in win32 API.
It also accepts a timeout, so looks like the system
mechanism to support the tooltips internally.
user's implementation of tooltip
Such implementation as a proof of concept
is possible right now with mouse move event,
capture and timer. The
11 matches
Mail list logo