Okay. I am sure that once again I

[Fluke026]

Okay. I am sure that once again I have a simple problem, but the solution escapes me. It seems like the simpler the problem, the harder it is to see the solution.

I have a class [MoveMent = class(TPersistent)] that just spontaneously loses its settings between function calls. I call the constructor then return to the GUI. Taking advantage of the debugging tools shows me that this is okay up to this point. When I call an event that accesses the data of Movement, Movement is just full of weird data.

What is going on on?

 

[towerbase]

I think you need to give us a few more clues. I suspect that when you refer to class you mean an instance of the class MoveMent ie an Object. (Note that it is conventional to prefix class names with the letter 'T'.)

Have you called the MoveMent constructor?

movem := MoveMent.Create;

If movem was not properly constructed then it might have any old address in it which is likely to give the kind of symptoms you describe.

Andrew

 

[Fluke026]

I found it. The problem in TMovement was a bad copy constructor. Instead of creating another instance of the correct TMovement, I was creating a pointer to it. When I freed my copy, I freed the original also.