You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
media-col -> media -size -> (x-dimension, y-dimension) -> integer(1:MAX)
media-col-database -> media -size -> (x-dimension, y-dimension) --> integer(1:MAX) | rangeOfInteger(1:MAX)
The requirement is such that, we should not allow rangeOfInteger in the job template attribute media-col, but only allows rangeOfInteger in the Printer Description attributes media-col-database and media-col-ready.
Currently genTypes.py is unable to create a separate class for MediaColDatabase and instead it tries to put everything back to MediaCol with a warning on new member. WARN: Collection type already has different member media-size
The text was updated successfully, but these errors were encountered:
media-col-ready/media-size/y-dimension will have a syntax of integer(0:MAX)|rangeOfInteger(1:MAX) so that the printer can provide 0 (zero or nil) to indicate a roll length that is unknown or unbounded. That likely will also apply to media-col-database/media-size/y-dimension as well.
As per latest IANA spec https://www.iana.org/assignments/ipp-registrations/ipp-registrations.xhtml, MediaColDatabase and MediaColReady has different attribute types for MediaSize member attribute.
The requirement is such that, we should not allow rangeOfInteger in the job template attribute
media-col
, but only allows rangeOfInteger in the Printer Description attributesmedia-col-database
andmedia-col-ready
.Currently genTypes.py is unable to create a separate class for MediaColDatabase and instead it tries to put everything back to MediaCol with a warning on new member.
WARN: Collection type already has different member media-size
The text was updated successfully, but these errors were encountered: