aeontimeline

Open full view…

Unignore?

charlotterazon
Tue, 27 Jun 2017 09:26:48 GMT

Hi ^^ Is there a way to "unignore" a Scrivener document that has been set to "ignore"? Thanks for your help!

razyr
Tue, 27 Jun 2017 15:29:12 GMT

I also have this question. There doesn't seem to be a way. If you have a folder with two items "A" and "B" then ignore "A", there's no option to toggle off the ignore. If you then ignore the subtree at the parent folder level, "B" gets ignored, but you can switch it back with "Unignore subtree". "A" remains ignored.

charlotterazon
Tue, 27 Jun 2017 16:24:06 GMT

Yes, I tried the same thing... with the same result ^^ This shouldn’t be too hard to add though 🤔

aeonjess
Wed, 28 Jun 2017 01:16:39 GMT

Hi, We didn't implement this functionality because even when a document is ignored, you can still choose to sync it to an existing event or create a new event for it. When this happens it is effectively unignored. Is there a reason you wish to unignore a document but not immediately sync it to an event? Jess

razyr
Wed, 28 Jun 2017 02:46:09 GMT

I can't think of a use case for unignoring a document and then not linking it to an event.

chrille_from_sweden
Sun, 30 Jul 2017 14:04:00 GMT

My usecase is that I want the event to be linked to a scene in Scrivener. I ignored the scrivener document by mistake. Then if I link the ignored scene to some other event, it will not reflect in the original scrivener scene if/when I change different parameters. The thing with sync is that changes should reflect, but if I ignored a scene by mistake, it´s not possible anymore. So "unignore" would be a good thing :-)

razyr
Sun, 30 Jul 2017 16:51:51 GMT

From the end user's perspective, are there not just three state combinations that exist between documents and events? 1. Ignored 2. Not ignored but unlinked to any event (So you get the grey question mark) 3. Linked. The first state exists just so we're not seeing prompts to link items that we never have any intention to link. If you had an "unignore" menu option for single documents, you're really just enabling the prompts again for that item. If you ignored an item in the past by mistake, you can just link it to the correct event and it goes to the third state in one step. Any changes that you make in either the timeline or the binder metadata will be synced.By definition, if an event and document are linked, they SHOULD longer be on the ignore list. What doesn't happen is the "ignore" flag is never unset. I'd say this constitutes a bug. It seems that "ignore" is a separate state internally within AT2, but it doesn't have any meaning if the document is linked. This can be demonstrated by: - Ignore a document in the binder. - Link the ignored document t o an event. - Unlink the event and the document At this point, if the document was "unignored" you should get the grey question mark showing the document isn't linked. The fact that the question mark status isn't shown seems to be the only shortcoming of the current model. I don't think it's hampering sync in any way.