Toolkit Pro - CXTPControlEdit & context help conflict

Print Page | Close Window

CXTPControlEdit & context help conflict

Printed From: Codejock Forums
Category: Codejock Products
Forum Name: Toolkit Pro
Forum Description: Topics Related to Codejock Toolkit Pro
URL: http://forum.codejock.com/forum_posts.asp?TID=10427
Printed Date: 15 November 2025 at 1:58am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: CXTPControlEdit & context help conflict

Posted By: Joe19
Subject: CXTPControlEdit & context help conflict
Date Posted: 30 April 2008 at 2:11pm

Using 11.2.2 version of tools. I have a ribbon bar based application. Also using html help. I am trying to setup context sensitive help (user presses the F1 key while on a control, the relevant help section in the help file is displayed).

If I have a CXTPControlEdit control in the ribbon bar and if it has focus and the help file is open the help file becomes unresponsive. The help window will not accept any input. It can be dragged, but not closed.

If the focus is switched to another control the help window behaves correctly. Focus back on the edit control and the help file locks again.

I am able to produce the problem in the exampe SDI Ribbon project.

Replies:

Posted By: Oleg
Date Posted: 01 May 2008 at 2:00am

Hello,

Thanks, I see.

As workaround for now add virtual

virtual void WinHelpInternal(DWORD_PTR dwData, UINT nCmd = HELP_CONTEXT);

...

void CRibbonSampleApp::WinHelpInternal(DWORD_PTR dwData, UINT nCmd )

{

XTPMouseManager()->SendTrackLost();

CWinApp::WinHelpInternal(dwData, nCmd);

}

it will close all popups and kill edit focus befo show HtmlHelp.

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

Posted By: Joe19
Date Posted: 02 May 2008 at 5:14pm

This only partially solved the problem. This works in when tne initial F1 key is pressed. However if you change focus back to the edit control in the application the problem comes back.

This is a minor enough issue I'll be happy if you can resolve when you do your next toolkit update. Workaround is of little priority. Thanks,