topic XViewChecker.displayResults does not respect 'type' parameter in 3ds Max Programming Forum

XViewChecker.displayResults does not respect 'type' parameter

Anonymous — Tue, 23 Jun 2015 13:20:36 GMT

the XViewChecker.displayResults has 6 parmaters as it expressed in docs:

<void>xViewChecker.displayResults <color>color <time>time <node>node <HWND>hwnd <enum>type <&index array>results 

type enums: {#Failed|#Vertices|#Edges|#Faces} 
results is In and Out parameter 

Displays the results of the current Checker. This method can be used inside a custom displayOverride function to change the default checker display appearance, for example the colors to use, or what sub-object elements to highlight.

But it apperas the it competely ignores the <enum>type parameter. Regardless to the value passed in there #Edges or #Vertices, 2 or 1 - it draws faces in the viewport.

What is the issue? Is it a bug?

Re: XViewChecker.displayResults does not respect 'type' parameter

Anonymous — Tue, 23 Jun 2015 15:27:09 GMT

yes, it's dumb bug in

void IGeometryCheckerManager_Imp::DisplayResults_FPS(Color *c,TimeValue t,INode *node, HWND hwnd,int type,Tab<int> &indices)

the 'break' is missing in each 'case' statement:

switch(type)
	{
	case 0x0:
		returnval = IGeometryChecker::eFail;
	case 0x1:
		returnval = IGeometryChecker::eVertices;
	case 0x2:
		returnval = IGeometryChecker::eEdges;
	case 0x3:
		returnval = IGeometryChecker::eFaces;
	}

so returnval is alwasy eFaces. This is present in 2015 - does anybody know that it's fixed in 2016?

Re: XViewChecker.displayResults does not respect 'type' parameter

Nepre — Mon, 20 Aug 2018 21:12:03 GMT

Still in 2019

Re: XViewChecker.displayResults does not respect 'type' parameter

graeme.palmer — Mon, 03 Oct 2022 18:33:28 GMT

This seems to still be an issue in 2023 - ".supportedCheck #Edges" is returning only faces in viewport.

Is there a workaround to this please?