Options
Muse and TPDesign 5 ListViews, sanity check
Rombus
Posts: 17
I need a sanity check here:
a Listview in TPDesign5 has to be driven from a dynamic data source, correct?
Currently there is no way it seems to "host" a file on a MUSE controller for it to act as the dynamic data source, correct?
Is there anyway to manually fill in a listview? I know in netlinx you could publish a data source, but I dont think MUSE has that functionality.
0
Comments
Thinking about it, it may be possible to manually create a xml in the format the listview commands of G5 can read it. If having a listview compatible xml file, it should be possible to modify it with your own datasets. (or use the sample program in the G5 programming manual to create the xnl on a NX, and then download it from the NX)
Problem is where to store the file, so the panel can access the file.
G5 accesses the file by HTTP (port 80) or HTTPS(443), but currently Muse doesn't have an open webserver to host public stuff, like the listview xml. So the xml would have to be stored on another server that can be accessed by the panel, and the resource parameters in the G5 file have to be set up accordingly.
Just to note: in Varia fw 2.13.16, the listview functionality is broken, on graphical and functional level. It's reported.
@Marc Scheibein Thanks for the clarification! I Figured I could host a file elsewhere, but in our environment id have to spin up a HTML server somewhere since the A/V networks are self contained. Learning Android development to utilize the "Any-App" persona is on my eventual to-do list
well, for this little "provide the xml by http" thing, a Raspberry Pi should be enough...
@Marc Scheibein You mentioned in Varia FW 2.13.16 that Listview functionality is broken, Is there anything else? I noticed that ^BSP functionality has seemingly changed as well, and my button positioning scripts are now not working on the new FW.
I already have a newer, non-public fw build for some testing.
In that build, listview basically is working again (with still some issues), and the ^BSP is working as expected:
We hope that we will get a hotfix or new release of the Varia fw soon...
Thanks! I did more bench testing and figured out that it seems like FW 2.13.16 does not like the -1 as a default parameter usage for ^BSP-
the "-1" works in the fw version I have.
Fingers crossed that we get that release soon.