Sounds like an interesting solution, @Maki, to a problem i also have, i.e. : How to get around the limitations of this mobile platform -Quine2 on iOS- to leverage the full power of TW+Streams application.
Specifically: context menus requiring right-click (or control-click on Mac w/ 1 button mouse), i have not yet found a way to access on mobile. Does this shift+z solution of yours address that specific problem? If so, then: Can you tell us how that solution can be most easily installed on a standard TW instance? I tried to find it on your site <http://makiaea.org/>, but couldn't manage to navigate the Chinese character set. /walt On Sunday, August 8, 2021 at 7:36:43 AM UTC+1 ma...@makiaea.org wrote: > just jumping in to share my experience with streams on mobile. > > i'm on an old iphone and i basically have tiddlywiki open all day using > quine2. been using saq's streams lately with a tweaked shortcut to save > tiddler+stream, shift+z. works really well for quick notetaking on ios. > have customised the layout quite a bit ( http://makiaea.org ) for mobile > but the heavy lifting is from streams and shift+z. > > maybe there is an easier way but shift+z is not a key i use often and it's > easily available on the ios touch keyboard. not for everybody, but it made > it much easier (personally) to use streams. hope this helps! > > sorry for short message, have to send before gg eats my post > On Friday, August 6, 2021 at 7:16:26 AM UTC+1 saq.i...@gmail.com wrote: > >> Hi Mark, >> >> That sounds very disconcerting. Please do let me know if you discover a >> way to recreate the problem. >> It seems particularly odd that the configuration tiddlers were affected >> as neither the text splitting code nor relink should be touching those. >> >> There have been problems in the past where splitting longer text into >> nodes using alt+enter and having the configuration for new nodes to use the >> unusedtitle macro resulted in some nodes not being visible in the Stream. I >> have attempted to fix that but it is an area that needs further attention >> and upcoming changes in TW 5.2.0 will help clean it up. However, even if >> that bug is resurfacing, it would not explain the issue with configuration >> tiddlers. I will review the code for splitting longer text into multiple >> tiddlers once more. >> >> Saq >> >> >> On Friday, August 6, 2021 at 3:55:15 AM UTC+2 Mark S. wrote: >> >>> There might be a problem with the text splitter, or maybe relink or >>> relink with the text splitter. I was looking at my sample Streams file and >>> found I couldn't see any of the notes I had made previously. But all the >>> tiddlers were still in the TW. After some examination, I found that several >>> Streams configuration tiddlers had swapped titles (or swapped contents, >>> depending on your perspective) There were at least a half dozen such >>> configuration tiddlers. So Maximum node width >>> <#m_-5158747867511053490_m_7186877098821485007_m_5305531832700594985_%24%3A%2Fconfig%2Fsq%2Fstreams%2Fnode-max-width> >>> had \n\n in it and so forth. >>> >>> I don't see how that could have happened without code that actually >>> changes things. So either relink got something messed up, or the text >>> splitter moved titles around. None of the code I've added (my own search >>> section) changes tiddler's names or contents. The only other code I've used >>> is the command palette, which I've now disabled. >>> >>> I know this isn't very helpful, but in case someone else encounters >>> similar problems it may help narrow things down. >>> >>> -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2574c8a1-7aeb-45ae-bc94-1fda316ad4c4n%40googlegroups.com.
