| Age | Commit message (Collapse) | Author |
|
* adds FL/fl_callback.macros.H
* adds FL_FUNCTION_CALLBACK_n(widget, function, [type, data])
* adds FL_METHOD_CALLBACK_n(widget, class, instance, method, [type, data])
* adds FL_INLINE_CALLBACK_n(widget, [type, name, data], callback_body)
* adds `examples/callback`
* full documentation
|
|
|
|
Pressing the shift key while using the mousewheel changes
horizontal to vertical scrolling and vice versa. This allows users
with a standard mouse with only one scrollwheel to use it for both
scrolling directions.
This concludes "handling shift + mousewheel" for all supported platforms.
|
|
Pressing the shift key while using the mousewheel changes
horizontal to vertical scrolling and vice versa. This allows users
with a standard mouse with only one scrollwheel to use it for both
scrolling directions.
Note: other mice that have either two buttons or a scroll ball can
generate both horizontal and vertical scrolling in one action. This
commit does not affect such behavior.
This patch is different than the one in file 'scroll.patch' (STR 3521).
It takes care of distinct mousewheel delta calculation for vertical
and horizontal mousewheels and avoids the "fallthrough" case.
Note: macOS takes care of this, there's no special handling required.
To do: the Wayland platform still needs to be updated.
|
|
Pressing the shift key while using the mousewheel changes
horizontal to vertical scrolling and vice versa. This allows users
with a standard mouse with only one scroll button to use it for both
scrolling directions.
Note: other mice that have either two buttons or a scroll ball can
generate both horizontal and vertical scrolling in one action. This
commit does not affect such behavior.
This patch has been provided by Manolo in file 'scroll.patch'
(see STR 3521).
|
|
|
|
|
|
No effective code changes, i.e. only formatting, indents and comments.
|
|
+ update fluid dependencies
No code changes.
|
|
|
|
|
|
|
|
|
|
|
|
This commit fixes an error in the cube demo appearing specifically with the AMD Radeon GPU.
|
|
This reverts commit 3049e6394a3376f7fff1c8cde19fd7bb1a9252ec
as agreed upon in GitHub Issue #733.
|
|
|
|
Wayland protocol error messages now give the protocol name and the error code.
|
|
Thanks to Matt for the improved docs, I just fixed some typos and
added '()'s for better doxygen comments of functions.
|
|
|
|
Libdecor complicates what should be simple, to close a decorated window,
because it uses the titlebar after return from the closing callback function.
Thus, FLTK delays the sending of the FL_CLOSE event to the window,
only when libdecor runs in CSD mode.
|
|
Does not change the original API but adds a function and
keeps the original automatic.
|
|
|
|
When rendering the OpenGL layer, this prepares the FLTK rendering
parameters and restores them after FLTK rendering.
|
|
|
|
|
|
|
|
|
|
|
|
Part 1: [-Wreorder] 'shortcut_value’ will be initialized after ...
Part 2: [-Wunused] unused variable 'Y'
|
|
Also, use KWin to name the KDE desktop's Wayland compositor.
|
|
|
|
|
|
New file: Fl_Button_Type.cxx
|
|
Make background color and text (label) color of the transient scale
display consistent with tooltip colors.
|
|
|
|
The old version would send FL_MOVE events after dragging with more
than one mouse buttons pressed, as soon as the first button was
released.
The new version sends FL_DRAG until the last mouse button is released
and then FL_MOVE, as usual.
This change affects dragging only if more than one mouse button is
pushed and held while dragging. The order of pushing and releasing
mouse buttons does not affect the behavior.
|
|
|
|
Note: this may be somewhat confusing if the user enters out-of-range
values manually because they are overwritten immediately with valid
input but the effects seen in issue #749 are IMHO worse.
|
|
Notes:
(1) Fl::e_state holds the current state of all mouse buttons which is
returned by Fl::event_buttons() - "plural form".
(2) Fl::e_keysym holds the "key" of the current event which can be a
mouse button, returned by Fl::event_button() - "singular form".
|
|
... in Fl::event_button().
This can be seen when two buttons have been pressed simultaneously
and then released (see test/handle_events.cxx).
|
|
|
|
|
|
|
|
|
|
Document typical (recommended) usage and platform specific behavior.
|
|
|
|
Also, reorder members of class Fl_Wayland_Gl_Window_Driver
|
|
The additional [NSOpenGLContext flushBuffer] messages appear necessary when an Fl_Tile contains
2 or more GL subwindows.
|
|
|