![scribus link text frames scribus link text frames](https://i.pinimg.com/originals/c4/c6/40/c4c6400a794a81ea3aad8743c790de71.jpg)
ScCore->primaryMainWindow()->slotDocCh() +++ Scribus/scribus/plugins/scriptplugin/cmdtext.cpp (working -1329,7 +1329,8 *scribus_unlinktextframes(PyObject* /* self */, PyObject* args) Scribus/scribus/plugins/scriptplugin/cmdtext.cpp (revision 25083) Index: Scribus/scribus/plugins/scriptplugin/cmdtext.cpp Unlink_and_cut_text.txt (2,327 bytes) $ svn diff Thanks for helping me with my first contribution. In other words, it seems that the chain 'a->b->c->d' becomes the two chains 'a->b' and 'c->d' when you unlinkTextFrames(c). Whether I unlink via the GUI or via Scripter, and whether I cut text or not, it seems that breaking a link just separates the chain into two chains. The documentation for unlinkTextFrames() states, "If the frame was in the middle of a chain, the previous and next frames will be connected, eg 'a->b->c' becomes 'a->c' when you unlinkTextFrames(b)." However, I don't see that behavior. above, since, for example, the current function isTextOverflowing() also uses a boolean, but that function is excluded from api_textitem.cpp.ģ. The attached adds a function with an optional bool. cmdtext.cpp currently has almost no functions with optional arguments other than the optional object name.
Scribus link text frames how to#
api_textitem.cpp also contains a reference to unlinkTextFrames(), but I don't see how to add a boolean arg to that. If set the new flag mirrors "Item | Text Frame Links | Unlink Text Frames and Cut Text" the same way that the function without the flag mirrors "Item | Text Frame Links | Unlink Text Frames."ġ. Scripter should have some analog to the GUI option "Item | Text Frame Links | Unlink Text Frames and Cut Text."Īttached is a patch to add an optional "cut_text" boolean flag to the current unlinkTextFrames() function. 0016784: Support "Unlink Text Frames and Cut Text"