Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6795841
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T18:23:42+00:00 2026-05-26T18:23:42+00:00

I have a very weird behaviour in a screen with a modeless dialog and

  • 0

I have a very weird behaviour in a screen with a modeless dialog and I cannot find a solution.

I open a modeless dialog by clicking on a button in a view. As the dialog is not modal I should be able to click any other buttons in this view while the dialog is opened. But I cannot. In fact I can not place the focus in any control..edits, buttons, etc.

I have check which messages the view is getting and it seems it doesn’t get the WM_LBUTTONDOWN message. But it does get the WM_LBUTTONUP message.

To make things even weirder it just happen in Windows 7 64-bits (no one reported this problem in windows XP and is being used for a long time) and just in some computers. But I cannot find the reason and I don’t have a clue about why it happens in these computers.

Does anybody have a clue? Somewhere to start looking at?

Thanks.

Javier

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T18:23:43+00:00Added an answer on May 26, 2026 at 6:23 pm

    it was a tricky question.
    The problem happened to be in a custom implementation of the dialogs. They draw it’s non-client area with MFC2008 visual styles and when calling OnNcActivate for the visual manager it returned FALSE when Aero and Desktop Window Manager where active. So the dialog was not releasing the control to its child-controls.

    Quite tricky as I said…..I just let you know where was the problem just in case someone somewhere ever have a similar problem. I lost two days trying to figure it out.

    Thanks.

    Javier

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am facing a very weird behaviour. I have the $answer_styles array with some
I have a very weird problem: sometimes when I call nHibernate update to an
I have a very weird problem.. I really do hope someone has an answer
I have a very weird problem in Firefox ( version 3.5.2), and I am
I have a very weird problem with PROLOG. I have used it before, but
I have seen some very weird for loops when reading other people's code. I
I have come across a very weird error. I'm on Solaris 10, using Ruby
This is very weird. I have the following code: Assert.AreEqual(new DateTime(2000, 1, 1), DateTime.ParseExact(2000,
I encountered some very weird behaviour which I think is a bug, but I
I have a very weird problem that I can't understand. This is C code:

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.