RasterImageViewer InteractiveMode.MagnifyGlass freeze

Lead 17 WPF RasterImageViewer: The default function when using InteractiveMode.Magnify is mouse down shows the magnify and mouse up hides the magnify. Is it possible to leave the magnifiy glass in place, freeze, based on lets say a double click event or some key combination? Basically so the user can type with the magnify still showing.

Looks like perhaps this is just a function not supported in the WPF rasterimageviewer, the winforms version has a property AutoInteractiveMagnifyGlass that performs this function.

You're correct; WPF by default does not have such functionality. However, you could customize the behavior slightly using the overrides for OnInteractiveMagnifyGlass.

This does require that you inherit from our control, but it does give us an option. Basically, you want to set the Status to begin and end when YOU want them to. But this will have to be based on input you can gather in conjunction with these overrides.

OnInteractiveMagnifyGlass:
http://www.leadtools.com/help/leadtools/v175/dh/wl/leadtools.windows.controls~leadtools.windows.controls.imageviewer~oninteractivemagnifyglass.html

LineInteractiveEventArgs:
http://www.leadtools.com/help/leadtools/v175/dh/wl/leadtools.windows.controls~leadtools.windows.controls.lineinteractiveeventargs.html

So whats the trick for inheriting the rasterimageviewer? Whenever I try it blows an error at runtime saying the assembly has been tampered with

{"Assembly Keying.Controls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null has been tamerpered with!"}

Source - Leadtools.Windows.Controls

StackTrace - at Leadtools.Windows.Controls.ImageViewer..ctor()
at Leadtools.Windows.Controls.RasterImageViewer..ctor()
at Keying.Controls.ImageControlView..ctor() in C:\IM4Sight2010\Development\WorkInProgress\Product\Solutions\Keying\Keying.Controls\Views\ImageControlView.xaml.cs:line 23

Line 23 is just the constructor, all I’m doing is inherit the RasterImageViewer in a user control don’t even have any functionality defined yet. I think perhaps its something to do with assembly being signed so wondering what the recommendation is for avoiding this error.

This does not appear to be a LEADTOOLS related issue. This seems to be related to your DLL being signed.

When an assembly is signed if it is modified the PublicKeyToken is no longer valid and the error above would be thrown. The error appears to be pointing at the Keying.Controls assembly.