[Progresso]

Thank you Derek,

Your reply helped me a lot.

I have now changed the code thus grouping multiple events into a single undoable action inside a single macro.

In a couple of places I needed to control the flickering with ActiveDocument.FormattingUpdating=false/true

All this was resolved neatly, with only one remaining problem:

When I prompted the user with Application.Confirm() before performing a large number of DOM modifications, the processing became MUCH slower than without the prompt.

It seems like the mere appearance of a modal dialog creates problems.

I solved the problem by creating an XFT window with yes/no buttons, and performing the large number om DOM modifications from within the window.

Best regards
Bo

Reply

[Progresso]

Thanks Derek

I was unaware of the existence of Application.DisablePlainTextView()

I can see that it's supposed to be called from the On_Application_Open event, but this cannot be allowed in my client's case since they used the samme application settings for many users that open a variety of document types.  Some of these users might enjoy the Plain Text view so I cannot just disable it for all.

However, I have tested Application.DisablePlainTextView() from one of the “document macros”, the On_Macro_File_Load event.  This allows me to prevent Plain Text view only for selected document types (Schemas).  It works fine in version 4.6 so I'll keep it.  Hope that it also works in version 5.x/6.x.

You solved my problem 🙂

Bo

Reply

[Progresso]

Thank you Derek Read and Tom Magliery.

On our system I not sure that I cannot always rely on write access for creating a CSS file.  Furthermore, the id attribute is not always present, and the attributes that are always present are not always unique.

I have therefore decided to flash the selection on-off as Tom suggests.

Regards
Bo

Reply

[Author]

Posts