MFC SIP keyboard causing a redraw - what am I missing?

This is a Windows Mobile app.

I have a screen that has a textbox at the top. The text box is for typing search strings. Through the SETFOCUS and KILLFOCUS events, I have implemented a "zoom" feature. When the user clicks in the box or otherwise starts typing while on this screen, the box zooms to triple size/font, and then returns to original size when user clicks out of the edit box or another event happens that causes the edit to lose focus.

Everything works well, except for one case: toggling the SIP keyboard causes the edit to be redrawn and it is redrawing with the original dimensions rather than the zoomed dimensions. When this happens, the font is still the zoomed size, but the edit is the original size and the only way to "clear" the problem is to tap out of the editbox (to kill focus) and then tap back in.

So it is not losing focus when this happens, but apparently my way of modifying the size is missing something.


// On Focus - zooms
      CRect rc(0,0,0,0);
      searchVal.GetWindowRect(&rc);
      searchVal.SetWindowPos(NULL, 0, 0, rc.Width(), rc.Height()*2 - SCALEX(5), SWP_NOMOVE|SWP_NOZORDER);
      searchVal.SetFont(&theApp.largeFont, 1);
      searchVal.BringWindowToTop();

// Kill focus, unzooms to original
      CRect rc(0,0,0,0);
      searchVal.GetWindowRect(&rc);
      searchVal.SetWindowPos(NULL, 0, 0, rc.Width(), (rc.Height()+SCALEX(5))/2, SWP_NOMOVE|SWP_NOZORDER);
      searchVal.GetWindowRect(&rc);
      searchVal.SetFont(&theApp.smallFont, 1);


Can anyone spot what I am missing?
LVL 40
mrjoltcolaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

alexey_gusevCommented:
look into the following messages for the dialog :

        case WM_ACTIVATE:
            // Notify shell of our activate message
            SHHandleWMActivate(hWnd, wParam, lParam, &s_sai, FALSE);
            break;
        case WM_SETTINGCHANGE:
            SHHandleWMSettingChange(hWnd, wParam, lParam, &s_sai);
            break;

when SIP is on/off, your windows receives one of those (settings change most probably). I remember overriding WM_SETTINGCHAGE [basically doing nothing there].
0
mrjoltcolaAuthor Commented:
1) How can I do this with the MFC message map?

2) I don't quite follow here. The SIP activate/deactivate is triggering a component to redraw with its original dimensions, but it is not triggering a focus event. So with your suggestion, what should I do with those messages? Ignore them? Are you saying that possibly the dialog is redrawing on this event? If so, why would it use the original component dimensions.
0
alexey_gusevCommented:
1) ON_WM_SETTINGCHANGE()
2) try to ignore this above message, I've used something like that:

void CBaseDlg::OnSettingChange(UINT uFlags, LPCTSTR lpszSection)
{
      if(uFlags==224) // <-- here is some experimental value = SPI_SETSIPINFO
            return;

      CWnd::OnSettingChange(uFlags,lpszSection);
}

what happens if you simply add some eg static control  to your form and give it TOOLWINDOW style (so it doesn't grab the focus from editbox) - and in the click handler call Invalidate() to the dialog?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Rowby Goren Makes an Impact on Screen and Online

Learn about longtime user Rowby Goren and his great contributions to the site. We explore his method for posing questions that are likely to yield a solution, and take a look at how his career transformed from a Hollywood writer to a website entrepreneur.

mrjoltcolaAuthor Commented:
Ok, I am getting the general idea. So can I ask, why can't I just handle an ON_SIZE event for the component so I can draw it in its current "zoomed" state?

0
alexey_gusevCommented:
well, you could try, though I'm not sure it will work as you want, but maybe I didn't get to the bottom of the things :)
I'm not even sure you'll get WM_SIZE in such case, but this you can easily check with Spy++.
0
mrjoltcolaAuthor Commented:
Ok I put the handler in for WM_SETTINGCHANGE and I did not put the if(uFlags == 224), I only overrode the handler to call the base CWnd:: handler. This solved my problem! Now when I toggle the SIP, the zoomed window keeps its position.

So first, thanks! I will close the question.

But, I surely would like to understand the root cause. What is actually happening here? I assume searchVal.SetWindowPos() is not a permanent thing, and the the ONSIZE event (is that the event?) is causing the form to redraw with original settings from the resource file?
0
alexey_gusevCommented:
well, you have your controls defined in the dialog template, and God knows how MFC does a redraw :)

I think you can use Spy++ to observe what messages it receives
0
mrjoltcolaAuthor Commented:
I don't understand the issue fully, but this solved my problem. Thanks.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Smartphone Programming

From novice to tech pro — start learning today.