Files
DP44/docs/ai/DataPRO/DataPRO/obj/x86/Debug/CollectDataSubControls/ResolveChannels.md
2026-04-17 14:55:32 -04:00

5.2 KiB
Raw Blame History

source_files, generated_at, model, schema_version, sha256
source_files generated_at model schema_version sha256
DataPRO/DataPRO/obj/x86/Debug/CollectDataSubControls/ResolveChannels/ResolveChannels.g.i.cs
DataPRO/DataPRO/obj/x86/Debug/CollectDataSubControls/ResolveChannels/ResolveChannels.g.cs
2026-04-17T15:57:05.450580+00:00 zai-org/GLM-5-FP8 1 838545b37fdb28f7

Documentation: ResolveChannels (Auto-Generated WPF Component)

1. Purpose

This file contains the auto-generated partial class for ResolveChannels, a WPF user control that appears to manage channel resolution workflows within a data collection system. The control provides UI for categorizing and filtering channels across multiple states (unresolved, resolved, extra IDs, out-of-place, and hardware channels). This is build-generated code from ResolveChannels.xaml and should not be edited directly; the actual business logic resides in a separate code-behind file not provided here.


2. Public Interface

Class Declaration

public partial class ResolveChannels : DataPROWin7.SubControls.SubControl, System.Windows.Markup.IComponentConnector

Public Methods

Method Signature Description
InitializeComponent public void InitializeComponent() Loads the XAML component resource. Idempotent—returns early if already called.

Internal Fields (XAML Element References)

Field Type XAML Line Purpose
resolveChannels DataPROWin7.SubControls.ResolveChannels 12 Self-reference to the control instance
ctrlStatusRibbon DataPROWin7.Controls.StatusRibbon 45 Status ribbon control
ctrlUnResolvedContainer System.Windows.Controls.ContentControl 61 Container for unresolved channel items
ctrlResolvedContainer System.Windows.Controls.ContentControl 64 Container for resolved channel items
ctrlExtraIdsContiner System.Windows.Controls.ContentControl 66 Container for extra ID items
ctrlOutOfPlaceContainer System.Windows.Controls.ContentControl 68 Container for out-of-place items
rbAllChannels System.Windows.Controls.RadioButton 83 Filter: show all channels
rbOpenChannels System.Windows.Controls.RadioButton 84 Filter: show open channels
rbInUseChannels System.Windows.Controls.RadioButton 85 Filter: show in-use channels
rbManuallyAssigned System.Windows.Controls.RadioButton 86 Filter: show manually assigned channels
ctrlHardwareChannelsContainer System.Windows.Controls.ContentControl 89 Container for hardware channel items

Event Handlers (Referenced, Not Defined)

The following event handlers are wired to Checked events on RadioButtons but are not defined in this generated file:

  • rbAllChecked — wired to rbAllChannels.Checked
  • rbOpenChecked — wired to rbOpenChannels.Checked
  • rbInUseChecked — wired to rbInUseChannels.Checked
  • rbManuallyAssignedChecked — wired to rbManuallyAssigned.Checked

3. Invariants

  • Idempotent Initialization: InitializeComponent() will only execute its logic once; subsequent calls return immediately due to the _contentLoaded flag check.
  • Fixed Resource URI: The XAML resource is located at /DataPRO;component/collectdatasubcontrols/resolvechannels/resolvechannels.xaml (relative URI).
  • Connection ID Mapping: The IComponentConnector.Connect method maps integer IDs 111 to specific named controls. This mapping is generated from XAML and must remain synchronized with the XAML file.
  • Inheritance: ResolveChannels must always inherit from DataPROWin7.SubControls.SubControl as defined in the XAML.

4. Dependencies

This Module Depends On

  • DataPROWin7 (root namespace)
  • DataPROWin7.Common
  • DataPROWin7.Controls (specifically StatusRibbon)
  • DataPROWin7.SubControls (specifically SubControl base class)
  • System.Windows.* (WPF framework: System.Windows, System.Windows.Controls, System.Windows.Markup, etc.)

What Depends On This Module

  • Unclear from source alone — the partial class suggests a code-behind file (ResolveChannels.xaml.cs) exists that completes the implementation, but it is not provided.

5. Gotchas

  1. Auto-Generated Code: Both .g.cs and .g.i.cs files are build outputs from PresentationBuildTasks. Any manual edits will be overwritten on rebuild. The actual implementation is in the code-behind file.

  2. Typo in Field Name: ctrlExtraIdsContiner is misspelled (should be ctrlExtraIdsContainer). This typo originates from the XAML x:Name attribute and will propagate throughout the codebase.

  3. Missing Code-Behind: The event handlers (rbAllChecked, rbOpenChecked, rbInUseChecked, rbManuallyAssignedChecked) are referenced but not defined in these files. Their implementation resides in the partial class counterpart (ResolveChannels.xaml.cs), which was not provided.

  4. Duplicate Files: The .g.cs and .g.i.cs files appear identical. In WPF builds, .g.cs is typically generated for regular builds while .g.i.cs is used for IntelliSense. Both should be treated as ephemeral build artifacts.

  5. Namespace Mismatch: The project is named DataPRO but the namespace is DataPROWin7,