Works so far! ![]()
Same problem ![]()
It’s a bit crazy. If I delete the second parenthesis in the Cost(count) tag of a child node using Backspace and then reinsert it, the value of the top-level node is updated correctly.
The “bug” is aggressive and sneaky. ![]()
I forgot to do this one ![]()
Done in TestFlight 1.1 (260505.2206) it’s the only change @Oli
I was not including first line in calculation (off-by-one error)
Unfortunately, there’s still no change in the tag-filtered view. Only editing a child node updates the sum of the top-level project correctly.
I just discovered that it’s now possible in PaperTrail to archive only the completed tasks of a single subtree. That’s cool! Well done, Matt! ![]()
Thanks for the screenshot through TestFlight feedback! I’ll get on it later today
TestFlight
PaperTrail 1.1 (260506.1338)
- add: new Shortcuts intents and actions
- add: tap sync icon to find out what it means
- change: intro animation is now randomised
- fix: improved
@cost(…)calculations and parsing
TestFlight
PaperTrail 1.1 (260506.1933)
- add: Escape in Command Palette clears text filter, then dismisses on a second press
- change: Picking a command that opens a follow-up picker now resets the palette filter
- fix: Move to Project… is now undoable
- fix: Reformat Indentation is now undoable
- fix: doing more to prevent stale text after structural edits
All your bugs are belong to this release @Oli
Website updated.
Going to submit for approval and release later today, 7th May.
1.1 (260507.1619)
- fix: archive in focus mode now sends archived items to the document’s single top-level Archive section instead of creating a duplicate inside the focused project
- fix: cost and progress totals now recalculate immediately when entering or refreshing a tag/search filter, instead of waiting for the next edit
- fix: undo history is cleared when switching between focus, filter, or no-filter views to prevent edits being replayed against the wrong document state
- change: filtered views now show visible-aware totals only on screen; the underlying document always holds full-document-correct totals, so iCloud sync and autosave never see stale partial sums
Heureka! You did it!
![]()
I think this was a hard week for you! Love this feature!
Oli
I need a holiday. If we don’t find any bugs I will submit it in a few hours.
TestFlight
PaperTrail 1.1 (260507.1857)
- fix: scrolling the document no longer snaps back to the cursor position
(thanks @bkmj.hughes!)
Two things I have spotted:
- The toggle line type button on the toolbet doesn’t seem to do anything when a task line has started but there is not yet text content other than spaces. In other words for a line to be “- “ I would expect to lose the hyphen and go to a note, but nothing happens with taps.
- When hitting return for a new line from a task line, I would expect to get a new task line. I wouldn’t mind if this happens from a Project line, but it seems incorrect that PT defaults a new line to a task line after a note. In many cases I am trying to add more notes. Taskpaper only defaults to a new task line when following another task. This default works better fro me at least.
BTW, I have also had intermittent issues with the shortcuts for both most recent and a named doc opening to a white screen. I have not been able to reproduce and the screen shot is just a white screen, so there is not much I can say to help track that down.
Tim
Hi @tlrand
I added some extra checking and better failure state to Shortcuts in 1.1 (260506.1338) so if you can repro in a newer version than that I would like to know more.
Will do the other two today!
Decided to take my time on new assets for the store.
TestFlight
PaperTrail 1.1 (260508.1716)
- add: pressing return on a note line now inserts another note (instead of a task)
- change: renamed “Fold Marker” colour setting to “Accent”
- change: accent colour now applies to the fold markers, toolbar, window tint, etc
- fix: new tasks inserted from the toolbar in a tag-filtered view now carry the filter tag so they stay visible
If I force quit the PT, most of the time the Open Document shortcut to a named document will fail. The same shortcut works if PT in most other situations. Most Recent Document shortcut is more reliable across the board, but I have seen the error with it.
The flow to get to error is:
- Hit shortcut
- See splash screen / file view
- Get sent to white screen
- Force quit to get out
Oddly after this the shortcut then usually works.
Will try to repro this one. I am doing some strange pass the parcel and morphing of data to get this to work but nothing unapproved or sketchy.
Edit: have reproduced it ![]()
@tlrand how are you doing Open Recent?
I now have it working from a Shortcut widget containing PaperTrail’s Open Recent.
…but not from Spotlight “found doc” search result. So I’m thinking I’ll stop feeding those results to Spotlight.
Edit: ripped it out and then had an idea so put it back in and now both work!
I created a shortcut and then added it to my homescreen. I also did the same for my main ToDo doc. I am still getting inconsistent behavior for both of these when launching from the home screen.
EDIT: getting the same behavior from launching the shortcut directly.
So I could reproduce it and now I can’t, which means I’m almost confident it is fixed.
If it’s not too much bother please delete the app, restart your device, and then reinstall the app before testing the document open again @tlrand maybe do that if it’s still broken LOL
TestFlight
PaperTrail 1.1 (260509.2213)
- add: reveal Welcome in the document browser’s Recents tab on first ever launch
- add: Welcome links onward to Guide via a relative Markdown link
- change: Guide expanded with sections on features added since 1.0
- fix: reworked document opening from cold start so it works reliably from Spotlight and Shortcut widget
- fix: New Project no longer re-parents existing children — it is inserted after the whole current branch, even when triggered from a deep child line
- fix: pressing Return on an empty bullet inside a focused subtree keeps the resulting blank line inside the focused root
- fix: email addresses such as
bugs@example.comare no longer parsed, styled, or matched as@exampletags - chore: regression tests for empty-bullet behaviour in focus mode, New Project insertion, and tag/email parsing