Graphics

So... When is this gonna get fixed?

This goes back to at least version 6 (and I assume since forever really)
In visual logic there is a block "Data Sources -> DataLinq".

And adding it gives you access to the regular datalinq browsing, just like when you set a text object to get data from datalinq. Even with a checkbox that says "live update" on it.
However, this does not work. It only works in the one instance when you actually connect the datalinq block to another, and Xpression will get the correct current value in from DataLinq.

But, if you then change this value, even if the "live update" is checked, this does nothing to the datalinq element visual logic.

So, in order to use values from DataLinq into visual logic, what I've had to do, is to make a group that contains text elements that are linked with DataLinq values through their "Data Source" tab, hide this entire group, and then use their respective text values in visual logic in order for them to update live.

While it works, is just seems completly unessasary to me...
The simple DataLinq block in visual logic should do the trick, and would definetly save me some time. And last not but least, not clutter the left hand side in Visual logic with a bunch of elements that are just value holders.

What version and build of XPression are you currently seeing this behavior in?
#XPression

What version and build of XPression are you currently seeing this behavior in?

I'll get back to you tomorrow with the specific version.
But pretty sure it was version 8.0 (or basically the latest release).

The problem has allways been there though on every version of Xpression 6.x that I ever tried it on. For sure 6.0, 6.1 and 6.5...

But yeah, will get you the exact version tomorrow.
#XPression

Here we go @garner, the Xpression version in question (at least the latest one I've been able to test on) is Xpression Designer v.8.0 Build 4106
I have no reason to believe it works on Studio or Studio GO either.

Also found a post now about the same from 1 year ago here:
https://discussions.rossvideo.com/fo...-funcion-block

And I knew I had run into this problem before, so I also found a post where I mentioned some of the same back in 2017:
https://discussions.rossvideo.com/fo...with-dashboard

The storing of DataLinq values in text fields and not use the DataLinq block in visual logic in order to use the value again IN Visual Logic seems to have been the go-to-sollution since like... ever...
It just simply does not "Live Update" with the blocks in Visual Logic.
#XPression

it seems that datalinq block output is updated through visual logic as soon as the scene is online (and then live update works).
when in layout mode alone , and the scene is not in a framebuffer output, data is not updated.
(test done with Xpresssion Designer 8 build 4089 )

#XPression

it seems that datalinq block output is updated through visual logic as soon as the scene is online (and then live update works).
when in layout mode alone , and the scene is not in a framebuffer output, data is not updated.
(test done with Xpresssion Designer 8 build 4089 )

Hmmm.. ok! Never got that far as I'm used to seeing the changes in the designer (as it works with the text objects).

Can I then ask for a change in the way these DataLinq blocks work in designer?
As it can be somewhat difficult to work with a non-updating example in designer, only to trust it works when going online in the sequencer?
#XPression

a workaround ,when you are in layout mode, is to load your scene in a framebuffer : editor window seems to be updated then .
You can use virtual output for example , and even close the virtual output, but keep the scene in a layer.


#XPression

a workaround ,when you are in layout mode, is to load your scene in a framebuffer : editor window seems to be updated then .
You can use virtual output for example , and even close the virtual output, but keep the scene in a layer.

This seems to be working. However it also illustrates the point as well. It's obvious that it CAN update the editor window then this way.
But it just doesnt happen without a workaround like this.

So yeah, I'd still like to see this change.
#XPression