Replies: 1 comment 5 replies
-
|
It would be no trouble to allow the registration of a new name and ImageReference instance to ImageReferenceFactory. |
Beta Was this translation helpful? Give feedback.
-
|
You mean statically in icepdf itself? Or from the outside? I'ld like to register an old, already existing filter. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, inside icepdf. I can update that class to allow you to register a new filer and assign it. And/or as you say assign it to an existing name. I can put a PR together to discuss further if you'd like? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, that would be very useful. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I think this will get the job done. Let me know what you think, #481 |
Beta Was this translation helpful? Give feedback.
-
|
Principally I think this should work. But there seems to be a problem when using -Dorg.icepdf.core.imageReference=.., and then registering this key, see my comment on the code change |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
At the momemt it is not possible to provide new ImageReferences as everything is hard-wired statically in ImageReferenceFactory. I am trying to use a Lanczos3 filter, but that seems not to be possible at the moment.
Perhaps it would be feasible to override the used ImageReferenceFactory via Java's ServiceLoader mechanisms so that library users could provide their own implementation?
Beta Was this translation helpful? Give feedback.
All reactions