<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>wpfinspector Discussions Rss Feed</title><link>http://wpfinspector.codeplex.com/discussions</link><description>wpfinspector Discussions Rss Description</description><item><title>New Post: Not detecting Visual Studio 2010?</title><link>http://wpfinspector.codeplex.com/discussions/355980</link><description>&lt;div style="line-height: normal;"&gt;I had this same problem.  I was running Visual studio as administrator.   If you run VS as administrator then you also have to run WPF inspector as Administrator for the detection to work.&lt;br /&gt;
 &lt;br /&gt;
 Hope this helped.&lt;br /&gt;
&lt;/div&gt;</description><author>rloveless</author><pubDate>Tue, 30 Apr 2013 14:43:22 GMT</pubDate><guid isPermaLink="false">New Post: Not detecting Visual Studio 2010? 20130430024322P</guid></item><item><title>New Post: Request a Feature</title><link>http://wpfinspector.codeplex.com/discussions/249316</link><description>&lt;div style="line-height: normal;"&gt;&lt;ul&gt;
&lt;li&gt;Search visual tree for controls&lt;/li&gt;
&lt;li&gt;Pin properties at the top for I am currently inspecting, and clear, as erikvullings suggests&lt;/li&gt;
&lt;li&gt;Save screenshot! Allow the people who are writing documentation to use WPF Inspector to find the right control, and save a screenshot of the control only. Would make saving symbols much easier (same size, background, no noise)&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>bsundsbo</author><pubDate>Fri, 19 Apr 2013 09:34:39 GMT</pubDate><guid isPermaLink="false">New Post: Request a Feature 20130419093439A</guid></item><item><title>New Post: Can't run this application in Windows XP，.net 4.0</title><link>http://wpfinspector.codeplex.com/discussions/277665</link><description>&lt;div style="line-height: normal;"&gt;no idea.&lt;br /&gt;
&lt;/div&gt;</description><author>GarfieldJiang</author><pubDate>Sun, 31 Mar 2013 11:16:03 GMT</pubDate><guid isPermaLink="false">New Post: Can't run this application in Windows XP，.net 4.0 20130331111603A</guid></item><item><title>New Post: Can't run this application in Windows XP，.net 4.0</title><link>http://wpfinspector.codeplex.com/discussions/277665</link><description>&lt;div style="line-height: normal;"&gt;&lt;strong&gt;GarfieldJiang wrote:&lt;/strong&gt;&lt;br /&gt;
&lt;blockquote&gt;
I installed WPF inspector after installed .net framework 4.0 which worked well.But I received an error which said &amp;quot;Unable to find a version of the run this application&amp;quot;.Some one can tell me &amp;nbsp;why? Appreciate for any replay.&lt;br /&gt;
&lt;/blockquote&gt;
Same problem, any idea?&lt;br /&gt;
&lt;/div&gt;</description><author>meodudang</author><pubDate>Fri, 29 Mar 2013 04:39:35 GMT</pubDate><guid isPermaLink="false">New Post: Can't run this application in Windows XP，.net 4.0 20130329043935A</guid></item><item><title>New Post: Export Property Grid</title><link>http://wpfinspector.codeplex.com/discussions/400024</link><description>&lt;div style="line-height: normal;"&gt;
&lt;p&gt;I was wondering if a export button could be added for the purpose of exporting the details of the property grid to csv or excel. What I'm trying to do is compare 2 elements.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;/div&gt;</description><author>oszymczak</author><pubDate>Fri, 19 Oct 2012 10:09:59 GMT</pubDate><guid isPermaLink="false">New Post: Export Property Grid 20121019100959A</guid></item><item><title>New Post: Trigger is too complex to expect. Problem</title><link>http://wpfinspector.codeplex.com/discussions/360577</link><description>&lt;div style="line-height: normal;"&gt;
&lt;p&gt;I don't know what happens) Inspector just stop working when i point to some elements in my app.&lt;/p&gt;
&lt;p&gt;Can i just turn of this option, or see error on tub of trigger expection&amp;nbsp;to use other functions of the inspector?&lt;/p&gt;
&lt;p&gt;It would be a nice feature.&lt;/p&gt;
&lt;p&gt;Thnx for great program!&lt;/p&gt;
&lt;/div&gt;</description><author>sashakirichek</author><pubDate>Fri, 22 Jun 2012 09:31:58 GMT</pubDate><guid isPermaLink="false">New Post: Trigger is too complex to expect. Problem 20120622093158A</guid></item><item><title>New Post: Not detecting Visual Studio 2010?</title><link>http://wpfinspector.codeplex.com/discussions/355980</link><description>&lt;div style="line-height: normal;"&gt;
&lt;p&gt;I understood Visual Studio 2010 is a WPF application so why does WPF Inspector not detect it?&lt;/p&gt;
&lt;p&gt;Is there a workaround?&lt;/p&gt;
&lt;/div&gt;</description><author>Gary2930</author><pubDate>Wed, 16 May 2012 10:31:57 GMT</pubDate><guid isPermaLink="false">New Post: Not detecting Visual Studio 2010? 20120516103157A</guid></item><item><title>New Post: works with vs11beta, net4.5?</title><link>http://wpfinspector.codeplex.com/discussions/346957</link><description>&lt;div style="line-height: normal;"&gt;
&lt;p&gt;Haven't tried it out yet, though&amp;nbsp;would be helpful to know what is the latest .net/wpf version it should work with before installing.&amp;nbsp; thanks.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;/div&gt;</description><author>techvslife</author><pubDate>Fri, 02 Mar 2012 03:36:27 GMT</pubDate><guid isPermaLink="false">New Post: works with vs11beta, net4.5? 20120302033627A</guid></item><item><title>New Post: Handle events like Snoop</title><link>http://wpfinspector.codeplex.com/discussions/280797</link><description>&lt;div style="line-height: normal;"&gt;
&lt;p&gt;Snoop handles routed events, an extremely useful feature. &amp;nbsp;However, its interface is clunky and doesn't let you drill directly to a certain part using Ctrl&amp;#43;Shift click on the UI, so it can take forever to debug. &amp;nbsp;If WPF Inspector allowed for event
 debugging, it would be the perfect all in one tool.&lt;/p&gt;
