NoEventsPending event

   Example   

Occurs after the Microsoft Visio instance flushes its event queue.

Version added

5.0

Syntax

Private Sub object_NoEventsPending(ByVal app As IVApplication)

Remarks

Visio maintains a queue of events and fires them at discrete moments. Immediately after Visio fires the last event in its event queue, it fires a NoEventsPending event.

A client program can use the NoEventsPending event as a signal that Visio has completed a burst of activity. For example, a client program may want to react to changes in a shape's geometry. A single user action performed on the shape can generate several CellChanged events. The client program could record selected information for each CellChanged event and perform its processing after it receives the NoEventsPending event.

Visio fires the NoEventsPending event only if at least one of the events in the queue is being listened to. If no program is listening for any of the queued events, the NoEventsPending event does not fire. If your program is only listening to the NoEventsPending event, it does not fire unless another program is listening for some of the queued events.

If you're using Microsoft Visual Basic or Visual Basic for Applications, the syntax in this topic describes a common, efficient way to handle events.

If you want to create your own Event objects, use the Add or AddAdvise method. To create an Event object that runs an add-on, use the Add method as it applies to the EventList collection. To create an Event object that receives notification, use the AddAdvise method. To find an event code for the event you want to create, see Event codes.