In the current implementation we disabled messages containing array fields:
This has multiple reasons:
Arrays containing only numbers such as int32[] or float64[] should be possible to implement, but would require some work as we didn't have this in mind initially.
Arrays containing strings (string[]) are not as easy, as URScript only supports numeric arrays / matrices. We could probably only copy the whole string array to a string as a list `"[string1, string2, ...]" and leave the parsing to users / provide script functions to extract the Nth entry from that list...
Arrays containing more complex structures, e.g. the rosout/get_loggers service:
will be even more complicated to handle in URScript. Again, keeping the full json string [{"name": "ros", "level": "info"}, {"name": "ros.roscpp", "level": "info"}, ...] might be an option.
I currently tend to leave this out of the first non-beta release, as this isn't something we initially planned to support completely.
In the current implementation we disabled messages containing array fields:
This has multiple reasons:
int32[]orfloat64[]should be possible to implement, but would require some work as we didn't have this in mind initially.string[])are not as easy, as URScript only supports numeric arrays / matrices. We could probably only copy the whole string array to a string as a list `"[string1, string2, ...]" and leave the parsing to users / provide script functions to extract the Nth entry from that list...rosout/get_loggersservice:[{"name": "ros", "level": "info"}, {"name": "ros.roscpp", "level": "info"}, ...]might be an option.I currently tend to leave this out of the first non-beta release, as this isn't something we initially planned to support completely.