It would probably be good if we could get rid of all hard coded numbers in FLTK, providing an API to change them, with the current values as defaults. Identifying them all is a chore, but perhaps just start with checkbox and go from there.

OP: in case you're working with a deadline for release on VNC, when I've run into the check mark issue, or issues like those with limitations of labels, I usually take one of two approaches:

• Add leading spaces to the label to add space (easy solution, but hacky)
• Derive a custom class, e.g. "MyCheckbox", from Fl_Group, and put the checkbox and an Fl_Box next to it to act as the more controllable label, allowing custom placement with your own API to manage

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: <fltk/fltk/issues/371/1013371678@github.com>