@m_adam said in First Time calling SetAction does show the Brush tool's AM:

And I did test only on R21 so be sure to check again because I wasn't able to reproduce as you said with default layout in R21.

Cheers,
Maxime.

I am using R21.207 and with default layout see the brush tool in the AM (identical to what happens with R20.059). For safety, I have now tested your solution on R21 and works as expected.

This works:

		const Int32 currentMode = doc->GetMode();
// only change mode if current one is different from Mpoints, Medges, Mpolygons or Mpolyedgepoint
		doc->SetMode(Mpoints);
		doc->SetAction(MYTOOL_PLUGINID);
		GeSyncMessage(EVMSG_TOOLCHANGED, MYTOOL_PLUGINID);
		doc->SetMode(currentMode);

Thanks for the hint.

EDIT:
FYI, note that I have only tested this solution on R20, not R21, but I assume it will behave identical.

@m_adam said in First Time calling SetAction does show the Brush tool's AM:

First of all this issue appears only if you are in BodyaPaint Layout mode.

Nope!
I am simply starting the application in its default state. The default startup layout, with the default move tool selected.

However, I agree that in the default state the Object Model mode is active So, if I indeed perform a mode change to set it to points (probably also edges or polygons will work) I can see the SetAction bringing the expected tool settings in the AM.
So, this might be a solution:

1. Switch mode to points/edge/polygon
2. SetAction
3. Switch to orginal mode

Hi again,
It is not my intention to bump this topic every other day, but I just want to know if a response from devs is still in the pipeline.

So far, it seems that with R21 the obtained mouse coordinates are valid as long as the mouse pointer is hovering over the main Cinema application window. Once outside of that window the obtained coordinates are that of the last position inside the window.
This means that when the application is not full screen, or when multiple monitors are involved the coordinates outside of the window are useless. Most important is that one cannot find out if the mouse cursor is inside or outside the window and thus decide (or know) the obtained values are useless.

This isn't an issue with R20.

On the other hand, as far as I have understood with the release of S22, there will be no further service packs for R21. Which means any fix to this issue (if provided) will be S22 or R22.
Which brings me to the inevitable decision that I will need to ditch any further development for R21. There just are too many unresolved open issues for any of my current (and work-in-progress) plugins.

As discussed here going from unique edge index to global edge index (polygon * 4 + polygon side) is not possible. You are better of working with global edge indeces to start with ... I have learned that the hard way.

@zipit
I did try to activate a tool when initializing the plugin ... didn't make any difference.

But to answer your actual question, I just tried the following:

		doc->SetAction(ID_MODELING_ROTATE);
		doc->SetAction(ID_MODELING_MOVE);
		doc->SetAction(myPluginID);

Sadly, no difference, the brush tool still gets shown into the AM.

I am not sure about the dirty state, and I am not familiar with generator object, but I have used NodeData::GetDDescription and NodeData::GetDParameter in the past to show data in the Attribute Manager.
Additionally, you can use NodeData::GetDEnabling to disable (grey-out) the necessary gadget making it readonly.

@m_adam
Sorry to say but CallCommand is not an option, as in my specific case the DescriptionTool I want to activate is a hidden plugin, and CallCommand cannot execute hidden ones.
I understand the fact that CallCommand cannot call hidden plugins, and I don't assume this to be a bug. But if SetAction is an issue to use, and CallCommand doesn't execute as expected ... then what is one supposed to use?

Please use the Markdown to list your code, as mentioned here (link = https://plugincafe.maxon.net/topic/10953/how-to-post-questions). It's easier for anyone to look at your code in your topic, instead of following a link. Thanks.

@m_magalhaes said in Mouse positions and screen dimensions:

But no news :)

Thanks for the update. I guess no news is good news ...