Hi Tobias

> The event is: "display tiddler", although... no user interaction other "open 
> a tiddler" triggers it ...it's simply being rendered alongside a tiddler.

That sounds like you are modifying the store on widget creation or refresh. 
Widgets should not do that. Remember that the purpose of the refresh cycle is 
to synchronise the DOM with the internal tiddler store; that’s a one way 
process, with changes to the store flowing to the DOM, and not the other way.

> What happens is that I move a given popup-reveal away from the place it is 
> generated to a placeholder.

We’ve endlessly discussed this problem, and I have pointed you directly to an 
approach in the existing core code that could be adapted. It looks like you are 
still pursuing an approach based on widgets reaching around to other parts of 
the widget tree. For the reasons that we’ve discussed before, that’s not a 
viable approach.
> 
> Now, obviously, to adhere to tw architecture, I am shifting those reveals to 
> (state) tiddlers to be picked up by the placeholder listening for any changes 
> to those. There simply is NO other way to push popups away from the context 
> in which I want none of them, for reasons discussed at length on GitHub. If 
> your argument is "I should not do it" then my argument is "but I want to and 
> I have to, as there is no other way" that  I am provided with to take the 
> popup out of the flow, by the core.

I think my argument is more that perhaps you do not have a strong understanding 
of how the widget mechanism works, and so understandably are reacting to it 
with superstition!

I think you’ve got all the pieces in your hand, though. It’s just a matter of 
putting it together, and testing some of your assumptions.

Perhaps we should try to talk about the widget architecture during today’s 
hangout.

Best wishes

Jeremy.


> 
> Best wishes,
> 
> Tobias.
> 
> -- 
> 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] 
> <mailto:[email protected]>.
> To post to this group, send email to [email protected] 
> <mailto:[email protected]>.
> Visit this group at https://groups.google.com/group/tiddlywikidev 
> <https://groups.google.com/group/tiddlywikidev>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywikidev/b74e495a-d058-446c-b25e-4030c37d3171%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/tiddlywikidev/b74e495a-d058-446c-b25e-4030c37d3171%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
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 post to this group, send email to [email protected].
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/FDDDB367-208B-47DD-B123-2C15A7238A43%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to