Hi Mohammad It seems that in presentation mode you’re using CSS to expand tiddlers in the story river so that they fill the whole browser window. The complications you’re running into are perhaps primarily because the story river CSS is subtly different in zoomin story view, but in general because it is fiddly to try to change the story river mechanism to do something that it wasn’t designed for.
I wonder if it might be worth exploring a different approach: decoupling the slide display mechanism from the story river mechanism. You could have a $:/tags/PageTemplate tiddler that displays when the presentation mode is engaged, and uses CSS to make itself cover the window. Then, rather than a story list, you can make your own navigation mechanism using a single tiddler to identify the title of the currently viewed slide. Modifying that single tiddler will be simpler than modifying the story river. Users would still be able to display individual slides as separate tiddlers in the story river if they needed to see them side by side etc. Best wishes Jeremy. > On 22 Jan 2020, at 03:24, Mohammad <[email protected]> wrote: > > Hi Mario > Thank you very much for all your clarifications! > This make things more understandable. > > On Wednesday, January 22, 2020 at 12:59:39 AM UTC+3:30, PMario wrote: > On Tuesday, January 21, 2020 at 7:29:15 PM UTC+1, Mohammad wrote: > ... > Well, this is kind of reverse engineering! > > You are absolutely right. ... But TW has an "organically" grown UI, which was > mainly driven by user demand. > > At the very early (alpha) days TW suffered from so-called "divitis". .. That > means way too many nested div-elements. ... The whole system was in constant > flux. > > We reduced most of the redundant stuff, but some "wrappers" have escaped and > made it to the V 5.1.0. Since 5.1.0 backwards compatibility is one of TWs > major goals. Which is good, but also causes some headache in combination with > the existing CSS. > > Some "wrappers" are still there. eg: If a tiddler designed for the sidebar is > shown in the main story river, it looks and sometimes behaves different. > That's the way it is. > > That's why, browser dev-tools are our best friends ;) > > BUT all in all, we have a functional, stable and mainly backwards compatible > UI. That's worth something q:-) > > I will dive and try to find how a tiddler can occupy the whole screen in solo > story view! > I did the same when I developed Tiddlyshow which uses zoomin > > have fun! > mario > > > Cheers > Mohammad > > -- > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/3fed0076-9aca-4425-8ab3-a9cd00db29d3%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/3fed0076-9aca-4425-8ab3-a9cd00db29d3%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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/3A23ED44-215E-4A53-AED7-23ACDF50B3C5%40gmail.com.
