Sorry I missed this call (and all the other recent interop review
calls) but product development schedules dictate my time lately, as
you all can well appreciate. We do in fact implement DECLARED as r/w
for some products (the XPrint products, for example). And we do
actually use it as a way of configuring the printer to know what paper
size is in a tray for sizes that cannot be detected. Specifically we
have products which can detect typical sizes like letter, A4, and
legal, but cannot detect other sizes which the printer does in fact
support. So we use DECLARED as a way of telling the printer "hey I
know you can't detect what size is in tray 1 right now but, trust me,
it's 8 x 10". In this case, if you then load letter in tray 1,
DECLARED will still indicate 8 x 10, but CHOOSEN will change to
letter. Does this make sense to anyone? I believe it pushes the
definition of these objects to the limit, but we do use it this way.
Cc: "Harry Lewis <email@example.com>"
Subject: PMP> prtInputMedia...Dims
Date: Friday, March 07, 1997 12:51PM
We went over this in the call, and I don't think there were any cases where
Declared and Chosen really differed. What we didn't cover, however, is
how many vendors implemented Declared as r/w vs. how many just map the
Chosen value into the Declared?
Isn't this important interop info? I don't know why a "show of hands"
wouldn't suffice, here.