Age | Commit message (Collapse) | Author | |
---|---|---|---|
2021-02-23 | Keep only referenced form fields in --pages | Jay Berkenbilt | |
2021-02-23 | Preserve form fields when splitting pages (fixes #340) | Jay Berkenbilt | |
2021-02-23 | Add methods for copying form fields | Jay Berkenbilt | |
2021-02-22 | Change from QPDF{Array,Dict}Items to aitems() and ditems() | Jay Berkenbilt | |
2021-02-21 | Add transformAnnotations and fix flattenRotations to use it | Jay Berkenbilt | |
2021-02-21 | addFormField: update cache rather than invalidating | Jay Berkenbilt | |
2021-02-18 | Add QPDFAcroFormDocumentHelper::addFormField | Jay Berkenbilt | |
2021-02-18 | Form field for non-widget just returns null | Jay Berkenbilt | |
2019-06-21 | Fix sign and conversion warnings (major) | Jay Berkenbilt | |
This makes all integer type conversions that have potential data loss explicit with calls that do range checks and raise an exception. After this commit, qpdf builds with no warnings when -Wsign-conversion -Wconversion is used with gcc or clang or when -W3 -Wd4800 is used with MSVC. This significantly reduces the likelihood of potential crashes from bogus integer values. There are some parts of the code that take int when they should take size_t or an offset. Such places would make qpdf not support files with more than 2^31 of something that usually wouldn't be so large. In the event that such a file shows up and is valid, at least qpdf would raise an error in the right spot so the issue could be legitimately addressed rather than failing in some weird way because of a silent overflow condition. | |||
2019-01-04 | Add basic appearance stream generation | Jay Berkenbilt | |
2018-06-21 | Allow setting a form field's value | Jay Berkenbilt | |
2018-06-21 | Implement helper class for interactive forms | Jay Berkenbilt | |