Is no news good news @cboone @Gorgonzola? My hardware test with your notes was successful.
Let me know and I’ll ship 1.2, I’m eager to get it approved before WWDC begins.
Sorry haven’t made it testing yet. Quick test shows that visual glitches are mostly gone, but there’s still significant lag on my device when editing. See video:
1 Like
Hmm. The second most recent version was working pretty well. I hadn’t had a chance to try it out with my long file before I updated to the most recent. Autocomplete was working fine. The only obvious bug was the seemingly random (presumably not, but I didn’t have a chance to try to figure out the pattern) first letter of the line capitalization. I upgraded to the latest build just now, and I can’t open any of my files! Tapping on a file produces a little shimmy in the iCloud Drive panel, as if it was doing something, but the file never loads. Nothing happens.
OK! Thanks, Gorgonzola, I really appreciate the videos as it saves me so much time and energy reproducing when I can just click and see what is going on.
I found another slow bit in my recalc code in certain extreme scenarios. Then I kept pushing and found some more opportunities for improvement. My goodness, some of my code from 1y ago is…not great.
TestFlight
But more perf updates coming if I can find time tomorrow
2 Likes
Thanks, that one still on my list.
That is iCloud. A device reboot or wifi toggle or some such will usually spur it into action.
FWIW the app flow is app launch (PaperTrail), Document Picker (iOS), document opens for editing (back into PaperTrail). It’s an odd back and forth blurred ownership setup, but it’s the way Apple has structured DocumentGroup apps on iOS: the reason they give is for security. It also made opening most recent file a real headache, but I did manage that through a game of pass the messaging parcel.
Got it. What’s the fix / workaround for the iCloud problem?
The workaround is not PaperTrail specific, but more general for your device or setup. First I would check iCloud settings for any errors. Personally, I would then do device reboot and see. Some people suggest a force restart!
The issue is that sometimes the background daemon responsible for file coordination (fileproviderd) just hangs. Thanks iOS!
OK, realistically I am going to be out for the weekend and then it’s WWDC next week and I’m going to be distracted, so I’m going to call it on 1.2
Managed to squeeze even more performance this evening.
Here are the results:
| before (ms) | after (ms) | |
|---|---|---|
| edit (total) | 10.96 | 3.16 |
| styling | 5.32 | 1.55 |
| onChange | 3.10 | 0.24 |
| aggregates | 2.62 | 0.38 |
| display-to-store | 2.01 | 0.26 |
| alarms | 0.76 | 0.71 |
| caret | 0.19 | 0.17 |
TestFlight
PaperTrail 1.2 (260605.2315)
1 Like
@Oli your new project in focus bug will be fixed for 1.2 I forgot to merge it in the latest TestFlight but will do another build in the morning.
1 Like
I’m…unsure about gains in this last update. It might be the visual glitches have regressed a little and performance when editing feels marginally better, but not by a whole bunch. Hard to measure and compare, but I’ll keep testing if you make improvements in later versions.
I noticed a couple of minor issues:
-
“Folding by Level” doesn’t seem to work when I’m in a focused view.
-
When I select multiple lines and try to delete them using the trash icon or Ctrl+Shift+K, only the first line is removed. The entire selection gets deleted only when I press Cmd+Backspace. Is that the expected behavior?
I am sure of the gains 
device runs about 20% slower than Simulator, in future tables I’ll be sure to list both Sim and Device.
Not really, that’s what computers are for! All measurements are taken through code to time thousands of repeat operations then taking an average, using automated testing. On device and in Simulator.
Anyway, good news everybody!
This morning’s version:
- more performance improvements
- Oli’s new project whilst focused
- improvements to What’s New panel
- improvements to iPad menu
- first item capitalisation!
About the capitalisation, we can hint to the system what type of capitalisation we want: .none, .words (every word), .sentences (only first word of sentence). The problem is that iOS flip-flops about whether it considers "– " the start of a sentence or not. So my workaround is to check when we are at the start of an item ourselves, and set the hint to .words and then revert it to .sentences when when we are not at the start of an item. I hate having to do this, but it works well enough.
Autocomplete is still off by default because that uses yet another system to detect capitalisation, one that we cannot hint, and it has a tendency to revert our beautiful capitalised first letters to lowercase when you press space. But, of course, you can still toggle it on if you’d prefer to live dangerously.
Will fix those two and push another quick build.
Expected behaviour is whatever TaskPaper does, so this is an oversight by me in PaperTrail so I’ll change it to make it work the same way.
TestFlight
PaperTrail 1.2 (260606.1251)
- changelog at top of thread
I just noticed that my filter icon is disappearing, so I’ve had to pull the submission whilst I figure out when it broke.
Why are you trying to force first letter capitalization at all? TaskPaper doesn’t.
I’ve done a bit of testing. The issues I reported seem to be resolved now. Great! 
1 Like
It’s a good question. It’s because imho that is what is expected on iOS, eg. Notes does it.
My goal is TaskPaper-parity, with an eye on iOS-best practices.
But I suppose that now we can control it, a toggle would be possible in a future version.
TestFlight
PaperTrail 1.2 (260606.1541)
(submitted)
I’d like to make a small aesthetic suggestion.
Would it be possible to place the palette along the right edge of the screen instead of having it pop up in the center? I’ve always wondered why it has to appear in the middle.
When using an iPad, especially while lying down 
, you naturally interact with the right side of the screen using your thumb. As it is now, I have to awkwardly reach for the index finger every time.
I also feel that having the palette appear at the edge would be more in line with a minimalist design approach.
I agree 100% when I was taking the iPad screenshots on the train I thought “the iPad layout really needs more love”
I will make it a priority, maybe I will push a 1.2.1 sooner than 1.3
1 Like