Looking Forward to Window Clippings 3: Popups

Continuing my look at some of the highlights in the upcoming Window Clippings 3 release, today I want to share some of what I’ve done to improve support for capturing popups.

Basically you should expect far better support for capturing different types of popups. Previous version of Window Clippings did a good job of capturing standard popups such as tooltips and standard menus, but it failed with applications that used non-standard menus and popups such as those from WPF applications.

The good news is that this is no longer a problem and Window Clippings 3 can easily handle many more types of popups.


That’s it for today. Stay tuned for more highlights from the upcoming Window Clippings 3!

Check out the other highlights:

8 thoughts on “Looking Forward to Window Clippings 3: Popups

  1. asf

    It would be cool if you shared some more technical details about the changes in v3. DWM vs classic. How do you know this is a menu etc

  2. John Schroedl

    Have you tried wc3 with Stardock’s Fences in use? I *think* wc2 went bad for me once I started using Fences (ie. inability to select individual windows any more — always selects whole desktop now).

    I am waay too addicted to Fences to ever go back though so I’d love it if you could try it out once before wc3 goes live… pretty please!


      1. John Schroedl

        I just experimented more and I have to exonerate Stardock. It seems that this is only a problem with the main window of our app which I needed to take lots of clips of this week.

        Oddly, other windows in our app work fine with wc2.

        It’s a pretty standard WPF-based window so I have no idea why wc2 cannot select it. I do have the popups issue you mention in this post for our other windows so I’m psyched to see that’s improved.

        If there’s anything I can tell you about our main window to diagnose the issue, Spy++, Snoop, etc. let me know. I’d love to have WC work everywhere in our app.


      2. John Schroedl

        Sorry to steal the comments into bug triage but I think I see the culprit: Telerik RadDocking

        I can send you a test app to repro the problem if you like. The 30-day trial of RadControls for WPF would be needed to build/run if you don’t already have a license.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s