C# Class SIL.FieldWorks.IText.InterlinVc

Add the pile of labels used to identify the lines in interlinear text.

Throw if the IsDisposed property is true

Display the specified object (from an ORC embedded in a string). Don't display any embedded objects in interlinear text.

Estimate the height of things we display lazily.

Initializes a new instance of the InterlinVc class.

We use the default analysis writing system as the default, even though this view displays data in multiple writing systems. It's pretty arbitrary in this case, but we need a valid WS because if we get an ORC, we have to create a Ts String using some writing system.

Call this to clear the temporary cache of analyses. Minimally do this when data changes. Ideally no more often than necessary.

Add a display of the category of hvoAnalysis. If choiceOffset is -1, display the current analysis writing systems, otherwise, display the one indicated (choiceIndex is an index into line choices). When choice index is not -1, hvoAnalysis may not be the current object. In that case, we invoke AddObj with a special flid which results in a recursive call to this, but with the correct current object.

Add the specified string in the specified color to the display, using the UI Writing system.

Displays Analysis using DisplayWordBundleMethod and closes the views Inner Pile.

Format the gloss line for the specified ws in an interlinear text

Normally gets some virtual property tags we need for stuff above the bundle level. Code that is only using fragments at or below bundle may override this to do nothing, and then need not set up the virtual property handlers. See ConstChartVc.

Called right before adding a string or opening a flow object, sets its color.

Setup a box with 10 points behind and 5 under and open the inner pile

Add any extra material after the main bundles. See override on InterlinTaggingVc.

Add a segment number appropriate to the current segment being displayed. (See LT-1236.)

If the analysis writing system has the opposite directionality to the vernacular writing system, we need to add a directionality code to the data stream for the bidirectional algorithm not to jerk the insertion point around at every space. See LT-7738.

Answer true if the specified word can be analyzed. This is a further check after ensuring it has an InstanceOf. It is equivalent to the check made in case kfragBundle of Display(), but that already has access to the writing system of the Wordform. GJM - Jan 19,'10 Added check to see if this occurrence is actually Punctuation. Punctuation cannot be analyzed.

NOTE: this routine is ignorant of calling context, so caller must provide NoteDependency to the possibleVariant and the sense (e.g. vwenv.NoteDependency(new[] { wfiMorphBundle.Hvo }, new[] { WfiMorphBundleTags.kflidSense }, 1); vwenv.NoteDependency(new[] { wfiMorphBundle.Hvo }, new[] { WfiMorphBundleTags.kflidInflType }, 1);

Displays a MorphBundle, setting the colors of its parts.

Get an AnnotationDefn with the (English) name specified, and cache it in cachedVal...unless it is already cached, in which case, just return it.

Get a guess for the given word or analysis.

try to get the ws specified by spec.WritingSystem, otherwise get the default vernacular ws for the display (e.g. ws of paragraph).

Check whether we're looking at vernacular data.

Load data for a group of segments

Set the background color that we use to indicate a guess.

Set the paragraph direction to match wsAnalysis and the paragraph alignment to match the overall direction of the text.

setups up the display to work with the given wsVern.