Will BindExternalWidget() work against the Global Rackspace?

Hi.

Is it possible to use BindExternalWidget() in a local rackspace in order to bind to a widget in the Global Rackspace?

AI (which of course could be incorrect) suggests something like this:

   globalKnob : ExternalWidget

Initialization
   if BindExternalWidget(globalKnob, "GlobalGainKnob", "GlobalRackspace") then
      Print("Successfully bound to GlobalGainKnob")
   else
      Print("Binding failed")
   end
End

But I have not had success in getting this construction to report a successful binding, despite trying to edit/correct the arguments to match the System Functions List. I can get a successful compile, but not a successfully reported binding. (The arg2 widgetName I assume to be the global widget’s handle …)

AI doesn’t know much about GPScript - please don’t depend on it.

Try “GLOBAL RACKSPACE” instead of “GlobalRackspace” but I don’t remember if we support it - there is a reason that BindExternalWidget is marked as “experimental”

Thanks for your reply.

I don’t/won’t depend on it, but I do consult it and it has been quite helpful to me in some cases. I started doing this based on a prior tip from you!

Sometimes I tell it about it’s mistakes, and it always politely thanks me for correcting it. (I wonder if it can actually learn from such feedback.)

Hey, that worked, thanks!

The problem is, its not correct often and then you’ll end up coming back here to ask for the real answer anyway. In the meantime, re-posting incorrect script from an AI source means that it is now being re-integrated into all AI sources as a reliable source of GPScript. The more people re-post incorrect information, the more corrupt the models become.

Very good point. Thanks for this reminder.

I do it the other way. I have a global GPScript which binds widgets in the Local Rackspace. Hence I only need to have one GPScript one the Global Rackspace.

2 Likes