Wrote a Boolean LPE - How to make operand path invisible?
![](https://secure.gravatar.com/avatar/89f89b6ba0370a33089a7510a98574f3.jpg?s=120&d=mm&r=g)
Dear Inkscape Developers,
I just wrote a Boolean OP LPE. It was quite easy using sp_pathvector_boolop. It works well, just I can't figure out how to make the operand path, which comes in via a OriginalPathParam, invisible.
Also I have one design question:
Some operations are symmetric, others not. Currently my interface has a bool_op enum and a swap operands bool parameter. I wonder if it would make more sense to combine these into one like:
uninion intersection this minus operand operand minus this ...
I think this would be easier to use, but it would break consistency with the existing bool op menu operations.
Best regards,
Michael
![](https://secure.gravatar.com/avatar/684824914fba488f69c20551cd5d764a.jpg?s=120&d=mm&r=g)
I think you are using the old livarot based boolops, the new boolops from Krzysztof is the future in inkscape boolops. Here is a LPE using it:
https://code.launchpad.net/~inkscape.dev/inkscape/offset
Cheers, Jabier.
El sáb, 27-02-2016 a las 15:35 +0100, Michael Soegtrop escribió:
Dear Inkscape Developers,
I just wrote a Boolean OP LPE. It was quite easy using sp_pathvector_boolop. It works well, just I can't figure out how to make the operand path, which comes in via a OriginalPathParam, invisible.
Also I have one design question:
Some operations are symmetric, others not. Currently my interface has a bool_op enum and a swap operands bool parameter. I wonder if it would make more sense to combine these into one like:
uninion intersection this minus operand operand minus this ...
I think this would be easier to use, but it would break consistency with the existing bool op menu operations.
Best regards,
Michael
Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
![](https://secure.gravatar.com/avatar/89f89b6ba0370a33089a7510a98574f3.jpg?s=120&d=mm&r=g)
Dear Jabier,
I think you are using the old livarot based boolops, the new boolops from Krzysztof is the future in inkscape boolops. Here is a LPE using it:
thanks a lot for the hint - luckily writing the bool LPE was easy enough, so I didn't spend much time. I will check out the new branch and the offset LPE.
But I think the question how one makes an operand path invisible in a LPE is independent on how the LPE computes the result. Can someone answer this question how this is done?
Best regards,
Michael
participants (2)
-
Jabiertxo Arraiza Cenoz
-
Michael Soegtrop