C# 클래스 SIL.FieldWorks.FwCoreDlgControls.RegionVariantControl

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

Constructor.

Raises the T:ScriptRegionVariantChanged event.

Activates a child control.

Turn on or off certain side effects of changing the various components of the language tag. Turning on runs the code that normally does the side effects at once.

Deal with special Audio handling

Required method for Designer support - do not modify the contents of this method with the code editor.

Identify characters allowed in the abbreviation fields: upper case or numeric plus hyphen. Strictly ASCII characters are used to name locales. Review: do we need to allow backspace, del, arrow keys?

Load the controls from the writing system, if it is not null. If it is null, clear all controls. If the combo boxes are not populated, do nothing...the method will get called again when the form loads.

Suppress entering invalid characters. Note that, for incomprehensible reasons, Backspace and returns come through this validator, while Delete and arrow keys don't, so we have to allow Backspace/return explicitly but can ignore the others.

This is also called when the selection changes. If the user types the exact name of an existing item, we may get both notifications, and the order we get them is not certain (In fact, it appears that it is somewhat unpredictable(!) whether the index changed happens at all!). However, whatever the order, we make the behavior depend only on whether what's in the text matches one of the items. We do this continuously, not just when the user leaves the control, because the natural place to go when leaving is the abbreviation, but that might be disabled when the user starts editing this box.

Suppress entering invalid characters. Note that, for incomprehensible reasons, Backspace and returns come through this validator, while Delete and arrow keys don't, so we have to allow Backspace/return explicitly but can ignore the others.

This is also called when the selection changes. If the user types the exact name of an existing item, we may get both notifications, and the order we get them is not certain (In fact, it appears that it is somewhat unpredictable(!) whether the index changed happens at all!). However, whatever the order, we make the behavior depend only on whether what's in the text matches one of the items. We do this continuously, not just when the user leaves the control, because the natural place to go when leaving is the abbreviation, but that might be disabled when the user starts editing this box.

Suppress entering invalid characters.

This is also called when the selection changes. If the user types the exact name of an existing item, we may get both notifications, and the order we get them is not certain. However, we expect that whatever the order, the last notification will have a correct SelectedIndex and so should produce the right effects. We do this continuously, not just when the user leaves the control, because the natural place to go when leaving is the abbreviation, but that might be disabled when the user starts editing this box.