&lt;/div&gt;</description><author>cbordeman</author><pubDate>Fri, 25 Nov 2011 07:16:02 GMT</pubDate><guid isPermaLink="false">New Post: Handle events like Snoop 20111125071602A</guid></item><item><title>New Post: Can't run this application in Windows XP，.net 4.0</title><link>http://wpfinspector.codeplex.com/discussions/277665</link><description>&lt;div style="line-height: normal;"&gt;
&lt;p&gt;I installed WPF inspector after installed .net framework 4.0 which worked well.But I received an error which said &amp;quot;Unable to find a version of the run this application&amp;quot;.Some one can tell me &amp;nbsp;why?&lt;/p&gt;
&lt;p&gt;Appreciate for any replay.&lt;/p&gt;
&lt;/div&gt;</description><author>GarfieldJiang</author><pubDate>Sun, 30 Oct 2011 04:14:03 GMT</pubDate><guid isPermaLink="false">New Post: Can't run this application in Windows XP，.net 4.0 20111030041403A</guid></item><item><title>New Post: Request a Feature</title><link>http://wpfinspector.codeplex.com/discussions/249316</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;Major feature request:&amp;nbsp; &lt;strong&gt;WIFF&lt;/strong&gt; - Where Is the &lt;em&gt;Fascinating &lt;/em&gt;Focus.&lt;/p&gt;
&lt;p&gt;Sometimes keyboard focus goes who-knows-where, and knowing &lt;em&gt;where&lt;/em&gt; focus&amp;nbsp;landed may help when pondering &lt;em&gt;why&lt;/em&gt; it landed there.&amp;nbsp; UISpy in "follow focus" mode&amp;nbsp;is helpful to a point, but it is dependent on the AP tree rather than the visual tree.&lt;/p&gt;&lt;/div&gt;</description><author>Eljay</author><pubDate>Thu, 06 Oct 2011 16:32:04 GMT</pubDate><guid isPermaLink="false">New Post: Request a Feature 20111006043204P</guid></item><item><title>New Post: Request a Feature</title><link>http://wpfinspector.codeplex.com/discussions/249316</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;When navigating the visual tree with the keyboard, I noticed that the arrow keys don't work as (I) expected. The left/right arrows don't do anything.&lt;/p&gt;
&lt;p&gt;Feature request: implement the default arrow navigation behaviour, e.g. when I press left, I either navigate to the next child, or expand the current element. In addition, although less useful, + and - would allow me to expand/collapse everything at once.&lt;/p&gt;&lt;/div&gt;</description><author>erikvullings</author><pubDate>Thu, 04 Aug 2011 12:45:51 GMT</pubDate><guid isPermaLink="false">New Post: Request a Feature 20110804124551P</guid></item><item><title>New Post: Request a Feature</title><link>http://wpfinspector.codeplex.com/discussions/249316</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;Another suggestion: currently, we can filter properties using a textbox. Sometimes, however, I'm interested in a few properties that require me to enter several keywords or see everything at once.&lt;/p&gt;
&lt;p&gt;Feature request: use pins to pin multiple properties (e.g. a pin next to the breakpoint), and an option to clear them all.&lt;/p&gt;&lt;/div&gt;</description><author>erikvullings</author><pubDate>Thu, 04 Aug 2011 12:43:38 GMT</pubDate><guid isPermaLink="false">New Post: Request a Feature 20110804124338P</guid></item><item><title>New Post: Request a Feature</title><link>http://wpfinspector.codeplex.com/discussions/249316</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;The problem: When debugging an app, after a first debug session, I already know where the problem is. I normally fix something, and try to see if the problem has gone away. This often doesn't happen, so I need to find the troublesome location again. Sometimes, this is as easy as selecting the item again, but sometimes, it isn't (for example, when debugging a MS Surface application, the hover option doesn't work, so I need to manually browse through the visual tree).&lt;/p&gt;
&lt;p&gt;Feature request: allow me to bookmark a view, or else to search the visual tree (e.g. for MainView).&lt;/p&gt;&lt;/div&gt;</description><author>erikvullings</author><pubDate>Thu, 04 Aug 2011 12:08:34 GMT</pubDate><guid isPermaLink="false">New Post: Request a Feature 20110804120834P</guid></item><item><title>New Post: Request a Feature</title><link>http://wpfinspector.codeplex.com/discussions/249316</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;The problem: I normally use WPF inspector to debug a running process. It requires me to start WPF inspector, and select the process to attach too. When I end my app, WPF Inspector exits too. This is quite cumbersome.&lt;/p&gt;
&lt;p&gt;Feature request: Would it be possible to automatically start WPF Inspector after my debug session was launched. Or, perhaps even easier, don't exit WPF Inspector when the attached application ends, but automatically re-attach when the process is relaunched.&amp;nbsp;&lt;/p&gt;&lt;/div&gt;</description><author>erikvullings</author><pubDate>Thu, 04 Aug 2011 12:04:27 GMT</pubDate><guid isPermaLink="false">New Post: Request a Feature 20110804120427P</guid></item><item><title>New Post: Report an Issue</title><link>http://wpfinspector.codeplex.com/discussions/249334</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;Hi Chrisitan,&lt;/p&gt;
&lt;p&gt;It would be great if WPFInspector could catch Popup objects.&lt;/p&gt;&lt;/div&gt;</description><author>Belorus</author><pubDate>Wed, 13 Jul 2011 15:22:50 GMT</pubDate><guid isPermaLink="false">New Post: Report an Issue 20110713032250P</guid></item><item><title>New Post: Windows on Different Threads</title><link>http://wpfinspector.codeplex.com/discussions/253264</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;Each window needs to run independently, without dialog boxes preventing access to other windows.&lt;/p&gt;
&lt;p&gt;Is it possible to make the Inspector see the individual threads that have dispatchers when selecting an application to inspect?&lt;/p&gt;&lt;/div&gt;</description><author>DRWebMonkey</author><pubDate>Tue, 26 Apr 2011 21:01:45 GMT</pubDate><guid isPermaLink="false">New Post: Windows on Different Threads 20110426090145P</guid></item><item><title>New Post: Windows on Different Threads</title><link>http://wpfinspector.codeplex.com/discussions/253264</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;currently it's not possible to inspect different threads, since the WPF inspector injects itself over the Windows message loop that runs in the main UI thread.&lt;/p&gt;
&lt;p&gt;Why do you need all these different threads? Can you maybe create a debug switch to run the application in one thread only for debugging it?&lt;/p&gt;
&lt;p&gt;Greetings&lt;br /&gt;Christian&lt;/p&gt;&lt;/div&gt;</description><author>cmoser</author><pubDate>Tue, 26 Apr 2011 20:33:17 GMT</pubDate><guid isPermaLink="false">New Post: Windows on Different Threads 20110426083317P</guid></item><item><title>New Post: Windows on Different Threads</title><link>http://wpfinspector.codeplex.com/discussions/253264</link><description>&lt;div style="line-height: normal;"&gt;
&lt;p&gt;I'm building an application that uses a seperate thread for each window.&lt;/p&gt;
&lt;p&gt;When I attach to the application, I can only see the original thread windows. Is there a way to attach to the other threads?&lt;/p&gt;
&lt;/div&gt;</description><author>DRWebMonkey</author><pubDate>Sun, 10 Apr 2011 00:19:49 GMT</pubDate><guid isPermaLink="false">New Post: Windows on Different Threads 20110410121949A</guid></item><item><title>New Post: Popups</title><link>http://wpfinspector.codeplex.com/discussions/252818</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;Hi Christian,&lt;/p&gt;
&lt;p&gt;Unfortunately the application i am currently working on uses Popups heavily.&lt;/p&gt;
&lt;p&gt;And yes, Snoop can handle Popups.&lt;/p&gt;
&lt;p&gt;WPF Inspector has some great features so i am looking forward for a Popup-capable version in the future.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Gunter&lt;/p&gt;&lt;/div&gt;</description><author>gunters</author><pubDate>Thu, 07 Apr 2011 18:31:18 GMT</pubDate><guid isPermaLink="false">New Post: Popups 20110407063118P</guid></item></channel></rss>