Codejock Developer Community : [SOLVED] v15.1.3.0908 SetFocusedRow(NULL)

[SOLVED] v15.1.3.0908 SetFocusedRow(NULL) : I found this too, but it occured...

Wed, 21 Sep 2011 05:18:36 +0000

Author: adrien
Subject: 18930
Posted: 21 September 2011 at 5:18am

I found this too, but it occured when I removed all records from a report. So it's necessary to be able to call CXTPReportSections::EnsureVisible(CDC *pDC, CXTPReportRow *pRow) with pRow = NULL.

e.g. XTPReportSections.cpp line 86


BOOL CXTPReportSections::EnsureVisible(CDC *pDC, CXTPReportRow *pRow)
{
	BOOL bResult = FALSE;
	
	if(!pRow)
		return bResult;

solves the problem for me

[SOLVED] v15.1.3.0908 SetFocusedRow(NULL) : Thanks, fixed.

Fri, 09 Sep 2011 11:20:26 +0000

Author: ABuenger
Subject: 18930
Posted: 09 September 2011 at 11:20am

Thanks, fixed.

[SOLVED] v15.1.3.0908 SetFocusedRow(NULL) : In the newv15.1.3.0908 release...

Fri, 09 Sep 2011 08:24:29 +0000

Author: markr
Subject: 18930
Posted: 09 September 2011 at 8:24am

In the new v15.1.3.0908 release of the XTP report control, I get an immediate crash if I invoke:

GetReportCtrl().SetFocusedRow(NULL);

Support for using NULL in this context was added to 15.1.1 to allow us to clear the currently focused row. The crash occurs because the method signature above calls EnsureVisbile(), which in turn doesn't always check to see if the row is NULL.

This problem can be worked around by instead calling:

GetReportCtrl().SetFocusedRow(FALSE, NULL, FALSE, FALSE);

... which bypasses the attempt to ensure row visibility (and thus avoids the crash).

For long term solution, recommend that CodeJock change CXTPReportControl::EnsureVisible(CXTPReportRow *pRow) method so that it *always* checks for NULL row pointer.