Hi all,
I'm currently building a project for a client that wants the XPression to trigger scenes by itself using data coming through datalinq.
I have got quite a bit working already and the rest is just a matter of time but I am hitting some bumps along the way that I need to work around.
Now I know that this type of automation is not really what XPression is meant for, but it is kind of a special setup and project. I have looked at the specs initially and found that I could do pretty much everything they asked using the tools in Visual Logic.
So after about a week I have quite a few bits working already but here are a few remarks:
• When you use Excel, you can make use of SQL Queries to sort data in your Datalinq to be able to reduce the amount of data. In my case, I can't use Excel because the automation-system is using XML-files to export data. This means I have to filter the results in Visual Logic, which means linking a lot of nodes which is taking a lot of time. It's also not much fun when there's a bug in the Datalinq node in Visual Logic...
What I'm trying to do is filter all the records that contain a specific ItemCode and then use the first two records that are found. I was thinking of maybe using the SORT-selector but I haven't managed to make it work yet.
• Does anybody know how the OUTPUT SELECTOR works?
• When you use the ClockTimer Widget in a scene, you are able to use offsets to account for timezone changes. However, the DateTime Clock-node in Visual Logic does not have this feature. Also it would be useful to have an option to be able to have the clock switch between Daylight Savings Time. This would make it a lot easier when we have to convert UTC-time to local time.
• The same applies to calculating with time. There is no node that allows you to add or subtract for example 2 seconds to a DateTime and get a new DateTime. This means that you need to do a lot of effort and calculations to be able to generate a new DateTime.
• The same applies to comparing two DateTimes. Yes you can use the DateTime-delta but it does not tell you if one DateTime is larger or smaller than the other DateTime.
• I am under the impression that there is something wrong with the calculations inside Visual Logic. When I was trying to make calculations with a precision of 8 digits, my value could not go above 10 or I would get a fixed value. I was doing this because I needed to check if one DateTime was larger or smaller than another DateTime. So I had to convert them to numbers to be able to compare them, but the values were getting too big for XPression to calculate with, so I had to use some other calculations to reduce them to be able to calculate with.
So in short, there are a few actions that could be added to Visual Logic, mainly regarding to calculating / comparing DateTime that could make it a lot easier for us.
Best regards,
Ken