Thanks! Yeah that was quite a minor one. Didn't bother me much. I just thought I'd report it since I found it.
On Tuesday, June 16, 2020 at 4:17:51 PM UTC+1, Saq Imtiaz wrote: > > I've pushed an update that should address that bug. I suspect we will find > a few more of these until I get the chance to do a comprehensive code > review, one is really needed after the major refactoring I did to rename > fields. > > Saq > > On Tuesday, June 16, 2020 at 4:54:02 PM UTC+2, OGNSYA wrote: >> >> I just tested again in your demo >> <https://saqimtiaz.github.io/sq-tw/streams.html> and it actually happens >> there too. >> Please see image attached. >> CTRL+down doesn't work for going from node A to A1 or from B to B1 (it >> works for all other operations). >> Let me know if you can't reproduce it, or if you want me to do any >> further tests >> >> >> On Tuesday, June 16, 2020 at 2:39:06 PM UTC+1, Saq Imtiaz wrote: >>> >>> @OGNSYA in order to try to investigate that potential bug I will need >>> either: >>> >>> - specific steps to re-create that bug in my demo >>> OR >>> - a file in which I can see that bug >>> >>> Is that problem happening in all streams? Or only in one specific >>> tiddler? >>> >>> >>> >>> On Tuesday, June 16, 2020 at 12:40:42 PM UTC+2, OGNSYA wrote: >>>> >>>> Thanks Saq. >>>> >>>> *Here's a very specific bug I'm getting *, which doesn't happen in >>>> your website (my setup is TiddlyDesktop, with Stroll). >>>> Navigating using CTRL+Down doesn't work when the next item is a child >>>> (ie. indented). >>>> Otherwise everything else works (including CTRL+Down when the next item >>>> is a parent). >>>> >>>> *And a suggestion/request*: when breaking a node in two, by pressing >>>> ENTER, could the caret (the text cursor) be moved to the *start* of >>>> the new node (instead of to the end)? To me that would be the most >>>> intuitive. It would be particularly helpful when manually breaking up >>>> longer texts. >>>> >>>> On Sunday, June 14, 2020 at 3:52:13 PM UTC+1, Saq Imtiaz wrote: >>>>> >>>>> I've pushed an update that fixes the bug with drag and drop. It's >>>>> something that crept in when I recently refactored to change field names >>>>> and plugin name. >>>>> >>>>> I've had a few things come up that will limit the time I have >>>>> available to work on this in the short term. So for now, I am focusing on >>>>> bug reports only. >>>>> >>>>> Will revisit other feedback once I am able to. In the meantime please >>>>> feel free to keep the feedback coming. >>>>> Cheers, >>>>> >>>>> Saq >>>>> >>>>> On Sunday, June 14, 2020 at 11:43:41 AM UTC+2, OGNSYA wrote: >>>>>> >>>>>> @Saq, thanks for addressing all our questions! >>>>>> >>>>>> *Single-click edit*: Got it! I didn't realize external links >>>>>> couldn't be clicked. I thought they'd behave the same as [[internal >>>>>> links]], which could be clicked in the initial (single-click) version of >>>>>> your plugin. I didn't know there was this distinction. (Maybe offer >>>>>> users a >>>>>> single-click option, which requires CTRL-click for links?) >>>>>> >>>>>> *Autocomplete*: I also ran into the autocomplete issue with >>>>>> edit-comptext. Thank you for the pull request >>>>>> >>>>>> *Direct editing*: In my previous email I suggest: *"Have you >>>>>> considered structuring it so that text can be directly edited at any >>>>>> level >>>>>> (ie., without needing to go into Edit mode)? Currently you can only edit >>>>>> child notes directly, but not the content of the node itself. This would >>>>>> make the editing experience consistent in all levels of hierarchy"* >>>>>> To be clear, I don't refer to WYSIWYG here. This would be just to >>>>>> keep the experience consistent for the end user. >>>>>> >>>>>> *Possible bug?*: I didn't see any reference to this anywhere, so I >>>>>> thought I'd mention. I'm not able to CTRL or SHIFT drag a bullet (ie., >>>>>> Copy >>>>>> or Transclude) to another tiddler (nothing happens). I can only drag it >>>>>> directly - ie., Move. >>>>>> >>>>>> Thanks! Streams is currently my favorite way to edit TW >>>>>> >>>>>> >>>>>> On Saturday, June 13, 2020 at 6:06:31 AM UTC+1, Saq Imtiaz wrote: >>>>>>> >>>>>>> Regarding title autocomplete via the edit-comptext plugin, the >>>>>>> problem is that it replaces the default editor with another. Since >>>>>>> Streams >>>>>>> also makes tweaks to the editor, it makes it difficult to combine the >>>>>>> two. >>>>>>> >>>>>>> I've re-written parts of the edit-comptext plugin to tweak the core >>>>>>> editor and add the same autocomplete features to it instead of creating >>>>>>> a >>>>>>> new editor. If these changes get merged by the developer, anyone with >>>>>>> that >>>>>>> plugin installed with automatically have title autocomplete in Streams. >>>>>>> Pull request: https://github.com/snowgoon88/TW5-extendedit/pull/17 >>>>>>> >>>>>>> If anyone is having issues with node duplication after drag and >>>>>>> drop, please ensure that you have the latest version of Streams. There >>>>>>> was >>>>>>> a bug fix related to this some days ago. >>>>>>> >>>>>>> Cheers, >>>>>>> Saq >>>>>>> >>>>>> -- 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/ae5faf5e-1206-4d68-9dcd-d408a249d327o%40googlegroups.com.