Topic: Reactor...

[JohnK]

Se7en, the COMMAND is not within a callback so it's perfectly legal.
...
When you get it working, I hope you are aware of the fact that the way it is written, it will add reactors each time C:HTZ is called (which can become very unpleasant).

The point is that you shouldnt use command or setvar in reactor apps at all untill you KNOW how/why/when you can use them. The fact that you can in certin circimstances is irrelevent to (s)he trying to learn reacotors. First they must learn why/what their code is doing before they can start learning the loop holes.

[SMadsen]

Aye Sir!

[JohnK]

Im sorry if i sounded gruff in my post.

I think it would be best if you use Pseudo code to layout your reactors. Cause then you can see potential disasters.  Creating a reactor everytime a command is called is not a really good idea. ...you have to be carefull when you use reactors. They can get away from ya real fast.

[MP]

A sure way to create a house of cards is to use reactors gratuitously. We use them VERY sparingly.

[Andrea]

ok...so if i understand...
can i modify the code like this..


(defun c:HTz ()
 (if (and (not var1) (CC_find_env));;detect if some variable is set
   (progn    
  (SDC_readSfile);;read other variables
  (setq BC1r T11r
           BC1 T11
  );;redefine some variables
  (loadreactortype);;<---HERE LOAD REACTOR NOT WORKING
);;progn
);;if

(command "_DTEXT")
);;end HTz
 
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
(defun loadreactortype ()
(setq var1 T)
;;(alert "Reactor loaded")
(vl-load-com)
(vlr-command-reactor nil '((:vlr-commandWillStart . startCommand)))
(vlr-command-reactor nil '((:vlr-commandEnded . endCommand)))
(vlr-command-reactor nil '((:vlr-commandCancelled . cancelCommand)))
(vlr-command-reactor nil '((:vlr-commandFailed . failedCommand)))
)

But not seam to work...

[SMadsen]

Setting a flag is one way to go about it, yes. If being precarious, which we all tend to be at times, it wouldn't necessarily mean that the reactors were actually created, though.

Personally, I would use the return value from VLR-COMMAND-REACTOR to tell me directly about the success of the function (in this particular case all the return values).

[Andrea]

SMaden..

I'm not sure if I really understand...
could you explain a little more ?

[SMadsen]

It's pretty much explained in the thread that Serge linked to. Did you read the comments in the code?

[Andrea]

It's pretty much explained in the thread that Serge linked to. Did you read the comments in the code?

Ok.. I've made some modification in my routine...and it work just fine with 2002 and 2004.

thanks all..

Now I need to know how to unload the reactor without closing the drawing..

any idea ?

[Andrea]

ok sorry...i just find it !!

(vlr-remove-all)

[SMadsen]

I'm glad you got it working, Andrea.

Just in case you forgot to do this: If you are depending on recreation of the reactor after having killed it and you are maintaining a global variable that points to it then set the global to nil when destroying it.

Code: [Select]


;; if you are doing this to create the reactor:
...
  (if (not *my-reactor*)
    (setq *my-reactor* (vlr-command-reactor .... etc..)
  )
...

;; then do this when destroying it:
...
  (vlr-remove-all)
  (setq *my-reactor* nil)
...

Of course, if you have multiple reactors running, you can also kill the specific one with (vlr-remove *my-reactor*)

[Andrea]

thanks SM I appreciate..

[Andrea]

I use this...



(vlr-remove-all :vlr-command-reactor)


is this ok ?

[SMadsen]

That would be correct if you want to kill all command reactors, yes.