Newbie baffled by new behaviour after editing wxProject.py demo program

So you don't use GetPyData anywhere? The only explanation I can see is that your current working directory is still the path where the file is located.

···

On 12/21/10 5:52 AM, Michael Mason wrote:

This displays the bare filename in the tree but stores the whole path
using SetPyData(). I expected to have to do some more work to get the
program to retrieve the stored pathname and use it, but in fact--and to
my great surprise--the program just worked. What I don't understand is
how the program knows to use the full pathname that I stored using
SetPyData().

Could some kind soul explain why this works?

--
Robin Dunn
Software Craftsman

> This displays the bare filename in the tree but stores the whole path
> using SetPyData(). I expected to have to do some more work to get the
> program to retrieve the stored pathname and use it, but in fact--and
> to my great surprise--the program just worked. What I don't understand
> is how the program knows to use the full pathname that I stored using
> SetPyData().
>
> Could some kind soul explain why this works?

So you don't use GetPyData anywhere? The only explanation I can see is

that

your current working directory is still the path where the file is

located.

And you're right. I stupidly hadn't noticed that my test version and the
original version had different working directories. Now that I've fixed
that, my test version no longer works--which is OK because that's what I was
expecting.

Many thanks for your help!

···

On 21 December 2010 at 17:59 Robin Dunn wrote:-

On 12/21/10 5:52 AM, Michael Mason wrote:

--
Michael