summaryrefslogtreecommitdiff
path: root/test/font-options.c
Commit message (Collapse)AuthorAgeFilesLines
* Add color palette optionAdrian Johnson2022-06-171-0/+4
|
* [test] Build test suite into single binary.Chris Wilson2008-10-311-8/+9
| | | | | | | | | Avoid calling libtool to link every single test case, by building just one binary from all the sources. This binary is then given the task of choosing tests to run (based on user selection and individual test requirement), forking each test into its own process and accumulating the results.
* Make the lcd_filter API privateCarl Worth2008-09-181-4/+0
| | | | | | During the cairo summit it was decided that this API is to freetype- specific to be in the general cairo interface for now. This will likely come back again soon as a cairo_ft-specific interface.
* [test] Initialise test context.Chris Wilson2008-08-181-13/+6
| | | | | Fixup a couple more tests that do not initialise a test context for themselves.
* Add tests for the new LCD filter APISylvain Pasche2008-08-051-1/+5
|
* [cairo-scaled-font] Create error objects on demand.Chris Wilson2008-02-151-1/+1
| | | | | | | | | | In order to correctly report the error back to the user during the creation of a scaled font, we need to support a nil object per error. Instead of statically allocating all possible errors, lazily allocate the nil object the first time we need to report a particular error. This fixes the misreporting of an INVALID_MATRIX or NULL_POINTER that are common user errors during the construction of a scaled font.
* [cairo-font-options] Disallow use of NULL font-options.Chris Wilson2008-02-151-22/+29
| | | | | | | | | | | | | | | Partial revert of commit 0086db893cba90dc73824d77c661d2965ad48112. This is a follow to the earlier commit that allowed creation of scaled fonts using a NULL font options (by interpreting the NULL as meaning use the default options) to reflect the comments made by Behdad (http://lists.cairographics.org/archives/cairo/2008-January/012714.html). The intent is that the public font options getter/setter API has similar defensive behaviour to that of the core objects - i.e. do not overwrite the nil object and if the object is in error then return the default value. For the indirect use of a NULL/nil font options (e.g. creation of scaled fonts), then an error should be returned rather than crashing.
* [test/font-options] Check for HAVE_FCFINIChris Wilson2008-02-151-0/+2
| | | | Only pull in the fontconfig headers if we actually use FcFini().
* [test/font-options] Check the defaults values.Chris Wilson2008-02-151-4/+20
| | | | | Exercise the getters by checking that a fresh cairo_font_options_t has the default values.
* [cairo-font-options] Treat NULL as a default cairo_font_options_tChris Wilson2008-01-171-0/+91
Interpret a NULL cairo_font_options_t as the default values - i.e as if it were a fresh pointer returned by cairo_font_options_create().