Scripting error with LemurEditor 5.0.3

[mssngmrblz]

i'm getting a little "!" error in Lemur Editor.

using destroyobject(obj)

please see attached screen grab.

Thanks for all your good help!

Screen Shot 2014-07-02 at 9.26.24 PM 1.jpg (208.69 KiB) Viewed 1919 times

[Softcore]

I dont think destroyobject(obj) is supported officially - I might be wrong though

[mssngmrblz]

Anyone know for sure or know a workaround?

[oldgearguy]

Anyone know for sure or know a workaround?

What are you trying to accomplish with destroyobject? Simply freeing up resources?

[mssngmrblz]

I have a page in my template for loading custom controls. When I launch a new scene in live that loads controls the page is first wiped clean to make way for the new bank of controls.

it's also used in Mu. I stole it from there. Mu has the same script and is displaying the same error.

Thanks for your time and thought.

Pat

[Macciza]

Hi
Yes i am pretty sure it was deprecated with create object though they are looking at keeping that
From memory they were used together to get around the memory issues on hardware lemurs.
With the sizes possible now i guess it would be a case of rewriting Mu to simply have all those subpages in the one project and simply page them in and out of view as needed

[oldgearguy]

I have a page in my template for loading custom controls. When I launch a new scene in live that loads controls the page is first wiped clean to make way for the new bank of controls.

it's also used in Mu. I stole it from there. Mu has the same script and is displaying the same error.

Thanks for your time and thought.

Pat

Got it. That's good programming practice for sure. From my (limited) experiences with Lemur on iOS programming, resource management may be done 'under the hood', but in general I've tried to define a set of controls and then either use hide/show type operations to bring them into view or use setattribute() type commands to relabel/resize/reposition them as needed.

I can certainly see how the sheer number of objects needed for large templates could cause memory issues, although there was a recent maximum template size increase in one of the 5.0.x updates.