Digital Workshop

Hi

I've come across a strange issue with drawn shapes and reloading pages. The shape is set to draw automatically, which happens the first time. If you reload the page, it doesn't draw.

I've recreated the problem in the attached. It works in editor mode but the not in a published version. The original issue I was fighting with was actually only showing up on an older, slower PC, which made me think it was a memory or speed issue.

I just need a workaround for this. I've tried adding delays, switching between two drawing backgrounds, moving to another page then back, but it seems to remember not to show the drawing.

Any suggestions for solutions would be much appreciated.
Cheers
Dan

Hi Dan,

The easiest way to achieve this is to use a clone and destroy it each time.

Mack

Thanks Mack. I just slept on this after working far too late and also thought of clones. Glad there is an easy solution.

BTW, I know clones don't appear on a page if you reload it, but do they continue to use up memory if you don't destroy them before leaving the page?

Cheers
Dan

I tried to answer my own question and have ended up more confused. Reloading the page was increasing the RAM used by about 3-5MB each time. I set it up to destroy all the clones on leaving the page, but the memory used still increases by about the same amount each reload. This is also the case if you move away from the page and return. All the other variables and arrays remain unchanged, so I'm not sure why the RAM used is constantly increasing.

Another thing I am wondering about is how I store images. Each clone contains a number of images which can be cycled through by the user. I have the images in different placeholders, hiding one and showing another in order to change the image. If you clone one of these objects, does Opus copy all the images to the clone or refer to a common resource? Just wondering if there is a better method.

Finally, if you put code into an 'On Hide' trigger on a page, it doesn't execute. I've used 'Pre'Hide' instead to destroy clones, but wonder why the 'On Hide' is possible on a page if it doesn't in fact work.

Too many questions. Not enough answers.
Thanks
Dan

Ram / Memory is rather a generic term. You'd need to be more specific about what is increasing or do some reading if your not sure:

http://stackoverflow.com/questions/1984 ... orking-set

From my understanding of it, creating a clone will increase the WS private bytes (the important ones) that the publication is using. Creating a clone with child frames containing images will further increase the WSPB. If you reload the page, the WSPB should be reset, but virtual private bytes will not. I'm led to believe that the latter does not impact on the disk or physical memory BUT...

Taking out the trash, by destroying redundant clones and or before changing pages will keep both WSPB and Virtual PB down.

As for hiding, I always thought it was meant for objects on the page rather than the page.

Mack

My belief is that you cannot use a Hide action for a Page object the same way you would hide/show a graphical object.

But I wonder...
If you had a Pub that used Chapter properties to 'open in separate window', and subsequently used some of the opusscript commands to 'Close a View' (ie, close the original Page) -- that may represent an effective "hide" of the page (and so the 'on hide' trigger)???

Have you tried Multiframes at all? I would expect however the same 'no redraw' issue.

"moving to another page then back" works for me (incl. quick published FULL Type)

I put a Transition effect on the Page also -- to better observe the change.

Thanks for the feedback Lar. I got the clones working on this so moved on, but it is strange that the problem didn't show for you. There must be something odd going on here. I think I'll leave it for now.

Regarding the 'onhide'... it wasn't difficult to find a workaround; I just found it odd that this was allowed when it would be ignored. Perhaps not

Cheers
Dan