Open stelfrich opened 8 years ago
The general idea is for the burnIn
op to solve this: you can call burnIn
and it will "copy as needed". The View
marker interface, and its proper propagation, is a necessity for this to work well.
Thanks for the heads up @ctrueden. I wasn't really aware of the gory details of the topic (btw thanks for the great recap).
The
View
marker interface, and its proper propagation, is a necessity for this to work well.
You are talking about the output of an op implementing the View
interface, right?
You are talking about the output of an op implementing the View interface, right?
Correct. Since your new scaleView
op returns the result of a Views
method call, this should already be the case, fortunately.
@ctrueden in a discussion about #433:
Most of the ops in the
TransformNamespace
are nowadays wrappers forViews.*
.Ops.Transform.Scale
implemented a scaling operation that copied pixel-wise. With chaining it is possible to get a copy of the output of anyViews
-based transform anyway. But should we consider exposing convenience methods forInput > Transform > Copy = Output
?