[solved] Editing an Index Topic name doesn't trigger Preflight

[MikeTO]

This is very minor.

If you rename an index topic the index should become outdated and need to be updated, but Publisher won't mark the index as outdated so Preflight won't show an error or warning. Adding and removing topics will mark the index but not editing a topic name.

Edited January 29, 2023 by MikeTO
marked as solved

[walt.farrell]

I'm not sure I'm duplicating what you've done, but if I rename an index topic the edit changes in-place, automatically, on Windows. Thus it is not out-of-date.

So, perhaps some additional info on your exact workflow, or some screenshots/videos or a sample document?

[MikeTO]

Oh, I'm being dumb, you're completely right. This explains a few other things, too.

For example, if I have a modified index (I added some new marks) but haven't updated it yet, and then rename a topic, the index completely updates, adding the new marks to it.

That's interesting, if the entire index can update automatically when renaming a topic why doesn't it just update the index automatically when I add new index marks?

[walt.farrell]

13 hours ago, MikeTO said:

why doesn't it just update the index automatically when I add new index marks?

I don't think I'd want it to. Adding or deleting index marks is much more common, and if that happened each time you did that there'd be significantly more overhead.

[MikeTO]

4 hours ago, walt.farrell said:

I don't think I'd want it to. Adding it deleting index marks is much more common, and if that happened each time you did that there'd be significantly more overhead.

I'd be okay with it keeping the index up to date all the time, or as an option. It just seems inconsistent that if I add a bunch of index marks but don't update the index that it updates automatically if I fix a typo in an index mark. I think it should work one way or the other.

[Pauls]

I think its the difference between adding/removing marks which is a heavier process than renaming something where we know its location. One requires a scan of the document whereas the other doesnt

[MikeTO]

3 hours ago, Pauls said:

I think its the difference between adding/removing marks which is a heavier process than renaming something where we know its location. One requires a scan of the document whereas the other doesnt

Renaming a mark can add a mark. And when you add a mark it sets the dirty or modified index flag so Publisher never actually needs to scan the document (assuming Preflight is set to Live).

If you add mark A and don't update the index and then rename mark B, Publisher will add mark A and update mark B at the same time.

Edited February 2, 2023 by MikeTO
Preflight setting is irrelevant

[walt.farrell]

13 minutes ago, MikeTO said:

Renaming a mark can add a mark.

How? (Or, under what circumstances?)

[MikeTO]

5 minutes ago, walt.farrell said:

How? (Or, under what circumstances?)

It always does this, at least on macOS. Here's a screen recording to demonstrate. It doesn't matter if Preflight is set to Live or Never but I have it on to make it clear.

 

 

[walt.farrell]

2 minutes ago, MikeTO said:

It always does this,

As I see that, renaming Apples did not add any index marks. It just renamed an index entry that already existed and updated the existing Index.

[MikeTO]

44 minutes ago, walt.farrell said:

As I see that, renaming Apples did not add any index marks. It just renamed an index entry that already existed and updated the existing Index.

Renaming Apples updated the index with Bananas. My point is that if the index can be updated with all pending index changes when renaming a index mark it can just as easily update the index when adding an index mark.