lklo
Industrial
- Nov 24, 2010
- 226
Hi -
I'm a little challenged these days, because I'm not fully aware how a small mechanism in NX works..
It is regarding how the parameter ACTIONS is handled in a menu file (*.men)....
I have created a lot of menu files in the past - and always the ACTION parameter is pointing to the *.dll (custom application)...works very well..
Then I saw in the 3Dconnexion plug-in - there is also a *.men file placed in the startup folder for this plugin...
But there is only one .*dll file - but there are 3 button sections in the menu file....each of them have the parameter ACTIONS defined.
But I wonder how these parameter is handled....?
Does NX look inside the *.dll and search for the individual ACTIONS...
ec. ACTIONS On3DxButtonMappingEditor , ACTIONS On3DxHelp , ACTIONS On3DxAbout -but only one *.dll in directory and this name is 3DxNX.dll
How does this work....?
Regarding the 3Dconnexion - everything works fine, but I just want to know if someone can tell me, how where NX finds these ACTIONS...?
The reason I ask for all this, is that since we updated to NX11 in our company, it has been necessary to put in entire filepath to the application's in our custom menufiles for each ACTIONS...
I have wondered why - but just did it....
If I not do this - NX raises an error when the button is pushed..."No action for this button"
But now - in our Ansys plug-in - the scenario is, that there are several ACTIONS defined in the *.men file, but only one(or two) *.dll - In this case I cannot put in entire filepath, because the ACTION does not refer directly to a *.dll application.....
Maybe someone can guide me on this issue...
lklo
I'm a little challenged these days, because I'm not fully aware how a small mechanism in NX works..
It is regarding how the parameter ACTIONS is handled in a menu file (*.men)....
I have created a lot of menu files in the past - and always the ACTION parameter is pointing to the *.dll (custom application)...works very well..
Then I saw in the 3Dconnexion plug-in - there is also a *.men file placed in the startup folder for this plugin...
But there is only one .*dll file - but there are 3 button sections in the menu file....each of them have the parameter ACTIONS defined.
But I wonder how these parameter is handled....?
Does NX look inside the *.dll and search for the individual ACTIONS...
ec. ACTIONS On3DxButtonMappingEditor , ACTIONS On3DxHelp , ACTIONS On3DxAbout -but only one *.dll in directory and this name is 3DxNX.dll
How does this work....?
Regarding the 3Dconnexion - everything works fine, but I just want to know if someone can tell me, how where NX finds these ACTIONS...?
The reason I ask for all this, is that since we updated to NX11 in our company, it has been necessary to put in entire filepath to the application's in our custom menufiles for each ACTIONS...
I have wondered why - but just did it....
If I not do this - NX raises an error when the button is pushed..."No action for this button"
But now - in our Ansys plug-in - the scenario is, that there are several ACTIONS defined in the *.men file, but only one(or two) *.dll - In this case I cannot put in entire filepath, because the ACTION does not refer directly to a *.dll application.....
Maybe someone can guide me on this issue...
lklo