Activity for xtal256

  • xtal256 xtal256 posted a comment on ticket #15

    There seems to be a taskbar button and/or Glass/Aero frame with stale background and that's it. 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. 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!

  • xtal256 xtal256 posted a comment on ticket #15

    Have you tried refreshing the Window Detective tree (Green button in the toolbar, or menu View > Refresh)? Whilst Window Detective can track the creation and destruction of windows and automatically update the tree, it does not always see new windows. 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 EnumChildWindows function to get all child windows of the desktop. I don't know if it's possible for PMM to show...

  • xtal256 xtal256 posted a comment on ticket #7

    The last time I build it would have been with VS 2010, so there's probably a lot that has changed. But from the look of that screenshot, "CL.exe" (the compiler/linker) cannot be found. So perhaps something is wrong with the installation or paths. Try googling the error.

  • xtal256 xtal256 posted a comment on ticket #3

    Thanks for using Window Detective. I have not worked on it in a long time, but I will consider your request if I ever pick it back up again. For the moment, you can see the number of immediate children (i.e. not including children of children) if you hover your mouse over a window in the list. Not sure how helpful that would be to you.

  • xtal256 xtal256 posted a comment on ticket #14

    I've planned to do it for a while now, but I never got around to it. Been too busy with other stuff.

  • xtal256 xtal256 posted a comment on ticket #14

    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. 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. If you are unsure, you can check if an application is 32 or 64 bit by using something like Process Hacker....

  • xtal256 xtal256 posted a comment on ticket #13

    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. 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.

  • xtal256 xtal256 posted a comment on ticket #13

    Yes, I suspected that might have been the case. I've definitely encountered bugs like this before, but they are difficult to debug because they are so rare/intermittent.

  • xtal256 xtal256 posted a comment on ticket #13

    Thanks for the detailed information and stack trace. I tried for a bit in Thunderbird but could not reproduce. Were you able to reproduce consistently, or was it intermittent?

  • xtal256 xtal256 modified a comment on ticket #2

    Try uninstalling and then installing again. The installer should create the registry keys, then WD will use them. If the parent key does not exist when WD starts up, then it will not create it and not save any settings. I can't quite remember why I did this (so perhaps it's not a good idea), but it might have been to allow portable installs that don't touch the registry. I think I was going to make it use an ini file instead, but never got around to it.

  • xtal256 xtal256 posted a comment on ticket #2

    Try uninstalling and then installing again. The installer should create the registry keys, then WD will use them. If they keys do not exist when WD starts up, then it will not create them and not save any settings. I can't quite remember why I did this (so perhaps it's not a good idea), but it might have been to allow portable installs that don't touch the registry. I think I was going to make it use an ini file instead, but never got around to it.

  • xtal256 xtal256 modified ticket #2

    Let WD remember last window size and position on screen

  • xtal256 xtal256 modified a comment on ticket #12

    I cannot reproduce. I assume this is what you are referring to: Are you on the latest version of WD (3.5.1)? Does Office crash immediately after you open the VB editor, or shortly after? Does it happen every time? Can you please get the crash dump and attach it here or email it to me. If it's too big we'll have to find a hosting service to upload it to.

  • xtal256 xtal256 modified a comment on ticket #12

    I cannot reproduce. I assume this is what you are referring to: Are you on the latest version of WD (3.5.1)? It would be useful if I could get the crash dump, but I will continue to try and reproduce.

  • xtal256 xtal256 modified a comment on ticket #12

    I cannot reproduce. I assume this is what you are referring to: Are you on the latest version of WD (3.4.0)? It would be useful if I could get the crash dump, but I will continue to try and reproduce.

  • xtal256 xtal256 posted a comment on ticket #12

    I cannot reproduce. I assume this is what you are referring to: It would be useful if I could get the crash dump, but I will continue to try and reproduce.

  • xtal256 xtal256 posted a comment on ticket #11

    Thanks for raising. I will need to do some work to ensure that Window Detective correctly handles different DPI / scale.

  • xtal256 xtal256 modified ticket #10

    Crash when capturing messages

  • xtal256 xtal256 posted a comment on ticket #10

    Cool. I will release a new version with the fix shortly. You should revert the changes you made to the data_types.xml file now, the new version will be different.

  • xtal256 xtal256 modified a comment on ticket #10

    Ok, I think I know what's going on. I changed one of the names in data_types.xml ("uint" became "uint32") but I forgot to change it in the code. So it was trying to use a type that didn't exist. I will fix this soon, but can I get you to do something to validate the fix? Go to where Window Detective is installed (i.e. "Program Files") and open the data_types.xml file under the data directory. In it, near the top, you will see a bunch of lines that say "primitive". Look for the one that has name="uint32",...

  • xtal256 xtal256 modified a comment on ticket #10

    Ok, I think I know what's going on. I changed one of the names in data_types.xml ("uint" became "uint32") but I forgot to change it in the code. So it was trying to use a type that didn't exist. I will fix this soon, but can I get you to do something to validate the fix? Go to where Window Detective is installed (i.e. "Program Files") and open the data_types.xml file under the data directory. In it, near the top, you will see a bunch of lines that say "primitive". Look for the one that has name="uint32",...

  • xtal256 xtal256 posted a comment on ticket #10

    Ok, I think I know what's going on. I changed one of the names in data_types.xml ("uint" became "uint32") but I forgot to change it in the code. So it was trying to use a type that didn't exist. I will fix this soon, but can I get you to do something to validate the fix? If you go to where Window Detective is installed (i.e. "Program Files") and open the data_types.xml file under the data directory. In it, near the top, you will see a bunch of lines that say "primitive". Look for the one that has...

  • xtal256 xtal256 posted a comment on ticket #10

    No, I can make a debug build myself. I just need to get the right debug dlls of Qt otherwise it won't run.

  • xtal256 xtal256 posted a comment on ticket #10

    Remote debugging didn't turn up anything useful, and my development machine is Win 7, so I can't use that. Going to be difficult to determine the cause :(

  • xtal256 xtal256 posted a comment on ticket #10

    I have been able to reproduce the crash fairly consistently on Windows 10, and am now trying to debug.

  • xtal256 xtal256 posted a comment on ticket #10

    I suspect this is because Window Detective tries to access data from a window that has been destroyed. Does it happen to you often?

  • xtal256 xtal256 posted a comment on ticket #9

    The default language is not Greek, it's English. Perhaps you accidentally selected Greek when installing. If you think it's a bug then I will investigate, otherwise I'll close this issue.

  • xtal256 xtal256 posted a comment on ticket #2

    Window Detective does currently have this feature. It will remember the size and position of most, if not all, of it's own windows. It writes the settings to the Windows registry, perhaps the application cannot write to it for some reason. Run regedit.exe and look for the entry "HKEY_CURRENT_USER\Software\Window Detective\Window Detective\smartSettings". If that is not there, then your settings have not been remembered. Additionally, Window Detective uses a feature I call "smart settings", which...

  • xtal256 xtal256 posted a comment on ticket #9

    It seems you have the Greek language in use. Window Detective does not use the language set in the operating system (although that would be a good idea), it loads a language file from it's own installation directory. Look for a file with the .qm extension. You should find one called "el_GR.qm". Delete that file, and any other .qm files, and Window Detective should run using English. Did you download it from this site (SourceForge), or another site that offers "portable" applications? If the later,...

  • xtal256 xtal256 modified ticket #8

    Unable to save window messages

1