Scolring - Forum

Entraides et échanges autour de la technologie Scol - Informations and exchanges on the Scol technology

Vous pouvez changer la langue de l'interface une fois inscrit - You can change the language once registered

You are not logged in.

#1 27-May-2012 19:15:03

dhika11march
Member
From: Indonesia
Registered: 30-Mar-2012
Posts: 227

destroyed instantiate itself

hello?
is it possible to destroyed the instantiate itself?
because I don't want if I have been loaded my instantiate, then I can still use event such as showing flash interface with marker, that can only do when I am still in the .xos file before.

I am so confused with this condition.
I hope if I have been loaded the new .xos, so I hope there isn't event (that can only do in the file .xos before) that can be played in the loaded .xos.

I hope it can fixed well!
Thanks.

Offline

#2 28-May-2012 14:24:33

arkeon
Admin. / Scol language & OpenSpace3D developer
From: Nantes
Registered: 30-Mar-2009
Posts: 5,161
Website

Re: destroyed instantiate itself

yes just add a close plugIT in yout instantiate xos.
call the close action to destroy the instance

Offline

#3 28-May-2012 16:14:34

dhika11march
Member
From: Indonesia
Registered: 30-Mar-2012
Posts: 227

Re: destroyed instantiate itself

this is the case:

i have 3 files .xos

1.xos as container for 2.xos and 3.xos

then I running the 1.xos,

in this program, there is an events like this --> if I press 1 (on the keyboard) then it can loaded 2.xos
                                                                    if I press 2 (on the keyboard) then it can loaded 3.xos

my purpose is .. When I'm loaded the 2.xos or 3.xos, then file 1.xos (as container) must be destroyed.
Why?
Because if 1.xos isn't destroyed, so I can still use such as marker event, keyboard or mose event that it can only do on 1.xos, whereas
I want if the scene has been loaded on 2.xos or 3.xos, so there isn't related with 1.xos, so that I can't use an events that can do in 1.xos.

by the way,
I have been tried for your suggestion, that is about put close plugit on my scene.
but what I mean isn't like that, it's about how to destroyed the .xos as container.

Thanks!

Offline

#4 28-May-2012 17:42:13

arkeon
Admin. / Scol language & OpenSpace3D developer
From: Nantes
Registered: 30-Mar-2009
Posts: 5,161
Website

Re: destroyed instantiate itself

you want to unload other instantiates when you load a new one right ?
retrieve this directory : https://arkeon.dyndns.org/svn-scol/trun … samplebox/

and copy it in your openspace3d/samplebox directory
this is a good example for instatiate plugITs

Offline

#5 31-May-2012 08:55:12

dhika11march
Member
From: Indonesia
Registered: 30-Mar-2012
Posts: 227

Re: destroyed instantiate itself

hey, your suggestion can't solve my problem.

i was tried this:

keyboard.keydown.input ---> multioutputinst.out1 ---> instantiate.removeallinstance
                                                                 .out2 --->                .addinstance

for those event, it can't maked my .xos (as container) destroyed. but in fact, I only add an instantiate to.xos that being used. So, of course there is occured some event (that is event from first .xos and event from second .xos).
it means that there is 2 files running.

simply, i just want to switch .xos file when I press a keyboard. and when the .xos file loaded, so the all instance must be removed.

in fact, i think your suggestion is right and reasonable. But I'm so confused when it didn't work.

OK, that's all.
help me to solve my problem.
Thanks!

Offline

#6 1-Jun-2012 23:01:52

arkeon
Admin. / Scol language & OpenSpace3D developer
From: Nantes
Registered: 30-Mar-2009
Posts: 5,161
Website

Re: destroyed instantiate itself

Hi !

you should construct your project this way :
- main project witch manages the others instances with common plugITs (usually the navigation, camera for ar if all your others xos use it ...)
- 1st project
- 2nd project
- ...

for example the keyboard event is managed in the main project and then load or remove the instances.

Offline

Board footer

Powered by FluxBB