I could not get the linked offset directly connected to the text to work as stated in the tutorial. I ended up using duplicates of the text. This is not ideal because each layer would have to be changed individually in order to change the text. Other posts online suggest converting the text object to a path. This is makes the linked offset function as in the tutorial but then the base text is no longer text and therefor can't easily be edited, which voids the major benefit of linked offsets vs duplicates to begin with. I have also tried ungrouping the text selection, then combining the paths, and this does not seem to improve the situation. I fear I may be overlooking something.
Unfortunately it does require delving into the XML editor, so if you're not comfortable with doing that, the solution may not help. There is an open bug about this regression, but no sign of a fix being committed yet.
I was trying to follow this tutorial on creating a chrome text effect:
http://web.archive.org/web/20130308003839/http://troy-sobotka.blogspot.com/2007/11/inkscape-tutorial-1-chrome-effect.html
I could not get the linked offset directly connected to the text to work as stated in the tutorial. I ended up using duplicates of the text. This is not ideal because each layer would have to be changed individually in order to change the text. Other posts online suggest converting the text object to a path. This is makes the linked offset function as in the tutorial but then the base text is no longer text and therefor can't easily be edited, which voids the major benefit of linked offsets vs duplicates to begin with. I have also tried ungrouping the text selection, then combining the paths, and this does not seem to improve the situation. I fear I may be overlooking something.
Thanks for helping.
2007?
Ok - try the following: Type text - go Path->Object-to-Path - Object->Ungroup - then Path->Combine - now the linked Offset should work.
It's a regression in v1.0. There is a workaround though:
https://inkscape.org/forums/tutorials/text-and-path-regressions-in-10-with-workarounds/
Unfortunately it does require delving into the XML editor, so if you're not comfortable with doing that, the solution may not help. There is an open bug about this regression, but no sign of a fix being committed yet.