Preventing split with using styles
Posted: Thu Feb 04, 2010 4:23 pm
Hi,
Yet another query.
I have a document, which is generally to be treated as read-only, within it is a node which is to be treated as read/write.
I was originally intending to enforce this using a DocumentFilter to supress all edit events that occured out side of the target node, however I discovered the Styles property Styles.KEY_EDITABLE which I now set inside a StyleFilter; I set it to true on the target node (and all its children) and false on all other nodes. This works great apart from when using the 'split' function on the target node. 'Splitting' the target node creates another node of the same type as a sibling of the target node, essentially edting the content of the common parent node, which has been marked as readonly in the StyleFilter.
Is the intended behaviour, or is this a bug? Have you any suggestions other than goig back to my DocumentFilter plan?
Many thanks for any assistance you can provide,
Simon.
Yet another query.
I have a document, which is generally to be treated as read-only, within it is a node which is to be treated as read/write.
I was originally intending to enforce this using a DocumentFilter to supress all edit events that occured out side of the target node, however I discovered the Styles property Styles.KEY_EDITABLE which I now set inside a StyleFilter; I set it to true on the target node (and all its children) and false on all other nodes. This works great apart from when using the 'split' function on the target node. 'Splitting' the target node creates another node of the same type as a sibling of the target node, essentially edting the content of the common parent node, which has been marked as readonly in the StyleFilter.
Is the intended behaviour, or is this a bug? Have you any suggestions other than goig back to my DocumentFilter plan?
Many thanks for any assistance you can provide,
Simon.