<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/windowdetective/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/windowdetective/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 01 Jan 2023 23:44:40 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/windowdetective/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>#15 Some GDI windows are not seen</title><link>https://sourceforge.net/p/windowdetective/bugs/15/?limit=25#a64e</link><description>&lt;div class="markdown_content"&gt;&lt;blockquote&gt;
&lt;p&gt;There seems to be a taskbar button and/or Glass/Aero frame with stale&lt;br/&gt;
background and that's it.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Ah that might be it. When an app "hangs" in Windows, I often see it's window being replaced with a window owned by DWM. That's when the window goes translucent white.&lt;/p&gt;
&lt;p&gt;By the way, I apologise for any crashes in WD. I did work on improving it's stability while it was in active development, but I haven't touched it in over a decade. At this stage I'm just glad some people are still getting use out of it!&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">xtal256</dc:creator><pubDate>Sun, 01 Jan 2023 23:44:40 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netd5195045800ff271b02019e1d609244faa065c5c</guid></item><item><title>#15 Some GDI windows are not seen</title><link>https://sourceforge.net/p/windowdetective/bugs/15/?limit=25#fae3</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Have you tried refreshing the Window Detective tree (Green button in the toolbar, or menu View &amp;gt; Refresh)?&lt;br/&gt;
Whilst Window Detective can track the creation and destruction of windows and automatically update the tree, it does not always see new windows.&lt;/p&gt;
&lt;p&gt;If you started up Window Detective after PMM and still can't see it's window, then I'm afraid I cannot offer any help. WD just uses the &lt;a class="" href="https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-enumchildwindows" rel="nofollow"&gt;EnumChildWindows&lt;/a&gt; function to get all child windows of the &lt;a class="" href="https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-getdesktopwindow" rel="nofollow"&gt;desktop&lt;/a&gt;.&lt;br/&gt;
I don't know if it's possible for PMM to show a window but have it not be enumerated by that function.&lt;br/&gt;
It's possible that it is not a child window of the desktop, but I don't know how that would work.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">xtal256</dc:creator><pubDate>Tue, 27 Dec 2022 02:25:48 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netee6b28b224e5ff0c105b5687fb9a1b349c7e09a1</guid></item><item><title>Some GDI windows are not seen</title><link>https://sourceforge.net/p/windowdetective/bugs/15/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Can't find PMM's initial window.&lt;/p&gt;
&lt;p&gt;See: &lt;a href="https://github.com/AlexanderBagel/ProcessMemoryMap/issues/8" rel="nofollow"&gt;https://github.com/AlexanderBagel/ProcessMemoryMap/issues/8&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;When PMM is first launched it has the "select window" dialog.&lt;/p&gt;
&lt;p&gt;WD 3.5.1&lt;br/&gt;
PMM 1.1.15 up to the now latest v1.3.20-beta&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Burov Dmitry</dc:creator><pubDate>Sat, 10 Dec 2022 12:40:22 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net664362dd92194a2038f156eb794e24f1620be325</guid></item><item><title>#12 Crash on opening Office VBEditor</title><link>https://sourceforge.net/p/windowdetective/bugs/12/?limit=25#c5fe</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Just got exact same thing. If I have a normal Excel .xlsx file open and I start WD, all is fine. Then in Excel I try to open the VBIDE and Excel crashes.&lt;br/&gt;
Alternatively, if I have a workbook with macros (.xlsm) open (VBIDE not open) and I start WD, Excel crashes.&lt;br/&gt;
WD 3.5.1, Excel 365 desktop.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ddk1</dc:creator><pubDate>Thu, 03 Mar 2022 21:22:10 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netb16b4fccc19fe7688e715acea53629f5bd90b963</guid></item><item><title>#12 Crash on opening Office VBEditor</title><link>https://sourceforge.net/p/windowdetective/bugs/12/?limit=25#f206</link><description>&lt;div class="markdown_content"&gt;&lt;ol&gt;
&lt;li&gt;Neither Window Detective nor any of the MS Office applications was launched&lt;/li&gt;
&lt;li&gt;First, run the Window Detective application;&lt;/li&gt;
&lt;li&gt;Then run Excel in safe mode and create an empty workbook.&lt;/li&gt;
&lt;li&gt;Re-index windows in Window Detective by executing the "Refresh All Window" command or by pressing F5&lt;/li&gt;
&lt;li&gt;Everything works as expected&lt;/li&gt;
&lt;li&gt;Opening VBIDE in running Excel (it does not matter if the VBE window was closed after that)&lt;/li&gt;
&lt;li&gt;Re-index windows in Window Detective by executing the "Refresh All Window" command or by pressing F5&lt;/li&gt;
&lt;li&gt;MS Office Application crashed with message "Excel has stopped working". Closed this message.&lt;br/&gt;
9 After updating windows in Window Detective, new error lines appeared in the log:&lt;br/&gt;
04/27/2020 23:28:14 - Warning: The message 127 sent to window VbaWindow (0x00113308) has timed-out. wParam = 0, lParam = 0&lt;br/&gt;
04/27/2020 23:28:15 - Warning: The message 127 sent to window VbaWindow (0x00113308) has timed-out. wParam = 1, lParam = 0&lt;br/&gt;
04/27/2020 23:28:15 - Warning: The message 14 sent to window VbaWindow (0x00113308) has timed-out. wParam = 0, lParam = 0&lt;br/&gt;
04/27/2020 23:28:16 - Warning: The message 127 sent to window ScrollBar (0x002C262C) has timed-out. wParam = 0, lParam = 0&lt;br/&gt;
04/27/2020 23:28:17 - Warning: The message 127 sent to window ScrollBar (0x002C262C) has timed-out. wParam = 1, lParam = 0&lt;br/&gt;
04/27/2020 23:28:17 - Warning: The message 14 sent to window ScrollBar (0x002C262C) has timed-out. wParam = 0, lParam = 0&lt;br/&gt;
04/27/2020 23:28:18 - Warning: The message 127 sent to window ScrollBar (0x00077446) has timed-out. wParam = 0, lParam = 0&lt;br/&gt;
04/27/2020 23:28:18 - Warning: The message 127 sent to window OfficePowerManagerWindow (0x003D6684) has timed-out. wParam = 0, lParam = 0&lt;/li&gt;
&lt;/ol&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrey Lyashchuk</dc:creator><pubDate>Mon, 27 Apr 2020 20:39:20 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net8c04cd6c599741d9111d85c92ed42b7b34205af2</guid></item><item><title>#14 Can't monitor window messages</title><link>https://sourceforge.net/p/windowdetective/bugs/14/?limit=25#b8b9</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I've planned to do it for a while now, but I never got around to it. Been too busy with other stuff.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">xtal256</dc:creator><pubDate>Fri, 25 Jan 2019 03:29:47 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net643d894b4baf428ec064d970e2870f83ba3903e7</guid></item><item><title>#14 Can't monitor window messages</title><link>https://sourceforge.net/p/windowdetective/bugs/14/?limit=25#39f8</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Ah, that explains it! Any plans for 64bit support? Thoughts on a warning message when you try to invoke it on an unsupported app?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Charlie Hayes</dc:creator><pubDate>Mon, 21 Jan 2019 05:23:04 -0000</pubDate><guid isPermaLink="false">https://sourceforge.neta2f51833dcc0c75802444ce82c702267db1df131</guid></item><item><title>#14 Can't monitor window messages</title><link>https://sourceforge.net/p/windowdetective/bugs/14/?limit=25#d57e</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I suspect you are trying to monitor messages of a 64-bit application. Due to Window Detective being 32-bit, it can only monitor 32-bit applications. &lt;/p&gt;
&lt;p&gt;When viewing properties of a window in a 64-bit application, you might see an "access denied" warning message. However, nothing is logged if you attempt to monitor messages of those windows. In hindsight, I can see this would cause some confusion.&lt;/p&gt;
&lt;p&gt;If you are unsure, you can check if an application is 32 or 64 bit by using something like &lt;a class="" href="https://wj32.org/processhacker/" rel="nofollow"&gt;Process Hacker&lt;/a&gt;. If you hover the mouse over a process, it will say if it is 32 bit.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">xtal256</dc:creator><pubDate>Mon, 21 Jan 2019 04:52:47 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net3b6200686a4187baf525ef3df9442fed0c6ef4fc</guid></item><item><title>Can't monitor window messages</title><link>https://sourceforge.net/p/windowdetective/bugs/14/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I've tried attaching the window messages monitor to numerous windows, but I can't seem to get a single window message to be logged.&lt;/p&gt;
&lt;p&gt;I tried running as administrator, monitoring apps stared after detective is started, clicking the start/stop capture button, looking at the filter settings, nothing seems to work.&lt;/p&gt;
&lt;p&gt;The log looks clean. It says it got debug permission just fine.&lt;/p&gt;
&lt;p&gt;Windows 10 Home&lt;br/&gt;
Window Detective 3.5.1&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Charlie Hayes</dc:creator><pubDate>Mon, 21 Jan 2019 01:41:21 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netbaccbd86c8684ff3667c23cc543f171a42194bdb</guid></item><item><title>#13 Crash when stopping message capturing</title><link>https://sourceforge.net/p/windowdetective/bugs/13/?limit=25#4f24</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Ah, I have been able to reproduce now. I was previously trying on Windows 7, but when I used Win 10 like you have, I was able to see it crash pretty quickly.&lt;/p&gt;
&lt;p&gt;I only have my development tools on a Win 7 machine, so it will make debugging difficult. But I'll try to investigate some time soon.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">xtal256</dc:creator><pubDate>Wed, 22 Aug 2018 01:13:35 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netca39d71af327d8cda22a2cad2ffe35fa799d3f5f</guid></item></channel></rss>