Reply to thread

Message

<blockquote data-quote="DieBagger" data-source="post: 531594" data-attributes="member: 56421">How about GUI messages?You could define a standard set of options that a plugin has to use and maybe provide a sourcefile that implements sending of messages.Something like this:[CODE]&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; GUIMessage msg = new GUIMessage(GUIMessage.MessageType.GUI_MSG_NOTIFY, INFO_SERVICE_ID, this.GetID,&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ParentID, newItemId, someInt, &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; new string[] { &quot;Name of Item&quot;, &quot;Description of item&quot;, &quot;Path to image&quot; });&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; message = new GUIMessage(GUIMessage.MessageType.GUI_MSG_CLICKED, WindowId, GetID, ParentID, 0, 0, null);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; GUIGraphicsContext.SendMessage(message);[/CODE]Your plugin would just have to listen for messages with the given id:[CODE]&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; public override bool OnMessage(GUIMessage message)&nbsp; &nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; if (message.Message == GUIMessage.MessageType.GUI_MSG_NOTIFY)&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {//add item to recently added list&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; return base.OnMessage(message);&nbsp; &nbsp; &nbsp; &nbsp; }[/CODE]I have no idea if this could work or if it would produce any sideeffects (it would probably be better to choose a different id <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />) but it would minimize the effort for plugins (no dlls to include).</blockquote>

[QUOTE="DieBagger, post: 531594, member: 56421"] How about GUI messages? You could define a standard set of options that a plugin has to use and maybe provide a sourcefile that implements sending of messages. Something like this: [CODE] GUIMessage msg = new GUIMessage(GUIMessage.MessageType.GUI_MSG_NOTIFY, INFO_SERVICE_ID, this.GetID, ParentID, newItemId, someInt, new string[] { "Name of Item", "Description of item", "Path to image" }); message = new GUIMessage(GUIMessage.MessageType.GUI_MSG_CLICKED, WindowId, GetID, ParentID, 0, 0, null); GUIGraphicsContext.SendMessage(message); [/CODE] Your plugin would just have to listen for messages with the given id: [CODE] public override bool OnMessage(GUIMessage message) { if (message.Message == GUIMessage.MessageType.GUI_MSG_NOTIFY) {//add item to recently added list } return base.OnMessage(message); } [/CODE] I have no idea if this could work or if it would produce any sideeffects (it would probably be better to choose a different id ;)) but it would minimize the effort for plugins (no dlls to include). [/QUOTE]

Verification