[This is beyond me but anyway]

I'm thinking each "special rendering" such as a list, a transclusions etc 
will have to be identified as one unit when clicked on. So even if the 
caret position in view mode is calculated, this position - say 200 - could 
be after a few transclusions meaning that it in the code is really only 
position 20. To know that 180 has to be deducted, means one has to identify 
and calculate the character lengths of those transclusions. Including 
possible transclusions inside those transclusions, etc.

But maybe one can go the other way; start by peeking into the wikitext in 
the editor. There could be a "faux caret character" (for lack of better 
term) set inside the wikitext that shows up in view mode. If this caret 
could be steered, e.g via arrow keys (to type/delete it as it "steps") one 
could manually move it to where one wants to edit and "click enter" to 
switch to edit view - and with a positioned caret. Buuuut positioning the 
faux caret like that sounds like more work than just entering edit mode and 
searching up the correct position. So steering the faux caret would need a 
better way, perhaps ideally by having it "follow the mouse". And that's 
where I've twaddled enough ;-)

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" 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/tiddlywikidev/14073e17-666f-469d-b351-e230225782a7o%40googlegroups.com.

Reply via email to