Many Thanks @mwra. That lets me do exactly what I want, to view the text of one note conventionally, and write a summary of that text in a text window of another note.
Unfortunately, after adding a few words of text in the text window, Tinderbox repeatedly closes and I get an Apple crash report. I have managed to replicate this in a new Tinderbox doc with two notes with a few paragraphs in each, and it may be associated with creating bullet points and adding further text to these.
However I can work with a less elegant solutions, such as summarising text in Apple Notes and pasting that into the required note later.
Sorry to hear that. Do please make sure to get any crash logs and steps for repetition direct to tinderbox@eastgate.com as such info is important to help the developer find the cause.
I have 4 notes selected, one of which āAnother Noteā is also open as a text window. If I edit in the latter window, the composite text in the text pane is not updated, but, if I click the tab (blue area above the view pane) this refreshes both panes and the edit shows up in the composite.
But, still a bit unclear as your edit configuration. In your demo TBX above (up thread) I donāt see any bullets in the $Text.
Might it be a good idea at this point to send the discussion of Text Window to its own thread? People might have more to contribute about Tinderbox for longform writingā¦
Thanks @mwra, and thanks also for moving the thread, I was thinking the same about contaminating the previous thread, I wasnāt expecting an issue to take up space.
Re your question, I was selecting bullet point entry via the ruler. However bullet points seem to be a red herring; I found I can get the crash, in a new document with one note, with vanilla text entry into the text window, after about 100 characters at most. Iāve sent the crash reports and files to @eastgate. The challenge is that he canāt replicate it (even with the sent file) and unless someone else encounters the problem Iām not sure how this can be furthered.
FWIW, I canāt replicate it either. Certainly it is not as simple a trigger as typing in the $Text of a stand-alone window. This suggests either we donāt have the causal steps accurately enough or something else running on your Mac is unexpectedly a factor in this. No fault on your part here. The challenge at this point is to replicate your issue in the same software on a different computer.
Iāve tried generating the effect in both the v10.0.2b693 public release and the most recent beta (though the latter hasnāt yet addressed this as we donāt know the cause!). Both have no problem with text entry. I also have TextExpander running (following the input key stream) so Iād strike that out as a possible factor.
If I understand you correctly, if you make a new TBX file, add a single note and start typing, after c.100 characters of input the app crashes? If not, what else has to be present (extra notes, different focus/selection, etc.)? If there are multiple windows we need to know what type they are.
Sorry for all the questions. Itās a matter of narrowing down the causal context, which may be accidental to your maaer of use but may not be so used by others. Murphyās Law. It would appear the crash logs also arenāt (again, not anyoneās fault!) giving the developer any clue as to the context of the crash.
to explore this, Iāve just shut down my Mac, restarted, opened Tinderbox only, added a first note to the default Tinderbox āUntitledā window, called it āTestā and then opened a Text Window and started typing. This time I got about 150 characters entered before Tinderbox crashed.
OK, the is definitely not repeatable here. This would suggest (not proof!) that the issue is something special to your Macās set-up, as opposed to a Macs in general. If you have any utilities that are monitoring the overall text input to you Mac it is worth quitting those sand seeing if there is any difference.
I tried turning off anything that might be jumping in and causing a problem, even when no other apps were running. My intial focus was Devonthinkās menu bar items, which keeps going even when Devonthink isnāt running. I also tried turning off every other menu bar item that wasnāt part of the standard Apple installation (iMenus etc., though I couldnāt see why that would intefere.
I then noticed that Apple Shortcuts had become a menu item with a Tinderbox shortcut that I hadnāt intentionallly put there, although it was stalling because I hadnāt given permissions
Then I also noticed, in the Tinderbox Text window, that I started getting unpredictable behaviour with the cursor suddenly jumping back to the previous location, and substituting the text that I had just written with some half formed word, as I wrote, with no other feedback.
That made me suspect Predictive text. Going to System Settings I searched for āpredictiveā and in the āKeyboardā sub-dialogue I saw that all four options, from Correct spelling automatically to āAdd full stop with double spaceā were on. I turned them off, so:
Since then I havenāt had a crash, nor any other unexpected behavioiur, when using the Text Window.
If anybody fancies experimenting with turning these four options on, and seeing if they get crashes when using Tinderboxās Text Window that would be interesting and helpful, but not vital.
Hopefully I wonāt be coming back on and saying the problem is still there after all!
The inline predictive text does seem to cause an issue, though I use it very rarely. I think it was new to Sequoia and arrived with a default āonā setting. But if I uses it and see crashes, Iāll likely turn it off. not least, it only knows/suggests school-level vocabulary so fails against my English ā¦ whose vocabulary has expanded since schooling back in a previous millennium.
Another thing that sneaked in without my really noticing. Iāve turned it off now. Apart from it being limited, I think it is also more American than I am (see āsneakedā).
I fear that is more due to the āavailableā (i.e. borrowed/stolen) data used for training than overt parochialism. AmE is probably the largest corpus is recent (i.e. likely digital) English.
Iād love to see the continuation if trained on Elizabethan, Georgian or late Victorian (British) English.
Huh. I wonder if this has been the source of my crashes as well. I havenāt been doing massive typing sprees in recent(ish) intermittent usage but Iāve definitely noticed a lot of crashing. Not just at a hundred words. Iāllā¦ go turn off those predictive toggles and see if it still happens, I guess.
I have done so! Although I didnāt get any more crashes after turning off prediction stuff, I also didnāt get any more crashes after turning prediction stuff back on, so Iām not entirely sure thereās a connection. But from now on out I will faithfully send crash logsā¦ and leave the prediction stuff on, just 'cause Iām curious.
