wpfinspector Issue Tracker Rss Feed

Created Issue: 64 bit Compatibility [1130]

vonbalaji — Fri, 22 Feb 2013 11:00:20 GMT

When I run the WPF inspector, it's not listing the application running in 64bit mode?

Are there any settings for attaching the applications under 64 bit ?

Thanks

Created Issue: Feature: Support for NotifyPropertyChanged [1067]

mbendtsen — Tue, 02 Oct 2012 18:00:45 GMT

Could be nice to have a feature where you would be able to see a log of INotifyPropertyChanged.PropertyChanged and INotifyCollectionChanged.CollectionChanged events raised by the DataContext.
You should be able to see which property what was changed and which Action in the CollectionChanged event was performed (Add, Remove, Reset, Move).

Created Issue: Elements tree display glitch [1054]

AccessD — Fri, 14 Sep 2012 05:49:06 GMT

When I'm selecting some element by Ctrl+LeftMouseButton element is focused in elements tree. Elements tree is expanded and scrolled to make selected element visible. But it is scrolled only vertically and if nesting is high, we can see just a blank view, because selected element is far to the right. I think elements tree content should be scrolled maximum to the right each time.

Created Issue: Slight incompatibility with .Net 4.5 [1037]

hamish — Mon, 20 Aug 2012 12:03:57 GMT

I realise nobody every claimed this would work with 4.5, but it doesn't seem to be very far off and I'm going to miss this tool until it's updated.

After I select any UI element either in the tree or using Ctrl+click, I get at least 400 Resource not found warnings in my application. These take a long time to run through, so it makes using the tool very slow.

Created Issue: Make readonly labeles copyable [925]

abatishchev — Thu, 26 Apr 2012 12:41:56 GMT

Readonly values on such tabs as Properties or DataContext can't be copied: text can't be selected, context menu contains no active items.
Please change that.

Commented Issue: Still getting "Trigger too complex to inspect!" crash message [663]

BLJ — Tue, 27 Mar 2012 08:53:27 GMT

Hello,

I am running 0.9.9 and keep getting the "Trigger too complex to inspect!" exception when I try to inspect text blocks that have data triggers in their styles. The styles are defined in a separate assembly and are referred to using {DynamicResource}. Also the styles utilize inheritance via the BasedOn attribute. The WPF inspector app crashes :-(
Comments: ** Comment from web user: BLJ **

We're having the same issue.
I'd be glad to provide additional information if needed.

Thank you for your time - and the great tool!

Created Issue: The tool always tries to attach the first WPF application in the list [836]

Ucodia — Tue, 03 Jan 2012 16:05:44 GMT

When you have many WPF applications opened, whatever application you select for inspection, WPF Inspector will always try attach to the first in the list.

Commented Issue: Still getting "Trigger too complex to inspect!" crash message [663]

petunya — Tue, 19 Jul 2011 22:35:40 GMT

More Info --- this exception is preventing me from using the app almost entirely. I hit it all the time.

System.IndexOutOfRangeException

at ChristianMoser.WpfInspector.Services.Triggers.ConditionItem.GetPropertyFromIndex(Int32 index)
at ChristianMoser.WpfInspector.Services.Triggers.ConditionItem.HookBinding()
at ChristianMoser.WpfInspector.Services.Triggers.ConditionItem..ctor(BindingBase binding, Object instance, Object value)
at ChristianMoser.WpfInspector.Services.Triggers.DataTriggerItem.<GetConditions>d__1.MoveNext()
at System.Collections.Generic.List`1.InsertRange(Int32 index, IEnumerable`1 collection)
at System.Collections.Generic.List`1.AddRange(IEnumerable`1 collection)
at ChristianMoser.WpfInspector.Services.Triggers.TriggerItemBase.Initialize()
at ChristianMoser.WpfInspector.Services.Triggers.TriggerItemFactory.GetTriggerItem(TriggerBase trigger, FrameworkElement source, TriggerSource triggerSource)
at ChristianMoser.WpfInspector.Services.StyleExplorer.StyleItem..ctor(Style style, FrameworkElement source, String name, String location, StyleScope scope)
at ChristianMoser.WpfInspector.UserInterface.Controls.PropertyItems.StylePropertyItem.LoadStyles()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run(Window window)
at System.Windows.Application.Run()
at Schilling.Robotics.ROV.HMI.Shell.App.Main() in C:\HHProduction\Schilling.Robotics.Framework\Dev\Framework\Application_ROV\HMI\Shell\obj\x86\Debug\App.g.cs:line 52
at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Commented Issue: Still getting "Trigger too complex to inspect!" crash message [663]

petunya — Tue, 19 Jul 2011 20:32:57 GMT

Forgot to add, the data trigger binding uses a converter, in case that info helps.

Created Issue: Still getting "Trigger too complex to inspect!" crash message [663]

petunya — Tue, 19 Jul 2011 20:30:48 GMT

Created Issue: Unreadable errors list [632]

RafalFurman — Fri, 10 Jun 2011 15:00:25 GMT

Errors list can only display one line of text per error which makes it useless while error description is long.

Commented Issue: The handle is invalid. [474]

jhetzer — Wed, 23 Mar 2011 09:32:29 GMT

When I try to attach the WPF Inspector to my 64bit framework 4.0 application it gives me the following error:

The handle is invalid.

(Screenshot attached but in german language.)

Kind Regards,

J. H.
Comments: ** Comment from web user: jhetzer **

Hi Christian,

I found out that this problem is caused because I "just" start WPF Inspector.

If I start the WPF Inspector using right mouse click - "run as administrator" the error disappears.

KR,
J. H.

Commented Issue: The handle is invalid. [474]

cmoser — Sun, 20 Mar 2011 20:50:52 GMT

Hi,

thank you for the feedback. I tried to reproduce the problem, but on my machine it worked.
Can you provide some more details about your system configuration. OS version, versions of VisualStudio and .NET runtimes installed? Or can you download the source code and try to debug the problem? This would help me the most.

Thanks
Christian

Closed Issue: Can't select WPF application [489]

cmoser — Fri, 18 Mar 2011 17:47:18 GMT

When multiple WPF applications are running, no matter wich one I select WPF Inspector attach itself to the first in the list
Comments:

Fixed

Commented Issue: Can't select WPF application [489]

cmoser — Fri, 18 Mar 2011 17:46:54 GMT

When multiple WPF applications are running, no matter wich one I select WPF Inspector attach itself to the first in the list
Comments: ** Comment from web user: cmoser **

Added missing IsSynchronizedWithCurrentItem to application list
(Revision 4734)

Created Issue: Can't select WPF application [489]

tbayart — Thu, 17 Mar 2011 10:46:55 GMT

When multiple WPF applications are running, no matter wich one I select WPF Inspector attach itself to the first in the list

Created Issue: The handle is invalid. [474]

jhetzer — Fri, 11 Mar 2011 12:32:49 GMT