Dan, sry about the global variables. Didn't realize the plugin was "exec"ed, I assumed it was imported. I will change the calltips code so that it won't pollute the drpython environment.
Also, is there a policy on added members to drPython stuff? I added an "importAliases" member to the drFrame.txtDocument via the PlugIn. Any problems there?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No worries. I had never explicitly made that request
before, and thought it would be a good idea.
If it is in a plugin, you can do whatever you want to.
That the purpose of plugins.
Of course, adding members can be risky, and lead to
plugin conflicts, so it is advisable to make sure any variables added to DrFrame, etc, have the plugin name as a prefix.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When submitting fixes to plugins, please:
Unix Line Endings,
No Global Variables.
Dan, sry about the global variables. Didn't realize the plugin was "exec"ed, I assumed it was imported. I will change the calltips code so that it won't pollute the drpython environment.
Also, is there a policy on added members to drPython stuff? I added an "importAliases" member to the drFrame.txtDocument via the PlugIn. Any problems there?
No worries. I had never explicitly made that request
before, and thought it would be a good idea.
If it is in a plugin, you can do whatever you want to.
That the purpose of plugins.
Of course, adding members can be risky, and lead to
plugin conflicts, so it is advisable to make sure any variables added to DrFrame, etc, have the plugin name as a prefix.