I am not a fan of reinterpretation sources, because they dilute and distort the actual truth.
I would recomment win32 SDK and Java reference, and work your way through the links and hierarchy. Java API and Swing/Java2D tutorials http://www.google.com/search?q=java+eventhandler http://www.google.com/search?q=java+tutorial+events For win32 messages are in each separate section (window, mouse, each control) http://www.google.com/search?q=msdn+window+procedures http://search.microsoft.com/results.aspx?q=site:windowssdk.msdn.microsoft.com+mouse+input I was also thinking about a tooltip. There are a couple of ways: explicit with support for frameless windows, but that's too eleborate to implement in user code; or use the platform support, which would translate to something like wd 'settooltip id text' with empty text to turn off. For the latter there's no difference whether it's isisgraph or not. http://java.sun.com/docs/books/tutorial/uiswing/components/tooltip.html For MFC it's more involved: win32 ToolTip and CToolTipCtrl. To produce high leve mouse over: on mouse move capture and track boundaries, when outside that's your mouse out. --- Henry Rich <[EMAIL PROTECTED]> wrote: > 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 while. > (the apps display a tooltip). > > Now Eric says the list of events for isigraphs is complete, > and you are telling me that there is no such thing as a > hover event, so I suppose that the apps must start a timer > from each mousemove and draw the tooltip after a period > of no mouse movement. I can do that. > > Can you tell me how to display a tooltip? Is it a > special API call, or a control created over an isigraph? > I'm guessing a special API call, because the tooltip seems > not to respect the boundaries of child controls. > > And do I understand Eric to be saying that tooltips for > non-isigraphs will not be supported, because mouse events > for them are not in plan? (I'm in no hurry and can wait > till after the release to discuss it). > > What I'd really like to find is a website that collects > this information. > > > Henry Rich > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Oleg Kobchenko > > Sent: Saturday, August 19, 2006 6:01 PM > > To: Beta forum > > Subject: Re: Liberty for Events! WAS: [Jbeta] scrollbar event > > > > I also wish you understood the event system better :) > > What is "hover" event? Events like API, can be low level > > and high level, which you generate in your code for > > consumption by your high level handlers. > > > > Windows sends events (messages) indiscreminately, > > while Java won't send any events, unless you register > > a handler for each event (or group thereof). > > (J Windows using MFC is similar to Java though). > > To make it work, J wd "subscribes" at compile time to all > > supported events. Then to avoid the complication of > > maintaining the repertoir of events available to each > > control, it does a clever thing: it delegates the decision > > to wdhandler, which determines by reflection (!) whether > > the control has a handler and invokes it. Very neat I think. > > > > There are two reasons why it's impossible to process > > future unsupported events: in Java, that's a programmatic > > operation requiring concrete classes, etc., not just an event "ID"; > > and different events have additional parameters to pass back, > > like mouse coordinates, etc. > > > > --- Henry Rich <[EMAIL PROTECTED]> wrote: > > > > > 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 J app indicate what > > > events it will handle? Then there will be no need > > > for system modification every time a user makes a > > > good case for an event. The call would be something like > > > > > > EVENT_HOVER 9!:51 <'hover' > > > > > > to start handling the HOVER event. > > > > > > For events associated with a form, the event will pass to wdhandler > > > to be processed in the form's locale. The right argument to > > > 9!:51 is the name of the handler (wdhandler will append > > > form_ and child_ as appropriate). > > > > > > For other events, the given handler will be called directly. > > > > > > Henry Rich > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED] On Behalf Of bill lam > > > > Sent: Saturday, August 19, 2006 10:25 AM > > > > To: Beta forum > > > > Subject: [Jbeta] scrollbar event > > > > > > > > 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 __________________________________________________ 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
