Scripting Live-Link 📜

It’s just a test panel. If I add or remove an element, there is no sync. (2.1 KB)

1 Like


  • Corrected an unreg bug (small error msg) . as @Elreenys reported to me above.
  • an addon debug system is set in place as a checkbox. it is only for controlling if your link is working properly. you’ll see the activity of every timer and handler check.
  • now #STOP in the first line will stop the livelink from your editor. (23.3 KB)

1 Like


It worked perfectly with me. i don’t understand ?
you can try to push on the “Execute” operator, it will manually run the script. as it was in the text editor and pushing the run script button.

or copy paste in the text editor.

be sure that #EXECUTE is in firt line. and that the link is running. in the new v21 there’s a debug mode where you can check the activity of the addon.

also if #EXECUTE_CUSTOM is alone witouth boundaries the script will be empty.

are you on 2.81 ? i did not try it yet.

Oops, yes I forgot the #execute. Sorry @BD3D.

1 Like

I have just started using it. Here is my question what happens if a user saves a script multiple times in a row and if the script is a modal one? Is this well defined? I will try to look at the script later since I would like to contribute to this. My basic testing proves that this idea works.

One thing I want to add is to be able to increase and decrease the number of scripts (in the tab) that this one watches.

I don’t know the specific answer as I don’t use nodal operator that much, all I can tell you is that’ it will adopt that’s same behavior as clicking « running script » multiple time in a row. IMO, There’s no reasons it wil adopt another behavior.

If an user don’t want to be annoyed every time he save he can remove only one letter from #EXECUTE.
What could also be done is an #EXECUTE_IF_CHANGE fonction -> if new text == old text -> do not execute. I think this can be done easily.

Every scriptslots are affected by one same SCR_OT_start_link and OT_stop_link operators with index values.

Thoses operators will activate/stop timers and handlers (3 def: text_pollX ,text_execX, and redrawX). I think it’s not possible to transfer any arguments in thoses def without fuc*ing things up with the timers/handlers (and stopping them). That’s why I propose only 3 slots. copy/paste def 10x the same way I did 3x seems really absurd :frowning:

1 Like