Hello Wlad,

a) Here it is:

Code:
	{
//PISTC_PROCEDUREDEF:
		0,
		PIPD_COMMONTOOL,
		0,

		"IntenseX Action",
		ViewContextMenu"\\IntenseX Action{{behavior",
		NULL,
		NULL,
		NULL,

		& g_ProcDefList [ IDA_CHOOSEACTION],
		ChooseAction_Open,
		NULL,
		NULL,
		NULL,

//PI eigene daten
		FALSE,
		NULL,
		0,
		NULL,
		NULL
	},



The code just does not work on the pop up menu anymore although it works fine on the WED menu. If it makes it easier, the item does indeed gets created as a separator line, so if you actually click on the separator:



the Intense X action window will actually pop up. Btw, the "{{behavior" has absolutely no effect in this case, I get the same result with and without it.


b) Thank you. This code works great. You can't believe how important this function was to me. I just assumed it didn't made it to the new wedsdk cause the newfeatures.txt only mentioned the menu positioning stuff. Thanks again for this!


New Bug c) In a7.07 there was a very useful instruction where you could specify which of your dll menu options you still wanted to be visible even when no level was loaded in WED. Obviously, you could use such a feature to create a new level using your plugin instead of creating it from wed, like such:



This no longer works with A7.50's WED:



Here's the code on the New Intense X Project menu entry:

Code:
		{
//PISTC_PROCEDUREDEF:
		PIFL_MAINFRAMEMENU,
		PIPD_COMMONTOOL,
		0,

		"New IntenseX Project",
		"File\\New IntenseX Project",
		NULL,
		NULL,
		NULL,

		& g_ProcDefList [ IDA_NEWINTENSEXPROJECT],
		NewIntenseXProject_Open,
		NULL,
		NULL,
		NULL,  // p_DoCommandProc

//PI eigene daten
		FALSE,
		NULL,
		0,
		NULL,
		NULL
	},


It was the PIFL_MAINFRAMEMENU command that allowed a menu item to be visible at start, but in A7.50 it does squat

Cheers,
Aris

Last edited by LarryLaffer; 10/31/08 00:51. Reason: c)

INTENSE AI: Use the Best AI around for your games!
Join our Forums now! | Get Intense Pathfinding 3 Free!