aboutsummaryrefslogtreecommitdiffstats
path: root/vncviewer/fltk
Commit message (Collapse)AuthorAgeFilesLines
* Mark overridden virtual functionsPierre Ossman2024-06-242-2/+2
| | | | | Use the new "override" keyword to properly differentiate between new virtual methods, and existing virtual methods being overridden.
* Use nullptr in all C++ codePierre Ossman2024-06-244-11/+11
| | | | | It's more readable than 0, and a bit safer than NULL, so let's try to follow modern norms.
* Move custom FLTK box types to valid rangePierre Ossman2023-08-172-1/+6
| | | | | | | | FLTK only allows 256 different box types, but it doesn't actually check this when registering new ones. Move our custom types to a valid range, and add an assert for good measure to make sure we don't overflow FLTK's internal structures.
* Use modern UI colorsPierre Ossman2023-07-141-6/+34
| | | | | Follow the colors that modern desktops use when it comes to background, text and selections.
* Workaround for broken fl_arc()/fl_pie()Pierre Ossman2023-07-141-0/+25
| | | | | | | There is something broken with these FLTK draw routines on Windows. They leave gaps at the start and end of the arc/pie rather than filling the whole specified span. So we need to nudge the numbers a bit to work around this.
* Apply custom theme to FLTKPierre Ossman2023-07-142-7/+204
| | | | | | | | | | | Inspired by modern Windows appearance, and to some extent macOS. They have flat boxes and use white, or very light, colors for interactive elements. Unfortunately we can't directly control the colors of widgets, so instead we just lighten everything that uses this box type. GNOME uses a different design, both their older and newer style. But UI look is less consistent on Linux, so hopefully our new look is decent enough there as well.
* Respect selection color in monitor widgetPierre Ossman2023-07-132-4/+2
| | | | We should have a consistent color set over all widgets.
* Explicitly mark unused parametersPierre Ossman2023-01-041-2/+4
| | | | | This allows us to separate accidentally unused, from explicitly unused parameters, which allows us to turn on such checks in the compiler.
* Remove debugging strdup()Pierre Ossman2023-01-021-1/+1
| | | | | This was not meant to be included in the previous commit. The static storage for the font string is more than enough.
* Keep font name in permanent memoryPierre Ossman2023-01-021-5/+10
| | | | | Fl::set_font() doesn't keep its own copy, so we need to make sure the font string doesn't get freed or overwritten at a later point.
* Respect system UI fontPierre Ossman2022-12-221-3/+34
| | | | | | Use the font specified by the system for UI elements. For Windows and macOS this is straight forward, but Linux is more complex as there is no single source for this information.
* Fix up padding for radio/check buttonsPierre Ossman2022-12-221-3/+3
| | | | | | | Try to follow the actual padding that FLTK adds to these widgets. The extra one pixel on each is because of a bug in FLTK's focus drawing code, where the box is always one pixel too small in both dimensions.
* Reduce indent to same as a normal marginPierre Ossman2022-12-221-1/+1
| | | | | This is how GNOME does things, so let's do the same so things look similar.
* Wider margin around window edgesPierre Ossman2022-12-221-1/+1
| | | | To conform with how e.g. GNOME sets its margins.
* Modern look for options sectionsPierre Ossman2022-12-221-1/+0
| | | | | Outlines are no longer commonly used. Instead visually separated headlines are the norm.
* Change to modern layout in options dialogPierre Ossman2022-12-223-3/+256
| | | | | | | | | Classical tabs are very dated. They are also a practical problem as you get very limited in the numbers of tabs we can have, and how long the text can be on them. Switch to one popular modern model with a list on the left instead where pages can be selected.
* Use standard accessors for Fl_Monitor_ArrangementPierre Ossman2022-09-072-8/+14
| | | | | The accessor functions are called value() for all standard FLTK widgets, so let's keep that theme here as well.
* Rename MonitorArrangement to Fl_Monitor_ArrangementPierre Ossman2022-09-072-26/+26
| | | | | Follow upstream FLTK naming to more clearly indicate that this is a general widget and not TigerVNC specific.
* Split general FLTK appearance to separate filePierre Ossman2022-09-072-0/+86
| | | | | These are general things and not specific to TigerVNC, so let's move it to the fltk specific directory for clarity.
* Split out FLTK utility functionsPierre Ossman2022-09-072-82/+110
| | | | | These have nothing to do with layout, so let's split them to their own file.
* Move general FLTK stuff to own directoryPierre Ossman2022-09-073-0/+858
Let's separate TigerVNC specific things from stuff that could be part of upstream FLTK. These are files that we would like to collaborate with other FLTK users, so they are more liberally licensed and avoid using TigerVNC specific things.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-05 18:50:59 +0000