summaryrefslogtreecommitdiffstats
path: root/src/libuemf/upmf.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* moved libcroco, libuemf, libdepixelize to 3rdparty folderMarc Jeanmougin2018-04-291-8660/+0
|
* patch should fix bug 1480651mathog2016-01-271-10/+6
| | | (bzr r14617)
* clean up a couple of clang warningsmathog2015-05-281-3/+3
| | | (bzr r14183)
* minor tweaks to libUEMF and related codemathog2015-05-211-5/+7
| | | (bzr r14169)
* patch for bugs 1447850 and 1447382mathog2015-04-271-376/+906
| | | (bzr r14062)
* Patch for libuemf.David Mathog2014-03-271-2/+2
| | | | | | | ----- Somewhere along the line during the clang patches the version of libUEMF in inkscape acquired changes not in the upstream library. Small patch which puts them back in sync. (bzr r13222)
* Fixed typo.David Mathog2014-03-261-1/+1
| | | (bzr r13218)
* Second patch for analyzer warnings in libuemf.David Mathog2014-03-261-75/+138
| | | (bzr r13214)
* Patch for several issues in libuemf.David Mathog2014-03-251-28/+40
| | | | | | | | | ----- The patch: 1. Removes half a dozen or so code lines that didn't do anything. 2. Fixes a couple of missing tests for pointers which cannot be NULL. (Note that in many instances the pseudoobject functions in upmf.c do accept null pointers because the objects being constructed have optional parts.) 3. There was one "real" potential memory leak (line 6276 in upmf.c, numbers before the patch). I fixed the others too, but they just never happen (iconv would have to fail in some strange way.) There are no (real) memory access violations or memory leaks in any of this either in standalone libUEMF testing or in use as part of Inkscape as determined from valgrind runs. (bzr r13211)
* libUEMF update; EMF linear gradient bug fixes (bug #1263242)David Mathog2014-01-171-0/+8057
Fixed bugs: - https://launchpad.net/bugs/1263242 (bzr r12953)