Digital Workshop

Does anyone know how to use this function ?

The help only states the next:

Syntax:

GetPersistentObject()

Return:

A unique persistent copy of this object.

Remarks:

The first time this function is called for any particular object a new script object is created as if the script "new Object" had been used. Subsequent calls to the function will return the same object. By setting properties of the object returned information can be stored that will remain even while the page is not visible. This mechanism is required because the objects on the page are destroyed when the page is no longer visible and are recreated when it becomes visible again.

This function creates a new native Object for the given host object.

As the Object is persistent, it is not destroyed like host objects when the page is changed.

To use it you would assign the new Object to variable, etc.

For example

var obj = Frame_1.GetPersistentObject()

Mack

I tried using this command with no success. Am I wrong in my thinking? If execute the code above on Page1, can I show and manipulate 'obj' or 'Frame_1' on Page2?

If it doesn't enable using objects across pages, what benefit or use is this command?

One sometimes gets this function repeatedly after you fail to follow your wife's directives

Which is shortly followed by IsObjectIntersecting()

Mack

I think you're both confusing this with some undocumented commands?
-- GetPersistentObjections()
-- IsObjectionInteresting() == false { do Chores() }


Been there, done that. So trying some OOPs scripts.

damn those undocumented commands!

As for being persistent, controlling across pages is not it's cuppa tea

It's a weird beastie, this one and most would probably simply create the same effect by reading the host objects into a global array but if you are creating a large multi-page program and want to be a super-ooper, then you could employ this method as it would offer an element of ease over using a super-array to track objects unless being associative is your kettle of fish (mostly piranhas) but that sounds like hard work.

On a serious point though, if Opus was able to access the persistent native object for a host object on other pages, this could provide large scale projects with an amazing internal data management system and scrap the need for lots of extra variables but alas on the family tree that is the publication - it doesn't seem to get much farther than the page branch

Mack

Mack wrote
I don't know what I need/will-do yet.

I still don't know/understand how exactly GetPersistentObject would be useful if it simply keeps an object alive for its page of residence. I guess if I rotated something and changed its colour, then returning to the page would restore it with that set of properties.

I might explore it further. What was thinking is to have a constructed object (ie, new Object()) in script hold various Page 'states' so that when a User returned to that page he is returned to the page the way he left it. But I think simply scripting will not accomplish that without a Pub level var or writing out to file or DB.


I think that is what you are referring to here. 'Yeah', rather involved... at least at the thinking and designing phase.

And the above mentioned GPO() only works for Host objects it seems.

Thanks.

Hi Lar,

Yeah, you're pretty much hitting the nail on the head. Any native object would need to be stored in a global variable, but of course you only need one variable to hold the super object which then holds the sub objects which then holds the properties.

But then this can hurt the head as much as working out the set-up for a GPO() but for large projects and when dealing with customers this a serious must. It's much easy to adapt a project that has been created using the principles of OOP that one with a crazy number of variables.

As for GPOs only for host objects - yes but then I cannot see why they'd be necessary for anything less.

Enjoy,

Mack

Thx.

Good timing with this advice. I am migrating a pilot layout after some rethinking. Trying to get my mind around the various piecemeal operations I built and bring some sense of order to it all.

I'll try using your past post on OOPs to see what I can sketch out for a super-Array.

Mack wrote:


I'd like to continue this part of the discussion, so am going over to previous post which is more directly on-topic for OOPs:
posting.php?mode=reply&t=3521