Version: 126.96.36.199 Beta (1129554) 64-bit - 04 Dec 2020
With a relatively big project and compile settings that assemble an entire manuscript, the compile operation provides meaningful feedback as it works at first. There is a point, however, when all feedback drops as if operations are complete. The Compile window stays open, however, with action buttons disabled. It’s obviously still working in the background. It eventually disappears and then that is how I know the compile is complete. In my opinion, it does not make sense to provide status bars in the beginning of the processing if they are not going to be present for all of the processing. I would expect a last status bar to reach 100% and then the compile window to disappear at that point. Otherwise, why show a status for half the compile operation, but not the other? For me personally, it’s not too bad because I’ve learned it. But I have been working with an older man who is not as proficient with computers and the compile operation status had him confused. I had to tell him , “Just wait until the compile window disappears. Trust me, it’s still working.” This is beta feedback, not a complaint. I love Scrivener and you guys are doing a great job with it.