fordprefect
03-19-2014, 07:28 AM
First to say:
:) IDE warning when a loaded module obscures another module (with same name) on the search path
:) new middle-click shortcut for Go To Definition option from the context menu
Next: when executing a script, references to imports are solved by
looking in the script's folder
looking in the Vizard library folder c:\Program Files\WorldViz\Vizard5\python\
looking in the Python library folder c:\Program Files\WorldViz\Vizard5\bin\lib\
So far so good.
now for the :( part: when invoking the Go To Definition command, this search path seems not to be used. More precisely, the file's folder is not searched.
[I found this as, for the moment, I have to obscure the shipped vizproximity module with my fixed variation. And when going for a definition, the IDE would always open the library file:eek:, and not mine]
Best Regards, Walter
:) IDE warning when a loaded module obscures another module (with same name) on the search path
:) new middle-click shortcut for Go To Definition option from the context menu
Next: when executing a script, references to imports are solved by
looking in the script's folder
looking in the Vizard library folder c:\Program Files\WorldViz\Vizard5\python\
looking in the Python library folder c:\Program Files\WorldViz\Vizard5\bin\lib\
So far so good.
now for the :( part: when invoking the Go To Definition command, this search path seems not to be used. More precisely, the file's folder is not searched.
[I found this as, for the moment, I have to obscure the shipped vizproximity module with my fixed variation. And when going for a definition, the IDE would always open the library file:eek:, and not mine]
Best Regards, Walter