Scroll via separate window works - and not :-/

[Mat]

This demo shows the problem: http://winproblem.tiddlyspot.com/

Basically:

Using $action-navigate works in a separate window...

IF the window was opened via the tiddler tool button "Open in new window"...

but NOT if the window was opened via another button.

...but both ways use the same method, i.e tm-open-window

What am I missing?

Thank you!

<:-)

[Eric Shulman]

On Monday, July 27, 2020 at 6:28:55 AM UTC-7, Mat wrote:

This demo shows the problem: http://winproblem.tiddlyspot.com/

Using $action-navigate works in a separate window...

IF the window was opened via the tiddler tool button "Open in new window"...

but NOT if the window was opened via another button.

...but both ways use the same method, i.e tm-open-window

What am I missing?

The one *difference* between the TWCore "open in new window" button

and your button is that your button includes a template="tid" parameter:

   <$action-sendmessage
      $message="tm-open-window"
      $param="""tid"""
      template="tid"
   />

If you remove this parameter from your $action-sendmessage,

then the button works the same in both cases.

-e

[Mat]

@Eric, thank you for taking a look!

template="tid" parameter .... 

If you remove this parameter from your $action-sendmessage,

then the button works the same in both cases.

OK, I updated the demo http://winproblem.tiddlyspot.com/  to make the template parameter not use the "tid" itself, but a separate template - because I do need to use a template in my real case. Shouldn't it work with the template parameter?

<:-)

[Saq Imtiaz]

Your template is missing a navigator widget to handle the tm-navigate message.

The default template includes a navigator widget.

[Mat]

Saq, thanks for reply

Your template is missing a navigator widget to handle the tm-navigate message.

The default template includes a navigator widget.

Which/where is actually "the default template" you talk about so I can investigate it? (The tm-open-window call in $:/core/ui/Buttons/open-window has no template attribute at all.)

Thank you.

<:-)

[Saq Imtiaz]

I don't remember off the top of my head the exact shadow tiddler name but it would be under core/templates.

Nothing special in it though, just wrap a navigator widget around your template and it should do what you want.

[Mat]

@Saq

Well, it works - that was certainly magical! I found a navigator widget in the pagetemplate just to get a clue what to do with it, because the docs definitely are not clear but I took your word for it and just naively threw one in, no parameters or anything, and... voila!

Thank you.

<:-)

[TW Tones]

Mat,

If you think about it any link clicked in the story or side bar navigates to and adds the tiddler in the link to the story. Thus the relevant navigator widget wraps the page template, because within that, the story is "enumerated". And any click on a link, therein, needs to be honoured.

I use open in new window such as opening the TOC tiddler, to remote control the story. 

However if your new window has a list widget that lists the links to tiddlers you can add your own history list or wrap it in a new navigator widget to get different results. 

Theoretically we could do this to get a remote control for the second column in stroll. 

Mario and I have discussed this in the past but its an open challenge to provide a more robust story management, such that you can save, switch, capture and restore stories and any list (field) for that matter. I for one would like to select a "project", which would restore a story list for that project, keep working on the project, then save the current story to that project and return to the default story or that of another project.

Similarly if we could build tools to swap, copy, share and change lists, we would add a new level of interaction to tiddlywiki.

I mention this because grasping the navigator widget and list widget are the two key methods.

Regards

TW Tones

[Mat]

 TW Tones, thanks for your insights on the navigator widget.

Regarding:

[...] a more robust story management, such that you can save, switch, capture and restore stories and any list (field) for that matter. I for one would like to select a "project", which would restore a story list for that project, keep working on the project, then save the current story to that project and return to the default story or that of another project.

Isn't that pretty simple to make? Just save the {{$:/StoryList!!list}} by appending it to some "list of storylists" and, for a UI, use a selectwidget to switch among them. Not sure what it has to do with the navigatorwidget, but anyway.

Similarly if we could build tools to swap, copy, share and change lists, we would add a new level of interaction to tiddlywiki.

Hm, just send permalinks? 

Regardless, it seems this doesn't really have to do with the 

[TW Tones]

Mat

The way I understand it the way we would do this is to change the settings with the navigator widget in the same way you need to consider for the OT.

Yes in many ways it is simple to do as I suggested but somtimes getting it to be really simple is quite complex ;)

regards
TW Tones