C# Class SIL.FieldWorks.XWorks.LexEd.ReversalIndexEntryChangeHandler

Summary description for ReversalIndexEntryChangeHandler.
Inheritance: IRecordChangeHandler, IFWDisposable
Afficher le fichier Open project: sillsdev/FieldWorks

Protected Properties

Свойство Type Description
m_originalForm string
m_rie IReversalIndexEntry
m_rlu IRecordListUpdater

Méthodes publiques

Méthode Description
CheckDisposed ( ) : void

Check to see if the object has been disposed. All public Properties and Methods should call this before doing anything else.
Dispose ( ) : void

Must not be virtual.

Fixup ( bool fRefreshList ) : void

Handle possible homograph number changes: 1. Possibly remove homograph from original citation form. 2. Possibly add homograph for new citation form.
ReversalIndexEntryChangeHandler ( ) : System
Setup ( object o, IRecordListUpdater rlu ) : void

Méthodes protégées

Méthode Description
Dispose ( bool disposing ) : void

Executes in two distinct scenarios. 1. If disposing is true, the method has been called directly or indirectly by a user's code via the Dispose method. Both managed and unmanaged resources can be disposed. 2. If disposing is false, the method has been called by the runtime from inside the finalizer and you should not reference (access) other managed objects, as they already have been garbage collected. Only unmanaged resources can be disposed.

If any exceptions are thrown, that is fine. If the method is being done in a finalizer, it will be ignored. If it is thrown by client code calling Dispose, it needs to be handled by fixing the bug. If subclasses override this method, they should call the base implementation.

Method Details

CheckDisposed() public méthode

Check to see if the object has been disposed. All public Properties and Methods should call this before doing anything else.
public CheckDisposed ( ) : void
Résultat void

Dispose() public méthode

Must not be virtual.
public Dispose ( ) : void
Résultat void

Dispose() protected méthode

Executes in two distinct scenarios. 1. If disposing is true, the method has been called directly or indirectly by a user's code via the Dispose method. Both managed and unmanaged resources can be disposed. 2. If disposing is false, the method has been called by the runtime from inside the finalizer and you should not reference (access) other managed objects, as they already have been garbage collected. Only unmanaged resources can be disposed.
If any exceptions are thrown, that is fine. If the method is being done in a finalizer, it will be ignored. If it is thrown by client code calling Dispose, it needs to be handled by fixing the bug. If subclasses override this method, they should call the base implementation.
protected Dispose ( bool disposing ) : void
disposing bool
Résultat void

Fixup() public méthode

Handle possible homograph number changes: 1. Possibly remove homograph from original citation form. 2. Possibly add homograph for new citation form.
public Fixup ( bool fRefreshList ) : void
fRefreshList bool
Résultat void

ReversalIndexEntryChangeHandler() public méthode

public ReversalIndexEntryChangeHandler ( ) : System
Résultat System

Setup() public méthode

public Setup ( object o, IRecordListUpdater rlu ) : void
o object
rlu IRecordListUpdater
Résultat void

Property Details

m_originalForm protected_oe property

original citation form
protected string m_originalForm
Résultat string

m_rie protected_oe property

Reversal entry being monitored for changes.
protected IReversalIndexEntry m_rie
Résultat IReversalIndexEntry

m_rlu protected_oe property

protected IRecordListUpdater m_rlu
Résultat IRecordListUpdater