WorldViz User Forum

WorldViz User Forum (
-   Vizard (
-   -   IDE file path resolution with 'Go To Definition' (bug) (

fordprefect 03-19-2014 07:28 AM

IDE file path resolution with 'Go To Definition' (bug)
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
  1. looking in the script's folder
  2. looking in the Vizard library folder c:\Program Files\WorldViz\Vizard5\python\
  3. 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

Jeff 03-19-2014 10:33 PM

Thanks for the IDE comments and bug report! We'll look into getting that fixed.

All times are GMT -7. The time now is 08:13 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
Copyright 2002-2018 WorldViz LLC