Dcal macro bug?
Posted: Fri Apr 10, 2009 7:20 pm
Hello Pietro,
I do not agree that the different way the function menu and command menu operate is a 'bug'. The command drop down menu allows the user to have access to their commonly used macros, even if they are in different folders.
The function menu pathname is controlled by the constant pathmcr. (in the case of macros).
So a user will add a commonly used macro by the 'configure' option in the command menu.
The problem with Xbuilder is that after adding it to the command menu it changes the function menu path. Not what the DataCAD user expects to happen, so the 'bug' is in Xbuilder.
Accessing other macros from the command menu does not change the function menu path (commonly \datacad 12\macros). Xbuilder does which is very annoying.
Regards
Rod Walker
I do not agree that the different way the function menu and command menu operate is a 'bug'. The command drop down menu allows the user to have access to their commonly used macros, even if they are in different folders.
The function menu pathname is controlled by the constant pathmcr. (in the case of macros).
So a user will add a commonly used macro by the 'configure' option in the command menu.
The problem with Xbuilder is that after adding it to the command menu it changes the function menu path. Not what the DataCAD user expects to happen, so the 'bug' is in Xbuilder.
Accessing other macros from the command menu does not change the function menu path (commonly \datacad 12\macros). Xbuilder does which is very annoying.
Regards
Rod Walker