Add AnimBlueprint Window for preview AnimBlueprint

[LoogLong]

AnimBlueprintWindow.mp4

This pull request introduces a new feature for visualizing Unreal Engine Animation Blueprint graphs within the application. The main changes add support for extracting, displaying, and interacting with animation blueprint graphs in a dedicated viewer window.

Animation Blueprint Graph Visualization:

• Added a new AnimGraphViewer window (AnimGraphViewer.xaml) with a modern UI for visualizing Animation Blueprint graphs, including toolbar controls, a graph canvas with layer tabs, and a node properties panel.
• Integrated extraction and display logic for UAnimBlueprintGeneratedClass assets in CUE4ParseViewModel.cs, allowing users to open the new graph viewer when an animation blueprint is selected.
• Registered the required namespace for animation objects in CUE4ParseViewModel.cs to enable the new functionality.

[Copilot]

Pull request overview

Adds an Unreal Engine Animation Blueprint graph preview feature to FModel by extracting AnimBlueprint node/connection data and presenting it in a dedicated WPF viewer window.

Changes:

• Added a new AnimGraphViewer WPF window (XAML + code-behind) to render AnimBlueprint layers/state machines with zoom/pan, selection, and a properties panel.
• Added AnimGraphViewModel extraction + layering logic to build nodes/connections from UAnimBlueprintGeneratedClass cooked data.
• Integrated AnimBlueprint preview launching into CUE4ParseViewModel when an AnimBlueprint generated class is selected.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 7 comments.

File	Description
FModel/Views/AnimGraphViewer.xaml.cs	Implements graph rendering, interaction (tabs, zoom/pan, selection), and properties UI logic.
FModel/Views/AnimGraphViewer.xaml	Defines the viewer window layout (toolbar, tabbed graph area, properties panel, status bar).
FModel/ViewModels/CUE4ParseViewModel.cs	Hooks AnimBlueprint selection to extract graph data and open the viewer window.
FModel/ViewModels/AnimGraphViewModel.cs	Extracts nodes/connections from cooked AnimBlueprint class data and builds layered graph/state-machine representations.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

canvasBorder.AddHandler(..., handledEventsToo: true) causes the pan gesture to begin even when a node/transition handled the click (your node/transition handlers set e.Handled = true, but the Border still receives the event). This makes selection interactions accidentally trigger panning. Consider removing handledEventsToo: true, or gate panning to background clicks only (e.g., ignore when e.OriginalSource is a node/transition element).

Suggested change

	canvasBorder.AddHandler(UIElement.MouseLeftButtonDownEvent,
	new MouseButtonEventHandler(OnCanvasMouseDown), true);
	canvasBorder.MouseLeftButtonDown += OnCanvasMouseDown;

[Copilot]

SelectNode always restores the previously selected Border to a hard-coded BorderBrush/BorderThickness (dark + 1.5). For elements whose default border is different (notably the Entry node hitArea, which starts with thickness 0), this leaves a visible outline after deselection. Suggest storing and restoring the original border brush/thickness per selected visual (or special-case visuals like Entry nodes).

[Copilot]

Closing a tab removes the layer state from _layerStates, but _currentLayerState is not updated/cleared if the closed tab was the selected one (or if the last tab is closed). Toolbar actions like Fit/Reset can then operate on a stale state. Consider updating _currentLayerState after removal (or clearing it when no tabs remain).

[Copilot]

In the properties panel, pin rows use AddPropertyRow(pin.PinName, ...). If PinName is empty (which you already handle elsewhere by showing "(unnamed)"), the key column becomes blank here. Consider using the same fallback display name in the properties panel for consistency/readability.

[Copilot]

A new BlurEffect instance is created for every node shadow (new BlurEffect { Radius = ... }). With large graphs this can become a rendering/perf bottleneck in WPF. Consider reusing a shared frozen BlurEffect (or simplifying shadows) to reduce allocations and GPU/CPU overhead.

[Copilot]

Helper.OpenWindow de-dupes windows by Title. Using the constant title "Animation Blueprint Graph Viewer" means selecting a different AnimBlueprint while the viewer is already open will only focus the existing window and won't display the newly selected graph (since the action won’t run). Consider including the asset/package name in the window title to allow multiple viewers, or reuse the existing window but add an update pathway (e.g., set DataContext / provide a method to load a new AnimGraphViewModel).

Suggested change

	Application.Current.Dispatcher.Invoke(() =>
	{
	Helper.OpenWindow<AnimGraphViewer>("Animation Blueprint Graph Viewer", () =>
	var windowTitle = $"Animation Blueprint Graph Viewer - {pkg.Name}";
	Application.Current.Dispatcher.Invoke(() =>
	{
	Helper.OpenWindow<AnimGraphViewer>(windowTitle, () =>

[Copilot]

IsPoseProperty uses name.Contains("Pose"), which will also match unrelated property names like "Expose…" (since it contains "pose"), causing non-pose properties to be treated as pose inputs and creating bogus pins. Consider tightening this heuristic (e.g., EndsWith("Pose") / known pose-link property names) or, better, add pins only when the underlying property tag is actually a FPoseLink/FComponentSpacePoseLink (same criteria you already use when resolving connections).