| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
cont'd
|
|
cont'd
|
|
|
|
This option can be used to disable pen/tablet support if there are
build problems on a particular platform or build system (e.g. MinGW)
so users can continue to build FLTK 1.5.
Users can also choose to disable pen support if they don't need it.
|
|
|
|
Widget would always call CHANGED but never
RELEASE events, no matter how the when()
flags were set.
|
|
This removes the need to guess names of files each theme gives to cursor shapes
and makes linking with dbus superfluous when the compositor supports
the new protocol.
The old, surface-based approach to cursor shapes remains used for custom shapes.
|
|
|
|
|
|
This is helpful for writing language wrapper, in
this particular case for PyFLTK.
|
|
This rewriting of the FLTK callback function that runs when there are data available
for reading in the socket connecting the app and the Wayland compositor is meant to
facilitate the integration of Vulkan.
This rewriting reproduces the recommended code to read from the socket
documented in Wayland function wl_display_prepare_read_queue() when several threads
potentially read from the socket.
|
|
- update comments, including filenames
- update build instructions for developers in util/cmap.cxx
- update CMakeLists.txt (comments only)
|
|
error: ‘fabs’ was not declared in this scope
|
|
Old code supported only frame styles, this code
can now handle box types with a background.
|
|
This method can be used to set a more appropriate color average to
prevent "graying out" the box colors of the 'plastic' scheme.
Alternatively environment variable 'FLTK_PLASTIC_AVERAGE' can be used
to set the color average value. See docs for details.
Set color average to 45% in test/unittests demo program.
|
|
- The removed code had been disabled in the year 2003 or earlier for
reasons mentioned in those old commits and has never been officially
used again. Use `git blame` to find these commits.
- Update comments and copyright.
- Remove empty lines.
|
|
|
|
|
|
Deferred handling of FL_APP_DEACTIVATE works very well.
|
|
This code generates a lot of
extra events
|
|
This is an attempt. Will verify on another machine now.
|
|
|
|
This event is sent on application level. Add a handler
with Fl::add_handler to receive the event.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cont'd (#259)
|
|
|
|
|
|
The fix puts the first window an app creates on the screen containing the mouse,
because the present window creation code needs to know on what screen a created
window is going to appear before creating it.
|
|
xdg_wm_dialog
|
|
|
|
warning: anonymous non-C-compatible type given name for linkage
purposes by typedef declaration;
add a tag name here [-Wnon-c-typedef-for-linkage]
399 | typedef struct {
| ^
Weird. This file is compiled as C++ but clang warns about a
"non-C-compatible type".
Anyway, this commit fixes the warning.
|
|
|
|
Currently supported Doxygen versions: 1.9.1 and higher.
Tested up to Doxygen 1.13.2 as of today.
Older doxygen versions may generate bogus warnings or even fail to
interpret correct C++ syntax.
|
|
|
|
|
|
|
|
By defining boxtypes with underscores, box
drawing cod ethat was not used was not linked,
but with the introduction of themes, all boxes
are available at all times. Reducing complexity.
|
|
The biggest changes are in src/Fl_Scroll.cxx where most of the changes
are caused only by formatting (alignment). The behavior is the same
for all boxtypes that had been covered by the old switch/case code
and should be improved for other FL_*_FRAME boxtypes that had been
ignored.
|
|
This is a first step to fix some background (re-)drawing issues in
widgets. A new bit in the array of boxtypes can be used to determine
if a particular boxtype uses a solid background (e.g. all FL_*_BOX
types) or if the parent widget is responsible for drawing it (FL_NO_BOX
and all FL_*_FRAME) types, and maybe more ...
The old struct member `set` in the struct of boxtypes has been
renamed to `flags` and is now used as a bit field.
Except these changes, this first commit fixes the focus box drawing
of specific boxtypes, as seen in unittest_schemes.cxx in the
Fl_Check_Button with label "Check", and very likely more.
|
|
|
|
|