Thank you guys for quick reply.
But I was probably not clear enough with the question.

I do understated the concept of setting panel description via GetDDescription() callback.
I already did the checks for whether it is request for full description of just single id.
As it is listed in the example below (it is member function of C4dControls class from previous snippet ):

void C4dControls::AddIntChoice(int id, int gid, const String& name, const BaseContainer& items)
{	
	const DescID cid = DescLevel(id, DTYPE_LONG, 0);
	//---------------------------------------------------------------------
	if (ex_descr && (!ex_singleid || cid.IsPartOf(*ex_singleid, nullptr)) )
	{
		BaseContainer bc = GetCustomDataTypeDefault(DTYPE_LONG);
		//---------------------------------------------
		bc.SetInt32	(DESC_CUSTOMGUI, ID_QUICKTABSRADIO_GADGET);
		bc.SetString(DESC_NAME, name);
		bc.SetInt32	(DESC_SCALEH, 1);
		// animate OFF
		bc.SetInt32	(DESC_ANIMATE, DESC_ANIMATE_OFF);
		//---------------------------------------------
		bc.SetContainer(DESC_CYCLE, items);
		//---------------------------------------------
		ex_descr->SetParameter(cid, bc, DescLevel(gid));
	}	
}

But it is still calling to rewrite each control description several times after any event in GUI.
What confuses me the most, is that each series of calls is with the different pointer to description (Description* description)
For example there are five different pointers to description when ToolData::GetDDescription() is executed for the same event. (after mouse click into attribute manager)

Is this the way how it really works?
There are more versions of description for the same panel, and all of them have to be initialized repeatedly after each event?

Thanks!
Viktor

Hi,
I have a questions about behavior of ToolData class member function GetDDescription().
I can't find any example and I don't understand why Cinema is calling this function several times after each user event in GUI.

Below is the code of overridden member function.
I am filling description with controls every time now. (function LoadControls())

Bool LwCadToolData::GetDDescription	(BaseDocument* doc, BaseContainer& data, Description* description, DESCFLAGS_DESC& flags)
{
	// validation
	if (description == nullptr)		return false;
		
	ApplicationOutput("GetDDescription flags: @", flags);

	// initialize controls	
	LoadControls(C4dControls(description, description->GetSingleDescID()));

	// controls loaded into tool description
	flags |= DESCFLAGS_DESC::LOADED;

	//---------------------
	// base
	return SUPER::GetDDescription(doc, data, description, flags);
}

Problem is that after each mouse event , this function is executed several times, always a different description pointer.
Below is the list of calls after a single click.

GetDDescription flags: NONE
GetDDescription flags: NONE
GetDDescription flags: NONE
GetDDescription flags: NONE
GetDDescription flags: RESOLVEMULTIPLEDATA|MAPTAGS
GetDDescription flags: NONE

Could you please give me a hint, how to optimize this properly?
Optimal way is to fill description only once.
Is it necessary fill it every time the GetDDescription() function is executed?

Thanks!

Works like a charm!
It's much more flexible than I hoped;)

Thanks a lot!

I am trying to draw colored text with BaseDraw::DrawHUDText().
Using BaseDraw::SetPen() before, has no effect.

Is there any way to draw text with custom color using DrawHUDText funcrtion ?

Thanks!

@m_magalhaes
Thanks Manuel!

When I fill-in only Inner edges in NgonBase::BuildNgon, then it surprisingly works ;)
I don't know why I tested all combinations except this one :)
There are still some minor glitches, some inner edges are randomly not hidden, but ngons created are valid for all the cases I have tested.
Random glitches are easily fixable with forcing all inner edges to be hidden.

I will test it more, but this seems to be reliable for now.
NGONS import - read outer edges directly from Pgon::*m_Edge array
NGONS export - with NgonBase::BuildNgon(), filling Inner edges only, and force hide inner edges on quads.

Thanks a lot Manuel,
Your help has been very valuable to me.

Regards,
Viktor.

@m_magalhaes
I'll wait for what you get from your team.
Thanks Manuel!

Thanks I'll wait of course.
Viktor

Hey guys.
I spent almost two weeks to get stuck with this.
I would really appreciate any reply to this problem.

Just need an answer to these questions:

1. Is NgonBase::BuildNgon() function intended to use for creating ngons with holes from the triangles ?
2. If yes, are there any restrictions or rules for triangles provided ?

Please anybody, can you give me a hint?

I spent a week trying to rewrite our plugin to valid ngons.

I have Mesh already triangulated, uv mapped, I only need to add ngons for existing triangles.

Modeling class doesn't have an option to create ngons low level with already existing triangles.
NgonBase::BuildNgonFromPolys deosn't create holes therefore is useless. Also it is incorrectly documented!
NgonBase::BuildNgon is creating valid ngons but only for specific simple cases. Also insufficiently documented.

I did a brute force of testing all possible combinations how to use NgonBase::BuildNgon(), but it would be much easier if documentation would be a bit more comprehensive.

I am setting the both inner and outer arrays. Simple cases works, but problems starts when ngon has a two and more holes.
In this case, there are the triangles with all three edges hidden .
This seems to be a problem, even if ngon is created, and it passes the validation check, but the result is still broken.

I can post simple examples which are giving errors, but before I do, please let me know is BuildNgon function really works with arbitrary triangles and multiple holes cases?

Thanks!

So my problem was actually not related to OSX but to compatibility issues between minor releases.
Thanks to your replies I sorted it out.
And I finally understand your versioning concept.

Thank you Manuel, good job!

Regards,
Viktor Veličko WTools3D s.r.o.
www.lwcad.com