基于Caliburn Micro的WPF多窗口缩放失效问题排查

Let's break down why your secondary windows (like AboutBox, Settings) aren't responding to the ScaleTransform, even though the same code works in your MainWindow. Here are the most common fixes to check:

1. You Forgot to Apply the ScaleTransform to the Window's RenderTransform #

Having the ScaleTransform defined in your Window.Resources is only half the job—you need to actually attach it to the window's rendering pipeline. Chances are your MainWindow has this line, but your secondary windows don't:

<Window.RenderTransform>
    <StaticResource ResourceKey="windowScaleTransform" />
</Window.RenderTransform>

Add this directly to your AboutBox/Settings window XAML, right after the Window.Resources section. Without this, the transform exists in resources but never gets used to scale the window.

2. Your Secondary Window ViewModel Doesn't Have the ScaleX/ScaleY Properties (or Doesn't Notify Changes) #

Caliburn Micro relies on viewmodels implementing INotifyPropertyChanged (or inheriting from its built-in Screen/PropertyChangedBase classes) to update bindings.

• First, make sure your AboutBoxViewModel inherits from Screen (or a shared base viewmodel that includes the scale properties):

  public class AboutBoxViewModel : Screen
  {
      // Reuse the same ScaleX/ScaleY properties from your MainWindowViewModel
      private double _scaleX = 1.0;
      public double ScaleX
      {
          get => _scaleX;
          set => Set(ref _scaleX, value); // Caliburn's Set() auto-triggers PropertyChanged
      }
  
      private double _scaleY = 1.0;
      public double ScaleY
      {
          get => _scaleY;
          set => Set(ref _scaleY, value);
      }
  
      // Rest of your viewmodel code...
  }
  

• If you want scale to be a global setting (so all windows scale together), move ScaleX/ScaleY to a shared base class (e.g., BaseViewModel : Screen) and have all window viewmodels inherit from that. This avoids duplicating code and ensures consistency.

3. Verify the DataContext is Correctly Bound #

While Caliburn Micro usually sets the DataContext automatically when using windowManager.ShowDialog(), double-check that your secondary window's DataContext is actually pointing to its viewmodel:

• You can explicitly set it in the window's constructor:

  public AboutBox(AboutBoxViewModel viewModel)
  {
      InitializeComponent();
      DataContext = viewModel;
  }
  

• Also confirm your view-model naming follows Caliburn's conventions: AboutBox.xaml should pair with AboutBoxViewModel.cs (same namespace helps too).

4. Ensure Property Changes Are Triggered #

Double-check that when you update ScaleX/ScaleY (e.g., from your MainWindow), the property change notification is firing. If you're not using Caliburn's Set() method, make sure you manually raise the PropertyChanged event:

private double _scaleX = 1.0;
public double ScaleX
{
    get => _scaleX;
    set
    {
        _scaleX = value;
        NotifyOfPropertyChange(() => ScaleX); // Caliburn's method, or use PropertyChanged?.Invoke(...)
    }
}

Quick Troubleshooting Tip #

To debug binding issues, add this to your secondary window XAML to see binding errors in Visual Studio's Output window:

xmlns:diagnostics="clr-namespace:System.Diagnostics;assembly=WindowsBase"

Then modify your ScaleTransform bindings to include diagnostics:

ScaleX="{Binding ScaleX, UpdateSourceTrigger=PropertyChanged, Mode=TwoWay, diagnostics:PresentationTraceSources.TraceLevel=High}"

This will show if the binding is finding the property, if values are being passed, etc.

内容的提问来源于stack exchange，提问作者booshi