Dear Jabier,
thanks for your hints! I managed to set the operand path visibility in doEffect, doOnVisibilityToggled, doOnRemove.
A few questions remain:
1.) I wanted to make the operand path initially invisible in doOnApply, but there the operand path is not yet set. Is there a way to get a notification when the operand path is set? I do this now in doEffect which works, but is not terribly nice, especially together with 4.)
2.) I saw that some of your LPEs call "processObjects(LPE_VISIBILITY)" in doOnVisibilityToggled and similar function in other callbacks. What is the purpose of this? Should I do this in the boolop LPE as well?
3.) I use setExplicitlyHidden(true) to hide the operand path, but I am not sure if this is the best method. I also tried setEvaluated, but it didn't work.
4.) It is possible that the operand path is already invisible when I set the bool LPE. The bool LPE sets the operand path to visible when it is removed. It would be nicer to reset the operand paths original visibility state in this situation, but then I would have to remember it. Of cause not much of an issue, but then I should possibly also serialize it? What do you think? Just ignore this (probably would break undo), store the original state in the LPE object - lost when file is saved and reloaded or somehow serialize in SVG?
5.) Should I add on option (true by default) to make the operand path invisible?
6.) I saw the keep_paths option in removeCurrentPathEffect and also how it is implemented in your LPEs. But I couldn't find the UI for it.
Best regards,
Michael