Seems you´re using Inkscape 1.x. Since its release this behaviour changed: previously we just needed for instance a rectangle and a text and Path->difference punched the text out of the rectangle.
Now everything needs to be a path. But Text converted to Path is a group in a first instance - so you´ll need to ungroup and combine before you can use Path-Difference. It´s the pest - even worse: a single stroke becomes a group now - for no (I mean absolut no logical/understandable) reason. If one find this helpful I´d like to know why.
even worse: a single stroke becomes a group now - for no (I mean absolut no logical/understandable) reason
If you mean using Stroke to Path on a single stroke, we've discussed this one before. If you have a stroke with no fill, and no markers then the behaviour is as before: no group. If you have a fill or markers, however, you get a group with each part of your shape as a separate element within it. This is actually just an extension of the behaviour from 0.92, where Inkscape already created a group if there were markers set - 1.0 just extends that to the fill as well.
As for the reason: I think it's to avoid confusing new users when parts of their path vanish (after all, it's called 'Stroke to path', not 'Stroke to path and forget all the other properties I set'. There's a good argument that choosing either of the '... to Path' entries should convert the objects but not change their appearance; that's how Inkscape now behaves.
It's nice how you explain and justify the new code - but in my eyes the new implementation is far away from any everyday use and a big nuisance. So is the new text/boolean handling; absolutely useless and complicating the simplest tasks.
As long and as much as I've been using Inkscape since 2004, I can't use it with these behaviours any longer and will return to my old version of 2015 and discontinue support for 1.0 from now on.
I agree entirely that the current text/boolean handling is a terrible step backwards. But I'm not seeing the behaviour you are when using Stroke to Path on a path with no fill or markers:
Based on the release notes, I believe that what I'm seeing is the intended behaviour, which raises a question about why your installation behaves differently.
I don´t have AI nor Corel but Affinity (all 3) from day 1 - and there it´s: "Layer->Expand stroke" - done - no stupid group - no hidden path - just a color filled shape.
Can you confirm if that's the case PP? If that's the future behaviour of the program then I agree it's a step backwards - but there might still be an opportunity to get it reverted before there's a formal release.
Beginners' Questions Problems using the intersection tool with text.
Inkscape.org
Hi guys, when I want to use the intersection tool to divide the text, it turns out that it doesn't work for me.
I will attach a video of the problem.
Seems you´re using Inkscape 1.x. Since its release this behaviour changed: previously we just needed for instance a rectangle and a text and Path->difference punched the text out of the rectangle.
Now everything needs to be a path. But Text converted to Path is a group in a first instance - so you´ll need to ungroup and combine before you can use Path-Difference. It´s the pest - even worse: a single stroke becomes a group now - for no (I mean absolut no logical/understandable) reason. If one find this helpful I´d like to know why.
If you mean using Stroke to Path on a single stroke, we've discussed this one before. If you have a stroke with no fill, and no markers then the behaviour is as before: no group. If you have a fill or markers, however, you get a group with each part of your shape as a separate element within it. This is actually just an extension of the behaviour from 0.92, where Inkscape already created a group if there were markers set - 1.0 just extends that to the fill as well.
As for the reason: I think it's to avoid confusing new users when parts of their path vanish (after all, it's called 'Stroke to path', not 'Stroke to path and forget all the other properties I set'. There's a good argument that choosing either of the '... to Path' entries should convert the objects but not change their appearance; that's how Inkscape now behaves.
It's nice how you explain and justify the new code - but in my eyes the new implementation is far away from any everyday use and a big nuisance. So is the new text/boolean handling; absolutely useless and complicating the simplest tasks.
As long and as much as I've been using Inkscape since 2004, I can't use it with these behaviours any longer and will return to my old version of 2015 and discontinue support for 1.0 from now on.
I agree entirely that the current text/boolean handling is a terrible step backwards. But I'm not seeing the behaviour you are when using Stroke to Path on a path with no fill or markers:
Based on the release notes, I believe that what I'm seeing is the intended behaviour, which raises a question about why your installation behaves differently.
Did a quick test in Windows 10. Seems like Pixelpest is using 1.1 (Master) and Xav is using 1.0.
There is a difference in behaviour between these two versions.
PIxelPest is on a Mac, IIRC.
Text booleans were better in .92xx, IMO
The behavior of Stroke to Path is now similar to other vector programs like Ai, Corel, Affinity.
I don´t have AI nor Corel but Affinity (all 3) from day 1 - and there it´s: "Layer->Expand stroke" - done - no stupid group - no hidden path - just a color filled shape.
I can confirm this, both for Affinity and Corel.
I've just tried 1.0 on a Mac and see the same behaviour as on my Linux box.
Can you confirm if that's the case PP? If that's the future behaviour of the program then I agree it's a step backwards - but there might still be an opportunity to get it reverted before there's a formal release.
Not grouped, but two new objects. Earlier Inkscape behavior: the stroke became the object and the fill went away.
Not seeing the same single line behavior as PP in v1.0 under Mint. (No group, single filled object.)