Birthe,

Seriously, I have attempted to a number of times, even create minimal test 
case. But have failed. It is easy to get caught in complex loops and twists 
where the slightest change breaks it. 

I will have another go.

Regards
Tony

On Wednesday, October 9, 2019 at 12:36:19 PM UTC+11, Birthe C wrote:
>
> Hi Tony,
> You seem to have a lot of exiting things going on. Need and curiosity is 
> getting the best of me when reading about it. You know curiosity killed the 
> cat...and (Do I need to say more...).
>
> I understand that complexity and lack of time can make it difficult to 
> publish the all shining and glamorous solution, but is it not possible in a 
> wiki to show us some examples and list the needed tiddlers. That would, I 
> am sure, give you some feedback and even suggestions to make it even 
> better. Your choice of course.
>
> All respect for your work,
> Birthe
>
> onsdag den 9. oktober 2019 kl. 00.29.40 UTC+2 skrev TonyM:
>>
>> Hubert,
>>
>> The lag often occurs when you are editing text or fields in the same or 
>> another tiddler that is being rendered in front of your eyes.
>>
>> If you can edit values in a tiddler that is not visible this can be 
>> eliminated. 
>>
>> There are workarounds, and I have built these into a number of 
>> sophisticated solutions I have built (not yet published), but while I can 
>> hint at how I have done it, I can not possibly document this, because it is 
>> annoyingly complex and self referential (that being the problem here).
>>
>>
>>    - Place the edit text in a macro in another tiddler that references 
>>    the current tiddler
>>    - Use a View template to overlay the current tiddler with the edit 
>>    text macros
>>    - something else that is not quite so obvious.
>>
>> I have on a number of occasions tried to communicate a need to remedy 
>> this by providing a mechanism to reduce the complexity of this practice. I 
>> almost always get negative technical responses rather than positive 
>> creative solutions. Since I have done it, I know it is possible and 
>> workable, that is, it is technically possible, but due to its complexity 
>> and my current knowledge, I am not yet ready to publish my solution (I have 
>> tried) let alone show how a better mechanism could be designed. It is 
>> technically feasible, it is one of tiddlywikis worst features, it needs a 
>> solution.
>>
>> Regards
>> Tony
>>
>

-- 
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/f4c48711-ebd9-458b-90fb-95c39823737e%40googlegroups.com.

Reply via email to