- This topic has 0 replies, 1 voice, and was last updated 8 years, 5 months ago by .
-
Posts
-
We have a customer setting a custom capability on the Kodak i2000 series scanners:
#define CCAP_TRANSPORTTIMEOUTRESPONSE 0x8028
#define CCAP_TRANSPORTTIMEOUT 0x8003I can get these capabilities no problem, CCAP_TRANSPORTTIMEOUTRESPONSE uses an ENUM container, and CCAP_TRANSPORTTIMEOUT uses a RANGE container.
When the CCAP_TRANSPORTTIMEOUT capability is ‘set’ it succeeds, but then when I try to ‘get’ the CCAP_TRANSPORTTIMEOUTRESPONSE next I get it fails with condition code 15 (“Capability has dependency on other capability.”).
vs.
When the CCAP_TRANSPORTTIMEOUTRESPONSE capability is ‘set’ it succeeds, and then when I try to ‘get’ the CCAP_TRANSPORTTIMEOUT next it works without error.
This leads me to believe I can’t set CCAP_TRANSPORTTIMEOUTRESPONSE after setting CCAP_TRANSPORTTIMEOUT, so I have to set CCAP_TRANSPORTTIMEOUTRESPONSE first. The bizarre thing is when I duplicate these steps in Twacker it works both ways without issue.
Is this some weirdness with custom capabilities or if something is wrong our implementation and if so any clues where should I be looking?
😯