Digital Workshop

I've had this cloning problem for ages but couldn't pin down the source until now. Does anybody know a solution.

When you clone an object it starts life with the value 2147483648 and increments by one for every additional clone created.

However, when you reset a page, the clone value does not reset. I'd would have thought that it should.

Any ideas very much welcomed.

Mackavi

The object IDs have to be unique within any run of the publication; it cannot be reset.

Cheers Duncan,

That makes sense. Having slept on the problem, might have a solution.

My issue is that because the clones display a variable that is read from an array, I use a counter to track the position of each clones' value. The clone ID is then used to calculate which cell of the array, their value is stored in.

Because I have have to reset the page at certain times, the clone ID continuous on, but the array counter is reset to zero causing them to become out of sync. Without restarting the application, I'm unable to reset the clone ID.

As my reset needs to wipe all current variables, I can't even keep the counter in memory, but I think that if I use a temporary registry store, I could read the last counter value in and only wipe it if the exit button is clicked.

If anybody has a simpler solution, am more than will to take ideas.

Mackavi

Write to a root text file on harddisk before resetting?

BR

Jim

Mackavi I've found this solution ,but I don't know if this what you want or something else.Just give it a try

Glad to see I'm not the only one working on this sunny Saturday afternoon This issue is still on my bug board, as I've yet to impliment Duncan's solution.

I had a good play with the IMP you posted and it's a great idea for solving this (although I still feel that there is no reason why the CloneId shoudn't reset when all other publications variables are reset). Both solutions have merits - yours elemiates the ID problem altogether by wrapping the ILMObject inside an array which would of course be resettable whereas Duncan's allow me to continue storing my actual values inside the clone as a variable to be manipulated directly.

Storing objects inside an array is an extremely powerful way of handling them but can be extremely frustrating when you want access to the data inside the object as I discovered writing Scroggle.

I've since started using custom objects and prototypes and have the very very very early idea of how this will improve the next version of Plethos.

Many thanks for this. I love the idea of using cloning as it maximise the flexibility of my programs and I think that if i use it with custom objects / prototypes I'd have a powerful solution to many types of problem.

Mack

P.S to other readers - i would recommend downloading this and having a play if your interested in cloning as demostrates how to use it effectively. I'd add a debug, left click action to the TC box to see exactly what is stored in the myClone array