-
-
Notifications
You must be signed in to change notification settings - Fork 333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
arv_dom_document_get_url is always NULL #829
Labels
Comments
EmmanuelP
added
1. bug
Problems, incorrect behavior or appearance
5. Genicam
Issue in Genicam implementation
labels
Oct 21, 2023
EmmanuelP
added a commit
that referenced
this issue
Nov 3, 2023
Please try #835. |
eudoxos
pushed a commit
to eudoxos/aravis
that referenced
this issue
Nov 4, 2023
Excellent, #835 really helps! |
EmmanuelP
added a commit
that referenced
this issue
Nov 5, 2023
EmmanuelP
added a commit
that referenced
this issue
Mar 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
There is a function to retrieve URL of the genicam XML:
arv_dom_document_get_url
; it returnsArvDomDocumentPrivate
'surl
attribute, assigned inarv_dom_document_new_from_url
.This codepath is not currently used at all, though. Instead,
arv_gc_new
receives already loaded XML; the loading happens in_load_genicam
which only returns the XML content but does not store its URL (obtained witharv_gv_device_read_memory
atARV_GVBS_XML_URL_SIZE
). That is whyarv_dom_document_get_url
return NULL (as far as I understand).Expected behavior
arv_dom_document_get_url
returns URL (such asLocal:genicam.xml;123;456
, 123 being address and 456 size) which can be parsed and used to retrieve the XML from memory again (for GigeV, USB and Fake cameras).Platform description:
Additional context
This is needed for the GenTL provider so that it does not duplicate code from other parts of Aravis. GenTL consumers download and interpret the XML themselves, and use URL to request them via memory access.
The text was updated successfully, but these errors were encountered: