mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-10 01:48:00 +00:00
4341ba6d5c
Constructing a FontSpec in platform-independent code is awkward, because you can't call fontspec_new() outside the platform subdirs (since its prototype varies per platform). But sometimes you just need _some_ valid FontSpec, e.g. to put in a Conf that will be used in some place where you don't actually care about font settings, such as a purely CLI program. Both Unix and Windows _have_ an idiom for this, but they're different, because their FontSpec constructors have different prototypes. The existing CLI tools have always had per-platform main source files, so they just use the locally appropriate method of constructing a boring don't-care FontSpec. But if you want a _platform-independent_ main source file, such as you might find in a test program, then that's rather awkward. Better to have a platform-independent API for making a default FontSpec. |
||
---|---|---|
.. | ||
align_label_left.c | ||
arm_arch_queries.c | ||
arm_arch_queries.h | ||
block_signal.c | ||
buildinfo_gtk_version.c | ||
cloexec.c | ||
dputs.c | ||
filename.c | ||
fontspec.c | ||
get_label_text_dimensions.c | ||
get_username.c | ||
get_x11_display.c | ||
getticks.c | ||
keysym_to_unicode.c | ||
make_dir_and_check_ours.c | ||
make_dir_path.c | ||
make_spr_sw_abort_errno.c | ||
nonblock.c | ||
open_for_write_would_lose_data.c | ||
our_dialog.c | ||
pgp_fingerprints.c | ||
pollwrap.c | ||
signal.c | ||
string_width.c | ||
x11_ignore_error.c |