--
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 on the web visit https://groups.google.com/d/msgid/fltkgeneral/16874dc4-a667-c1e5-b8b5-4be6a315ab4e%40seriss.com.
From: Greg Ercolano
Sent: 14 July 2022 16:21
To: fltkg...@googlegroups.com
Subject: Re: [fltk.general] A box appears round an Fl_Help_View instance
Thanks Greg, that worked perfectly, both on screen and the resulting print to PDF.
This change would have the benefit that users could set FL_NO_BOX if they want to do so (for whatever reason, background image or anything else) and if they make sure that the text wouldn't scroll, i.e. it would fit in the widget.
Greg and others, what do you think? Should we change this?
I figure a possible downside would be if we change it,
an old app setting box(FL_NO_BOX) accidentally (e.g. a stray
setting in fluid)
would cause that app to smear during scrolling if rebuilt
against 1.4.x.
If so, that might be bad..?
I figure showing a background image "under" a help view
without a scrollbar
would be a narrow use case. I figure to do anything 'fancy' is
best done
in an external web browser by saving the html to a file and
then calling fl_open_uri()
On 7/14/22 11:42, Albrecht Schlosser wrote:
This change would have the benefit that users could set FL_NO_BOX if they want to do so (for whatever reason, background image or anything else) and if they make sure that the text wouldn't scroll, i.e. it would fit in the widget.
Greg and others, what do you think? Should we change this?
I figure a possible downside would be if we change it,
an old app setting box(FL_NO_BOX) accidentally (e.g. a stray setting in fluid)
would cause that app to smear during scrolling if rebuilt against 1.4.x.
If so, that might be bad..?
I figure showing a background image "under" a help view without a scrollbar
would be a narrow use case. I figure to do anything 'fancy' is best done
in an external web browser by saving the html to a file and then calling fl_open_uri()
... I withdraw my proposal to remove the internal FL_NO_BOX -> FL_DOWN_BOX hack because it would be possible to create unwanted and unpredictable side effects.
src/Fl.cxx:1440: if (box() == FL_NO_BOX) { src/Fl.cxx:1441: // Widgets with the FL_NO_BOX boxtype need a parent to src/Fl.cxx-1442- // redraw, since it is responsible for redrawing the src/Fl.cxx-1443- // background...Whatever is done in this if clause it not "correct" because it does not consider any FL_*_FRAME boxtypes which also need a parent with a background.