Enum Category

Namespace

Hi.Common.Messages

Assembly

HiGeom.dll

Classification of an IMessage — the “what kind of concern” axis, orthogonal to the Severity importance axis it pairs with. Applies to every IMessage on the channel (lifecycle / progress notices, configuration checks, NC-pipeline diagnostics, …), not only NC messages.

public enum Category

Extension Methods

InvokeUtil.SelfInvoke<TSrc>(TSrc, Action<TSrc>)

InvokeUtil.SelfInvoke<TSrc, TDst>(TSrc, Func<TSrc, TDst>)

MaskUtil.GetMaskedValue<T>(T, T, bool)

MaskUtil.SetMask<T>(ref T, T, bool)

ColorUtil.GetGloomyColor(object, double, double)

NameUtil.GetSelectionName(object)

StringUtil.GetPropertyStringIfToStringNotOverloaded(object, bool, bool)

LockUtil.Lock(object)

Fields

Configuration = 3

Missing or misconfigured end-user dependency / configuration (e.g. coordinate table, tool offset table, machine axis config, rapid feedrate config).

System = 0

General program / pipeline output — lifecycle, progress, infrastructure, internal exceptions. The default when no more-specific category applies.

Unsupported = 1

Recognized but unimplemented feature.

Validation = 2

Manufacturing / physics feasibility check.

Remarks

Representative (Category × Severity) combinations:

• System + Message / Progress → lifecycle, progress, general program output
• System + Error → exception / bug, unconsidered case
• Unsupported + Warning → known unsupported, likely harmless
• Unsupported + Error → known unsupported, likely matters
• Validation + Warning → manufacturing / physics may be unfeasible
• Validation + Error → manufacturing / physics is unfeasible
• Configuration + Message → dependency / config applied, informational
• Configuration + Warning → dependency / config missing, using fallback
• Configuration + Error → dependency / config missing, cannot proceed