You cannot assign shortcuts to buttons.
An alternative solution (which I have used in the past) is to create a CommandData plugin for each button, and let the CommandData::Execute call the button. Or instead of a CommandData plugin you could also create a separate script for each button.
Either way, these can then be assigned a shortcut.

If I remember correctly we did discuss the other way (from CommandData to ToolData) quite a while ago (see https://plugincafe.maxon.net/topic/10044/13513_using-objectmessage). But I guess using this same technique could still be applicable to your current request.

Most important is to understand that a CoreMessage is not captured by a ToolData. This type of message can only be captured by a MessageData plugin, where you then could "translate" it into a message that actually is sent to the ToolData.

What I have been successful in using is, performing following from the "transmitter":

BasePlugin* tool = FindPlugin(TOOL_PLUGIN_ID, PLUGINTYPE::TOOL);
if (tool)
	tool->Message(TOOL_MSG_PREPAREDATA);

Where TOOL_PLUGIN_ID is the plugin ID of the ToolData, and TOOL_MSG_PREPAREDATA is a custom defined message, using a unique plugin ID.

And then using following in the "receiver" ToolData:

Bool MyToolData::Message(BaseDocument *doc, BaseContainer &data, Int32 type, void *t_data)
{
	if (type == TOOL_MSG_PREPAREDATA)
	{
		PrepareData();
	}

	return DescriptionToolData::Message(doc, data, type, t_data);
}

@bentraje said in Bug on GetActiveObjects() on R20.057?:

objSel = doc.GetActiveObjects(c4d.GETACTIVEOBJECTFLAGS_SELECTIONORDER)
print objSel[0]
print objSel[1]

Works fine by me.

I have a cube and a plane primitive. With the two selected, I get a printout for both. No out of range.
Running 20.057 (on Windows).

<c4d.BaseObject object called 'Plane/Plane' with ID 5168 at 0x0000004C44847570>
<c4d.BaseObject object called 'Cube/Cube' with ID 5159 at 0x0000004C448476D0>

When I only select a single object then I get an out of range (obviously):

IndexError: list index out of range

EDIT:
Hang on, when I make one the child of the other and have both selected, I do get an out of range.
But this is obvious, since your active objects flag doesn't mention children. As such, you do only have a single parent object selected.

To take children into account as being detected as selected, you need:

 objSel = doc.GetActiveObjects(c4d.GETACTIVEOBJECTFLAGS_SELECTIONORDER | c4d.GETACTIVEOBJECTFLAGS_CHILDREN )

spam frenzy all over again, lately.

I have been in need of something similar as well. And if I remember correctly it has been discussed a few years ago.
Reason is that a ToolData or DescriptionToolData might need to initialize some stuff depending the currently active object. When the user selects a different object in the ObjectManager, the ToolData might need to reinitialize some stuff.

The solution proposed in the past was to use a MessageData and listen to EVMSG_CHANGE to check if a different object has been selected using the object's "unique" id and then trigger the ToolData by sending a SpecialEvent ... or something.

It is quite a complex implementation that seems to work, but probably is very error prone.
I wish we would have had some kind of message telling the active object selection was changed (from inside the ToolData), not via-via. And definitely not using such a hacky and complex solution.
It has been a while, but I seem to remember that the whole use of the object's unique id was rather flawed as the id didn't exactly seem to be that unique after all.

Anyway, I am still hoping for a nice solution to detect when user changes the current active object. But it seems to not be possible after all.

I am less active since a few months, and this will probably not change any time soon, but let that not restrict me for sending Best Wishes for 2021 to everyone of the SDK team.
Not only to those more present and visible in the forums, but also to those behind the scenes that keep everything running.

Thank you for your 2020 support and best wishes for 2021.

You need to obtain the tool's data in order to be able to modify/set it.
The callcommand just activates the tool.

import c4d

def main():

    # activate the command
    c4d.CallCommand(1019952)

    # change its settings
    nTool = c4d.plugins.GetToolData(doc, 1019952)
    nTool[c4d.ID_CA_JOINT_NAMING_REPLACE] = "_L_"
    nTool[c4d.ID_CA_JOINT_NAMING_REPLACE_WITH] = "_R_"

# Execute main()
if __name__=='__main__':
    main()

In the above code "nTool" is a BaseContainer, that won't work.

I also found the following in the legacy forum

import c4d

def main():
    
    toolID = 1019952
    c4d.CallCommand(toolID) 

    tool=c4d.plugins.FindPlugin(toolID, c4d.PLUGINTYPE_TOOL)  
    tool[c4d.ID_CA_JOINT_NAMING_REPLACE] = "_L_" 
    tool[c4d.ID_CA_JOINT_NAMING_REPLACE_WITH]= "_R_"
    c4d.CallButton(tool, c4d.ID_CA_JOINT_NAMING_REPLACE_APPLY)  
    
    c4d.EventAdd()

Another take on modifying the settings, since the "tool" returned from FindPlugin is a BasePlugin which is derived from BaseList2D, exactly what we need for the CallButton

The geometry of an object is stored in hidden tags (points and polygons, namely)
These are not visible, nor selectable ... and thus can theoretically not be deleted by user. But you still can access these via Python, or C++. As such, when removing all tags you also remove critical ones, that are needed by the object in order to exist.

import c4d

def main():
    c4d.gui.ActiveObjectManager_SetObject(c4d.ACTIVEOBJECTMODE_OBJECT, op, 0, c4d.ACTIVEOBJECTMANAGER_SETOBJECTS_OPEN)

if __name__=='__main__':
    main()

MSG_DOCUMENTINFO_TYPE_SAVE_BEFORE
-> Document is about to be written.
MSG_DOCUMENTINFO_TYPE_SAVE_AFTER
-> Document was saved.

@m_magalhaes
At the moment I am using R20.

Here is some example code of what I mean:

# Python 2.7
import c4d
from c4d import plugins
from c4d import bitmaps
import os

CMD_PLUGIN_ID = 1000001
TRIGGER_PLUGIN_ID = 1000002

kBaseMessageID = c4d.ID_TREEVIEW_FIRST_NEW_ID;
kTriggerMessageID = kBaseMessageID + 1
kAnotherTriggerMessageID = kBaseMessageID + 2
# ... etc

# =============== CommandData class =============
	
class TestCommandData(c4d.plugins.CommandData):
	
	def Execute(self, doc):
		return True
		
	def ExecuteSubID(self, doc, subid):
		if subid == kTriggerMessageID:
			# we got triggered .. do something
			print "TestCommandData was trigger for ", subid
		return True

class TriggerCommandData(c4d.plugins.CommandData):
	
	def Execute(self, doc):
		print "TriggerCommandData calls TestCommandData.ExecuteSubID with value", kTriggerMessageID
		c4d.CallCommand(CMD_PLUGIN_ID, kTriggerMessageID)
		return True
		
# =============== Main =============
		
def PluginMain():
	bmp = c4d.bitmaps.BaseBitmap()
	dir, file = os.path.split(__file__)
	fn = os.path.join(dir, "res", "test.png")
	bmp.InitWith(fn)
	plugins.RegisterCommandPlugin(
		id=CMD_PLUGIN_ID,
		str="TestCommand",
		info=0,
		icon=bmp, 
		help="TestCommand",
		dat=TestCommandData())
	plugins.RegisterCommandPlugin(
		id=TRIGGER_PLUGIN_ID,
		str="TriggerCommand",
		info=0,
		icon=bmp, 
		help="TriggerCommand",
		dat=TriggerCommandData())

	return
		
if __name__ == "__main__":
	PluginMain()

The above registers 2 CommandData plugins: "TestCommandData" and " TriggerCommandData".
When you select the "TestCommandData" from the plugin menu -> nothing happens.
When you select the "TriggerCommandData" it will call the "TestCommandData" with a subid.
This mimics sending the CommandData a message.
In TestCommandData.ExecuteSubID you then react to the particular "custom message ID". You can have as many of these as you want, and can react differently to each.

NOTE: the source of the trigger does not need to be another CommandData, it can be anything you like. The only thing you need to do is to perform a c4d.CallCommand(<pluginid>, <trigger-messageid>) from where you want to trigger your CommandData, and provide the trigger-messageid you want the CommandData to react on.

Now, if you also want to pass data ... that's another story, indeed.
Maybe have a look at c4d.SpecialEventAdd (but I guess this is a CoreMessage which does only get sent to MessageData type of plugins)

@césar-vonc said in Send Message to CommandData:

Mm, it did not work for me, the message was still not triggered ...

Sorry to have confused you.
The solution I mentioned was not to trigger the Message function of a CommandData. But the explicitly call its ExecuteSubID.

@constantine_sazonov
You will want to use

 BaseView.WS(self, p)

Converts p from world space to screen space (pixels relative to the view)

Or maybe better: Camera to screen conversion

BaseView.CS(self, p, z_inverse)

Not sure if this the reason but according to the documentation the Message from CommandData responds to messages of type MSG_COMMAND. Since you're sending a message with type 123, I can only imagine the CommandData does not react to this type of message.

What I have done in the past to trigger a CommandData is use the ExecuteSubID.
I define a value for a custom message, making sure to use a value higher than ID_TREEVIEW_FIRST_NEW_ID
and perform a CallCommand(<command-pluginID>, <custom-message-value>).
In the CommandData I then react to the specific custom-message-value passed in ExecuteSubID.
Granted, there might be other workarounds to message a CommandData, but the way I have done worked for me.

Note: Make sure to use a value higher than ID_TREEVIEW_FIRST_NEW_ID in order not to conflict with internal values defined for menus and handled in the CommandData GetSubContainer

@ferdinand
We are indeed talking about the little bell icon with a number next to it.

The strange thing is (as mentioned earlier as well) is that the unread icon does show up with a number of new unread posts. So, some of the notifications are working. Just not the bell icon.

When I re-enable a notification in the dropdown of the bell icon, I do see the number show up.
I noticed just recently that when I am currently looking at the forum page and someone replies, the number do show up. But without reading the posts, nor doing any actions and I leave the page, then come back to the forum ... the number on the bell icon is gone. Still the dropdown of the bell icon shows the list of notifications with a black circle next to it. Indicating that the replies have not been read yet.

I don't have any content, script, or ad blocker. All was working fine with previous plugincafe.
I have tried with Microsoft Edge (which isn't my default browser), and have exactly the same issues there. The number on the icon bell isn't displayed.
To me this sounds like it isn't browser related.
Do I have some setting in my account which causes this - no idea?
As said, all worked fine with previous plugincafe, and as far as I remember I haven't changed anything in my account settings since the switch.

Might I make a suggestion for the search functionality?

There is the option to show the result of a search as posts or as topics.
I am fine with the "topics" option only showing the topic title.

However, when one uses the "posts" option it would be quite useful to limit the post to -let's say- the first 10 lines.
If the post contains a lot of code, I don't want to see all this in the search result.

To illustrate my point:
try a search on "bitmapbutton array" and choose "posts" as result option ...

The first topic will probably be:
DDesc BitmapButtons when changed
and you will need to scroll quite some time to get to the second topic:
BitmapButton image change works in R13 but not R14
which also is a lengthy post on itself.
... and so on and so forth.

Could there be a way to limit the number of text shown per post? Or at least exclude any code (or collapsing that code) when listing the search result.

Thanks in advance.

@m_adam
Unfortunately no notification counter to be seen this time around.

@ferdinand
So, I have cleared all caches of my browser. Now it's waiting for a reply in order to see if the notification pops up.

In the meantime here's some info:
Windows 10 Home, version 10.0.19041.906
Firefox 88.0.1 (64bit)