From 82eb2381e6e8a733e2b5354047c86fd717bee263 Mon Sep 17 00:00:00 2001 From: Michael R Sweet Date: Sat, 12 Jun 1999 13:53:34 +0000 Subject: Updates for 1.0.4. Added changes to event documentation for FL_DRAG and FL_KEYBOARD. Added WIN32 stuff to Cosmo/Optimizer example code. git-svn-id: file:///fltk/svn/fltk/branches/branch-1.0@603 ea41ed52-d2ee-0310-a9c1-e6b18d33e121 --- documentation/events.html | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) (limited to 'documentation/events.html') diff --git a/documentation/events.html b/documentation/events.html index e43066dd5..88ec9b9f3 100644 --- a/documentation/events.html +++ b/documentation/events.html @@ -28,6 +28,10 @@ The mouse has moved with a button held down. The current button state is in Fl::event_state(). The mouse position is in Fl::event_x() and Fl::event_y(). + +

To receive FL_DRAG events you must also respond to the +FL_PUSH and FL_RELEASE events. +

FL_RELEASE

A mouse button has been released. You can find out what button by calling Fl::event_button(). @@ -68,10 +72,14 @@ widget when another widget gets the focus. be found with Fl::event_text() and its length is in Fl::event_length(). If you use the key handle() - should return 1. If you return zero then FLTK assummes you ignored +should return 1. If you return zero then FLTK assummes you ignored the key. It will then attempt to send it to a parent widget. If none of them want it, it will change the event into a FL_SHORTCUT - event. +event. + +

To receive FL_KEYBOARD events you must also respond to the +FL_FOCUS and FL_UNFOCUS events. +

FL_SHORTCUT

If the Fl::focus() widget is zero or ignores an FL_KEYBOARD event then FLTK tries sending this -- cgit v1.2.3