[vtkusers] GetNumberOfPoints() of vtkPoints

[Ming Chao]

Yeah, it makes a lot of sense. Local variables are definitely easier to
control than global ones. Thanks again for all help.
Ming

On Fri, Oct 24, 2008 at 12:42 PM, David Cole <david.cole at kitware.com> wrote:

> On Fri, Oct 24, 2008 at 1:00 PM, Ming Chao <mingchao2005 at gmail.com> wrote:
>
>
>> It appears you recommend to leave the env variable untouched, but would
>> rather copy dlls into the .exe directory. But the problems is that for every
>> project using vtk I have to copy them. Isn't that awkward? What is the
>> disadvantage of setting environment variables?
>>
>
> How long did you spend thinking there was a problem when there wasn't one?
> Wasted time is the primary disadvantage of setting environment variables for
> finding DLLs.
>
> If you do want to set it via environment variables, at least set it
> locally... (In a customized command prompt or just within your Visual Studio
> solution.) That way, you won't get confused again two years from now when
> you've built another new build of VTK and are trying to get another
> application running.
>
> The other secondary disadvantage of using environment variables to select a
> build of VTK dlls is when you have multiple builds of VTK that you are
> switching between. Whenever you switch an environment variable you have to
> kill all the processes that have a copy of the old value in them and then
> restart them. To me, it just seems easier to say "I will always get VTK dlls
> from the same directory as my exe" and *never* think about the PATH env var
> again.
>
> Hopefully, this makes some sense...
> David
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20081024/1bac8b7f/attachment.htm>