Bug: Exception when clicking on an empty Fl_Tabs with OVERFLOW_PULLDOWN

15 views
Skip to first unread message

pvr...@btinternet.com

unread,
Feb 26, 2026, 8:54:00 AM (6 days ago) Feb 26
to fltk.general
FLTK 1.4.4

I get an exception when clicking on an Fl_Tabs with no children. I have handle_overflow set to OVERFLOW_PULLDOWN. 

Trivial case attached.

Regards 
Phil Rose.

test_tabs.cpp

Albrecht Schlosser

unread,
Feb 26, 2026, 1:42:28 PM (6 days ago) Feb 26
to fltkg...@googlegroups.com
On 2/26/26 14:54 'pvr...@XXXX.com' via fltk.general wrote:
FLTK 1.4.4

I get an exception when clicking on an Fl_Tabs with no children. I have handle_overflow set to OVERFLOW_PULLDOWN. 

Trivial case attached.

Thanks for the report and the demo, bug confirmed (currently using FLTK 1.5 / master).

When looking through the FLTK code (src/Fl_Tabs.cxx) I noticed that this is not the only crash when the Fl_Tabs widget has no children. Another crash happens when you use the mousewheel in the same demo program.

Phil, can you please file an official bug report (GitHub Issue) so this won't be forgotten? This needs further investigation.

TIA.

pvr...@btinternet.com

unread,
Feb 26, 2026, 4:25:09 PM (6 days ago) Feb 26
to fltkg...@googlegroups.com
Issue #1366 raised.

Phil.

From: 'Albrecht Schlosser' via fltk.general <fltkg...@googlegroups.com>
Sent: Thursday, February 26, 2026 6:42 PM
To: fltkg...@googlegroups.com <fltkg...@googlegroups.com>
Subject: Re: [fltk.general] Bug: Exception when clicking on an empty Fl_Tabs with OVERFLOW_PULLDOWN
 
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/fltkgeneral/dbb1f4cf-3abf-4afc-bc26-50727ae2f200%40aljus.de.

Albrecht Schlosser

unread,
Feb 27, 2026, 2:15:12 PM (5 days ago) Feb 27
to fltkg...@googlegroups.com
FTR:

On 2/26/26 22:25 'pvr...@btinternet.com' via fltk.general wrote:
Issue #1366 raised.

Thanks for filing the issue - meanwhile it was fixed by Matthias, thanks for that as well.
Reply all
Reply to author
Forward
0 new messages