Coule the edit-in-current re-render issue be solved w built in temp tid?

[Mat]

Probably already dismissed as it seems a bit too obvious but anyway;

Could the problem with EditTextWidget re-rendering when attempting to edit the current tiddler be solved by having it fall back on a temp tid that is really what is edited? When unfocused, the tempvalue is transferred to the current and the temptid is deleted. This would take place behind the scenes.

<:-)

[PMario]

Hi Mat,

There are already some PRs, that completely fix the problem. ... They are not merged yet. or have been closed without merging. Some may still be open. I've lost the overview about this one.

-m

[Mat]

Thanks PMario. I don't find anything about it on gh (likely because I don't quite know what to search for) but if PRs have, as you say, been closed without merging - doesn't that mean they have been insufficient? Do you have any opinion on my proposal here? Does it make sense or is it bad?

<:-)

[TonyM]

Mat

I already have practical work arounds I can share. My key wiki runs on this edit in viewmode. I can in fact edit any field in the current tiddler this way.

However it takes quite a cognitive load to generalise it.

What you are suggesting is similar to the current edit mode and draft tiddlers.

Of course remember it is easy to edit one tiddler from another. So you can build a special tiddler that lets you select the tiddler to edit from within the special tiddler.

The difficulty of doing this with current methods and because this is a common request is in my view a reason we need a better solution. Even if it can be simplified a little it would help.

Regards
Tony

[PMario]

Hi,

Wiki can be tested at: http://refocusing-inputs.tiddlyspot.com/

gh is: https://github.com/Jermolene/TiddlyWiki5/pull/3747 and those linked in the first post

-m

[Mat]

@Tony, thanks, my proposal is merely for the sake of solving it once and for all in the core but if PMario says there are "real" solutions then that's probably better than work arounds. BTW, I've tried to reach you privately but not sure it's coming through. How should I reach you?

@PMario thanks for the links. Yes a brief testing of it does seem to work. I'll repeat your question to BTC there about why he closed it.

<:-)

[Jeremy Ruston]

There are already some PRs, that completely fix the problem. ... They are not merged yet. or have been closed without merging. Some may still be open. I've lost the

overview about this one. 

Just to clarify, BurningTreeC has been the one experimenting in this area, and has indeed produced some PRs for discussion. We've only closed them because we're not satisfied. We do now think we have figured out the basis. for a solution, but it has not been implemented yet.

Best wishes

Jeremy

-m

--
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 tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/8a4ae98e-9a88-474d-ab64-e1578cdb6d36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mat]

Jeremy Ruston wrote:

[...]We do now think we have figured out the basis. for a solution, but it has not been implemented yet.

Great.

Thread closed... if it were possible.

<:-)