On Thursday, June 11, 2020 at 5:58:32 PM UTC+2, Raghu Veer S wrote: > > Btw here is another thing I observed, I thought it was counter-intuitive > to what I was expecting to happen, so just wanted to know if this was the > desired effect: >
Essentially, yes. The mismatch with expectations is due to expecting the behavior one would expect in say MS Word or a WYSIWYG editor. Pressing Enter does not "push the parent node down". Rather what is happening here is that: - since the caret is not at the end of the text, this is interpreted as an attempt to split the text into two nodes. - everything after the caret is moved to a new node created after the current one, children stay with the current node. - this was in response to a user request to be able to press enter in the middle of a chunk of text and divide it into separate nodes. If it proves counter-intuitive, it might be dropped. It may also be possible to consider having the caret at the start of the text as a special use case with different handling similar to what you expected, i.e. insert a new node before the current one. However before adding more complexity I want to make sure this behavior dependent on caret position is going to stable enough to keep this feature in. Apart from this exceptional scenario when the caret is not at the end of the text, the behavior in general when pressing enter is that the node being edited is saved, and a new subsequent node is created. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8444e297-c0f4-474a-93bf-67fab3882172o%40googlegroups.com.
